action #177072
closed[security] audit_remote takes long time to run, find ways to reduce it
100%
Description
Note¶
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
The test often fails 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
Last good: 20250210-1 (or more recent)
Always latest result in this scenario: latest
Acceptance Criteria¶
- Find a way to remove the timeout failure
- Find also if there are ways to reduce the overall execution time in case of passing run
Updated by tjyrinki_suse 27 days ago
- Tags set to optimization, study
- Subject changed from [security] audit_remote takes long time to run to [security] audit_remote takes long time to run, find ways to reduce it
- Description updated (diff)
- Status changed from New to Workable
- Start date deleted (
2025-02-12) - Estimated time set to 16.00 h
Updated by tjyrinki_suse 27 days ago
- Has duplicate action #175317: [security][15-SP5][s390x] test fails in audit_remote added
Updated by amanzini 21 days ago
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.
Updated by tjyrinki_suse 4 days ago
- Copied to action #178783: [security] audit_remote (still) times out / stalls on s390x at times, find ways to reduce it added
Updated by tjyrinki_suse 4 days ago
- Status changed from Feedback to Resolved
It works as intended, still time outs even with the smaller bits but at least something has been tried! Low priority ticket #178783 created as a follow-up.