Your message dated Thu, 31 Aug 2023 10:32:27 +0100 with message-id <[email protected]> and subject line stress-ng: flaky autopkgtest has caused the Debian Bug report #1001666, regarding stress-ng: flaky autopkgtest to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1001666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001666 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: stress-ng Version: 0.13.08-1 Severity: important X-Debbugs-Cc: [email protected] The autopkgtests of stress-ng fail from time to time: | stress-ng: 20:49:12.58 info: [1091] unsuccessful run completed in 0.51s | stress-ng: 20:49:12.58 fail: [1091] cache instance 3 corrupted bogo-ops counter, 2 vs 0 | stress-ng: 20:49:12.58 fail: [1091] cache instance 3 hash error in bogo-ops counter and run flag, 796547380 vs 0 | stress-ng: 20:49:12.58 fail: [1091] metrics-check: stressor metrics corrupted, data is compromised | cache FAILED ... | zlib PASSED | 42 PASSED | 1 FAILED, cache | 0 SKIPPED See https://ci.debian.net/data/autopkgtest/testing/amd64/s/stress-ng/17550292/log.gz for a recent failure Cheers -- Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message --- The tests are indeed problematic, they also cause excess stress test loading on the systems running the tests. I'm re-thinking how to re-write the testing so that the core stress-ng functionality is tested without stressing the test system. I disabled these tests a while ago and so I'm marking this issue as closed. I will add more stable tests in some future release of stress-ng.
--- End Message ---
