Closed pengshanyu closed 1 month ago
Add tmt test case for tool "test_sched_setscheduler" according to #365
Test result: out: Trying to pull quay.io/centos-sig-automotive/ffi-tools:latest... out: Getting image source signatures out: Writing manifest to image destination out: 8cd597972703900be2a0612d821a115b418f61ff4b1006e03b429724ec9b9035 out: [ INFO ] set_scheduler() syscall denied in QM. out: Shared connection to localhost closed. 00:02:29 pass /tests/ffi/deny_set_scheduler (on default-0) [1/1] summary: 1 test executed report how: junit order: 50 output: /var/tmp/tmt/run-002/plans/e2e/ffi/report/default-0/junit.xml summary: 1 test passed finish
In description always add resolve #issue_id this way once this PR is closed the issue will also be closed automatically
please explain what tests should do, Tests out puts are not necessary we have packit ffi gate for it
In description always add resolve #issue_id this way once this PR is closed the issue will also be closed automatically
please explain what tests should do, Tests out puts are not necessary we have packit ffi gate for it
Thanks for the advice. Updated.
/packit test
/packit test
Add tmt test case for tool "test_sched_setscheduler" to verify that QM environment deny set_scheduler() syscall
resolve #365