QA (public) » openQA Project (public) » openQA Tests (public)

The test often used to fail with a time out: openQA test in scenario sle-15-SP6-Server-DVD-Updates-s390x-cc_audit_remote_client@s390x-kvm fails in
audit_remote

This was improved by ticket #177072 but regardless even the smaller bits claim time outs: https://openqa.suse.de/tests/16960715#step/audit_remote/274

Additionally, investigate about possible solutions to reduce time spent on this test; on a successful run on s390x it takes well over an hour, consuming worker resources and sometimes preventing also urgent updates to be released. On other archs the total execution time is a bit shorter but still near to ~1h

Acceptance Criteria¶

1. Find ways to remove or reduce the timeout failures
2. Find also if there are ways to reduce the overall execution time in case of passing run

Further Information¶

From the another ticket:

The tests are run from a collection of bash scripts, took from https://gitlab.suse.de/security/audit-test-sle15/-/archive/master/audit-test-sle15-master.tar

there are currently ~77 of them for audit-remote. Each test requires audit log rotation, so most likely they cannot be executed in parallel.

What we can do to add more responsiveness is to run each test with a for-loop, so openQA will "see" many small executions instead of one big that takes ~45 minutes, reducing in this way the chance of timeout.