Some machines failed in stress-ng test on hirsute

[Kevin Yeh]

We started running SRU testing on hirsute this SRU cycle.
I just found that some machine will fail in cpu_stress_ng_test test case.
In this test case, it will execute stress-ng with stressor like following:
"stress-ng --aggressive --verify --timeout 60 --metrics-brief --tz --times --af-alg 0 --bsearch 0 --context 0 --cpu 0 --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 --matrix 0 --qsort 0 --str 0 --stream 0 --tsearch 0 --vecmath 0 --wcs 0"

I used deb version of stress-ng(0.12.06), there wasn't any error message printed, I checked by echo $? and got 2, so the test will failed.
If I use snap version of stress-ng(0.12.09), it will print error messages and indicate that "stress-ng-af-alg: socket failed, errno=13 (Permission denied)", even I ran with sudo.

If I run without stressor --af-alg then it will pass and got 0 by echo $?.

We've run same test on different machines, only some of them will fail, and those failed machine can pass this test on focal, bionic, groovy.

Following are CIDs which fail in cpu_stress_test
202001-27665:Dell Precision 5550 https://certification.canonical.com/hardware/202001-27665/
201907-27241:Dell Inspiron 3593 https://certification.canonical.com/hardware/201907-27241/
202004-27811:Dell Precision 7550 https://certification.canonical.com/hardware/202004-27811/

Please help to take a look, thanks.

[Kevin Yeh (kevinyeh)]

Does anyone here could give me some feedback about this bug?
This failure continuously happen in SRU testing on 5.11 kernel.

[Colin Ian King (colin-king)]

The failure is because of the snap confinement being used on this older version. I believe newer versions of the stress-ng snap have this now fixed.

This bug is filed against Ubuntu 21.04 (Hirsute Hippo), this release reached End of Life on January 20 2022. Marking this as fixed released.