-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some stressors of stress-ng will always fail #800
Comments
The stressor
|
commit a650e32db690a6c63b7e08e7fd3fbb96545018b7
Probably worth reaching out to Colin and asking why he removed that. |
After reaching out to Colin, this is the feedback from Colin:
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1077.
|
I've created #1173 to ignore the stressors that would be marked as "disabled" by stress-ng. |
Me and @stanley31huang found that the latest verstion of stress-ng fixes this issue which means that return code is 0.
|
I built checkbox snap with stress-ng v0.17.07. All jobs are passed now (except something are crashed). |
Fixed by #1425, now stress-ng comes from maintainer's PPA (ppa: colin-king/stress-ng) |
Bug Description
We discovered that certain stressors in stress-ng would consistently fail due to being disabled by default, resulting in an exit code of 1. This situation caused the test job to fail, even though the stressor was not executed. But seems the latest version of stress-ng has resolved this issue.
However, we've noticed that stress-ng no longer supports the SNAP version. The stress-ng snap is no longer on the snap store and the snapcraft.yaml file has been removed from the git repo. This raises concerns about stress-ng's suitability for the UC environment.
For X86 platform:
https://certification.canonical.com/hardware/202310-32151/submission/339803/test-results/fail/
bad-ioctl
bind-mount
mlockmany
oom-pipe
sysinval
watchdog
For ARM64 platform:
https://certification.canonical.com/hardware/202304-31535/submission/326256/test-results/fail/?term=stressor
bind-mount
cpu-online
mlockmany
oom-pipe
smi
sysinval
watchdog
To Reproduce
$ sudo checkbox.shell
$ stress-ng --watchdog 0 --timeout 30 --skip-silent --verbose
Environment
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: