Compare commits

...

No commits in common. "c8" and "c8s" have entirely different histories.
c8 ... c8s

7 changed files with 38 additions and 1 deletions

3
.gitignore vendored
View File

@ -1 +1,2 @@
SOURCES/qatengine-1.4.0.tar.gz
SOURCES/qatengine-*.tar.gz
/qatengine-*.tar.gz

6
gating.yaml Normal file
View File

@ -0,0 +1,6 @@
--- !Policy
product_versions:
- rhel-8
decision_context: osci_compose_gate
rules:
- !PassingTestCaseRule {test_case_name: osci.brew-build.tier0.functional}

1
sources Normal file
View File

@ -0,0 +1 @@
SHA512 (qatengine-1.4.0.tar.gz) = 4e5a8a41ae07bf0704b5bfae23f6a5c7f1dd968ea721307ba078c704f8c2563ac9f17298752a9cf212ff9d6fb6185b7f5534651e1661ea06b1669dc53f80a585

13
tests/README Normal file
View File

@ -0,0 +1,13 @@
these tests should be configured as BaseOS CI tests (not as OSCI tests), as
they require an x86_64 machine with QAT_4XXX (or later) hardware, so should
be run in Beaker.
see: https://docs.engineering.redhat.com/display/RTT/Onboarding+gating+tests
and: https://docs.engineering.redhat.com/pages/viewpage.action?pageId=53110084
and: https://docs.engineering.redhat.com/display/RTT/Creating+and+Updating+beaker+test
see https://bugzilla.redhat.com/show_bug.cgi?id=1747499#c35 for the details:
> There is no make test inside qatengine. And yes the test procedures you mentioned
> in README are enough to test it with OpenSSL.
> https://github.com/intel/QAT_Engine#test-the-intel-quickassist-technology-openssl-engine
> https://github.com/intel/QAT_Engine#run-speed-with-the-intel-quickassist-technology-openssl-engine

6
tests/nulltest.sh Executable file
View File

@ -0,0 +1,6 @@
#!/bin/bash
# we cannot test this since there is no machine with QAT_4XXX hardware in Beaker as of now
# Intel promised us to provide OtherQA for qatlib, qatengine and QAT kernel patchsets
echo QATEngine nulltest is PASS
exit 0

10
tests/tests.yml Normal file
View File

@ -0,0 +1,10 @@
---
- hosts: localhost
roles:
- role: standard-test-basic
tags:
- classic
tests:
- nulltest:
dir: .
run: nulltest.sh