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/qatlib-23.11.0.tar.gz SOURCES/qatlib-*.tar.gz
/qatlib-*.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 (qatlib-23.11.0.tar.gz) = f6cdd0395dc43d0e9286b0ae9d30f10cf283e34077b67fb982cd376b5b1e26185d662a1e2b48ec3590997224908a42fa4cac59ad0fbe0e4c03e4dfce94fcea84

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=1725444#c31 for the details.
QATlib includes some sample codes that can be used to do a sanity check.
However they require a platform with QAT_4XXX. The sample codes reside now
in qatlib-tests package in CRB. You can use cpa_sample_code for a general
sanity test.

6
tests/nulltest.sh Executable file
View File

@ -0,0 +1,6 @@
#!/bin/bash
# we cannot the 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 QATLIB 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