For the record, the best way to get the desired behavior is by installing fwts before running checkbox, we recommend this as fwts does more thorough testing and diagnostics.
That said, we did find an oversight in how the log file is generated. The sleep 30 cycles test has this in the part where it invokes sleep_test, in absence of fwts:
set -o pipefail; sleep_test -p s mem -i 30 | tee $CHECKBOX_DATA/suspend_30_cycles_times.log
However, hibernate 30 cycles has only this:
sleep_test -s disk -i 30 -w 120
The same thing happens with the 250-cycle variants. I'll propose a fix for this in a moment.
For the record, the best way to get the desired behavior is by installing fwts before running checkbox, we recommend this as fwts does more thorough testing and diagnostics.
That said, we did find an oversight in how the log file is generated. The sleep 30 cycles test has this in the part where it invokes sleep_test, in absence of fwts:
set -o pipefail; sleep_test -p s mem -i 30 | tee $CHECKBOX_ DATA/suspend_ 30_cycles_ times.log
However, hibernate 30 cycles has only this:
sleep_test -s disk -i 30 -w 120
The same thing happens with the 250-cycle variants. I'll propose a fix for this in a moment.