"Could not determine time to resume" when running s3 tests

[Pierre Equoy]

(This issue was originally opened in Colin King's FWTS repo on Github <https://github.com/ColinIanKing/fwts/issues/8>, but it seems it's not the right place to do so, so reposting here)

Hello!

We use fwts to test, among other things, the time taken by the device to suspend and resume.

We use fwts V22.03.00 on Ubuntu 22.04.

For a little while now, it seems fwts is having troubles to find the resume times.

Steps to reproduce

sudo fwts -q --stdout-summary --s3-device-check --s3-sleep-delay 30 s3

Output (abstract, full output attached in results.log)

-------------------
Requesting Suspend action
Skipping the minimum delay (0) and using a 3 seconds delay instead
s2idle duration = 31.
pm-action returned 0 after 31 seconds.
Suspend/Resume Timings:
  Suspend: 0.693 seconds.
  Could not determine time to resume.
Completed s2idle cycle(s)
-------------------

I tried to install the latest version of fwts using snap, but it fails:

-------------------
$ sudo snap run fwts -q --stdout-summary --s3-device-check --s3-sleep-delay 30 s3
/snap/fwts/863/usr/local/bin/fwts: Cannot open results log 'results' (you may need to remove it to set proper permissions).

$ sudo snap run fwts -q --stdout-summary --s3-device-check --s3-sleep-delay 30 s3 -r stdout
Results generated by fwts: Version V22.11.00 (2022-11-21 07:34:15).

Some of this work - Copyright (c) 1999 - 2021, Intel Corp. All rights reserved.
Some of this work - Copyright (c) 2010 - 2021, Canonical.
Some of this work - Copyright (c) 2016 - 2021, IBM.
Some of this work - Copyright (c) 2017 - 2021, ARM Ltd.

This test run on 11/01/23 at 21:51:06 on host Linux ubuntu 6.0.0-9009-oem #9+exp.27-Ubuntu SMP PREEMPT_DYNAMIC Tue Dec 20 08:55:30 UTC 202 x86_64.

Command: "fwts -q --stdout-summary --s3-device-check --s3-sleep-delay 30 -r stdout s3".
Running tests: s3.

s3: Sleep suspend/resume test.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Cannot access Real Time Clock device /dev/rtc0.
Cannot automatically wake machine up - aborting Sleep test.
FAILED [MEDIUM] BadWakeAlarmSleep: Test 1, Check if wakealarm works reliably for Sleep tests.
Aborted test, initialisation failed.
===================================================================================================================================================================================================================
0 passed, 0 failed, 0 warning, 1 aborted, 0 skipped, 0 info only.
===================================================================================================================================================================================================================
ABORTED

0 passed, 0 failed, 0 warning, 1 aborted, 0 skipped, 0 info only.

Test Failure Summary
===================================================================================================================================================================================================================

Critical failures: NONE

High failures: NONE

Medium failures: 1
 s3: Check if wakealarm works reliably for Sleep tests.

Low failures: NONE

Other failures: NONE

Test |Pass |Fail |Abort|Warn |Skip |Info |
---------------+-----+-----+-----+-----+-----+-----+
s3 | | | 1| | | |
---------------+-----+-----+-----+-----+-----+-----+
Total: | 0| 0| 1| 0| 0| 0|
---------------+-----+-----+-----+-----+-----+-----+
-------------------

[Ivan Hu (ivan.hu)]

The fix patch was included in fwts version 23.01.00,

https://lists.ubuntu.com/archives/fwts-devel/2022-November/013569.html