stress/cpu_stress_ng_test hangs if the device tries to suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
Medium
|
Sylvain Pineau |
Bug Description
While testing two somerville platforms, I noticed the stress/
To reproduce:
1. On a device with suspend activated (Settings > Power > Automatic Suspend), start stress/
2. At the period set in the Automatic Suspend screen, the device tries to suspend.
3. From now on, the CPU stress test seems like it's running, but it will never complete and Checkbox cannot finish the testing session.
Workaround: Make sure Settings > Power > Automatic Suspend is set to OFF.
A solution could be to automatically deactivate suspend before starting this test, and automatically reactivate it after the test is finished, using those commands (see <https:/
# Deactivate suspend
gsettings set org.gnome.
gsettings set org.gnome.
# Reactivate suspend
gsettings set org.gnome.
gsettings set org.gnome.
It seems this issue only appear with stress/
I'm not sure how this would work on the server side, though...
Related branches
- Jeff Lane : Approve
- Jonathan Cave (community): Approve
-
Diff: 30 lines (+3/-3)2 files modifiedunits/memory/jobs.pxu (+1/-1)
units/stress/jobs.pxu (+2/-2)
- Sylvain Pineau (community): Needs Fixing
- Pierre Equoy: Pending requested
-
Diff: 73 lines (+35/-4)1 file modifiedbin/cpu_stress (+35/-4)
Changed in plainbox-provider-checkbox: | |
importance: | Undecided → Medium |
Changed in plainbox-provider-checkbox: | |
assignee: | nobody → Sylvain Pineau (sylvain-pineau) |
importance: | Medium → High |
tags: | added: ce-qa-concern |
Changed in plainbox-provider-checkbox: | |
milestone: | none → 0.50.0 |
assignee: | Sylvain Pineau (sylvain-pineau) → nobody |
Changed in plainbox-provider-checkbox: | |
assignee: | nobody → Jonathan Cave (jocave) |
Changed in plainbox-provider-checkbox: | |
status: | New → In Progress |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Confirmed |
assignee: | Jonathan Cave (jocave) → nobody |
Changed in plainbox-provider-checkbox: | |
importance: | High → Medium |
milestone: | 0.50.0 → none |
Changed in plainbox-provider-checkbox: | |
assignee: | nobody → Sylvain Pineau (sylvain-pineau) |
milestone: | none → 0.56.0 |
status: | Confirmed → In Progress |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
I would suggest to use inhibit API[1] to suppress the suspend with the user session, so the test script would not mess around the user settings. The inhibit API should only apply to the machine that are running Desktop.
Since the session is running under the specific Xorg instance. The checkbox should be aware of the DISPLAY environment and pass it to each test job. The dbus-launch command will create yet another user session, which is not something you want to do.
Since the cpustress test can be used on both core and Desktop, I think it's better to have the inhibit as it's own job, and only apply to the desktop environment.
[1] https:/ /github. com/GNOME/ gnome-settings- daemon/ blob/GNOME_ SETTINGS_ DAEMON_ 3_28_0/ gnome-settings- daemon/ org.gnome. SessionManager. xml#L102