lp:~firmware-testing-team/fwts/master

Related source package recipes

2 recipes using this branch. (?)

Related snap packages

Related bugs

Related blueprints

5363. By Ivan Hu on 2025-10-27

acpi: ras2: fix the wrong feature type check

BugLink: https://bugs.launchpad.net/fwts/+bug/2127968

Should be the feature_type not reserved

Signed-off-by: Ivan Hu <email address hidden>

5362. By Al Korv <email address hidden> on 2025-10-27

fwts: skip the wake alarm suite if the feature is not implemented

The wake alarm may be not implemented on a non-x86 platform
thus the calls to the RTC alarm interface may legitimately
fail. Although the wake alarm test suite appears to antici-
pate this and skips the first test on a non-x86 platform if
fwts_wakealarm_get() fails the routine doesn't detect that
the wake alarm is not implemented thus the 1st test passes
and the remaining tests fail if it is the case. Here's an
excerpt from the FWTS results log obtained in such an envi-
ronmemnt:

 wakealarm: ACPI Wakealarm tests.
 ---------------------------------------------------------
 Test 1 of 5: Test existence of RTC with alarm interface.
 PASSED: Test 1, RTC with a RTC alarm ioctl() interface
 found.

 Test 2 of 5: Trigger wakealarm for 1 seconds in the future.
 Trigger wakealarm for 1 seconds in the future.
 Cannot enable alarm interrupts on Real Time Clock device
 /dev/rtc0.
 FAILED [MEDIUM] WakeAlarmNotTriggeredTest2: Test 2, RTC
 wakealarm did not trigger.

 Test 3 of 5: Test if wakealarm is fired.
 Cannot enable alarm interrupts on Real Time Clock device
 /dev/rtc0.
 FAILED [MEDIUM] WakeAlarmNotTriggeredTest3: Test 3, Failed
 to trigger and fire wakealarm.

 Test 4 of 5: Multiple wakealarm firing tests.
 Trigger wakealarm for 1 seconds in the future.
 Cannot enable alarm interrupts on Real Time Clock device
 /dev/rtc0.
 FAILED [MEDIUM] WakeAlarmNotTriggeredTest4: Test 4, Failed
 to trigger and fire wakealarm.

 Test 5 of 5: Reset wakealarm time.
 PASSED: Test 5, RTC wakealarm set.
 FAILED [MEDIUM] WakeAlarmNotResetTest5: Test 5, RTC wakealarm
 failed to be reset back to original time.

This happens because the routine fwts_framework_run_test() stops
performing the suite only if its test returns FWTS_ABORTED or its
init callback returns FWTS_SKIP while neither is the case here.

The patch fixes the issue by adjusting the routines wakealarm_
test[2-5]() to return FWTS_SKIP if the 1st test is skipped.

The wakealarm suite report looks as follows after the patch
is applied:

 wakealarm: ACPI Wakealarm tests.
 ------------------------------------------------------------
 Test 1 of 5: Test existence of RTC with alarm interface.
 The wake alarm is not supported.
 non-x86 devices sometimes do not have an RTC wake alarm that
 is normally controlled by the RTC alarm ioctl() interface.
 This interface does not exist, so the wake alarm tests will
 be skipped.

 Test 2 of 5: Trigger wakealarm for 1 seconds in the future.

 Test 3 of 5: Test if wakealarm is fired.

 Test 4 of 5: Multiple wakealarm firing tests.

 Test 5 of 5: Reset wakealarm time.

Signed-off-by: Al Korv <email address hidden>
Acked-by: Ivan Hu <email address hidden>

5361. By Ivan Hu on 2025-09-30

lib: fwts_version.h - update to V25.09.00

Signed-off-by: Ivan Hu <email address hidden>

5360. By Ivan Hu on 2025-09-30

debian: update changelog

Signed-off-by: Ivan Hu <email address hidden>

5359. By Ivan Hu on 2025-09-30

auto-packer: mkpackage.sh: use the github tag source directly

Use the tar.gz file from the GitHub tag as the release source,
instead of creating a new tarball.

Signed-off-by: Ivan Hu <email address hidden>

5358. By Ivan Hu on 2025-09-25

wakealarm: skip the reset check when RTC time earlier than current system time

BugLink: https://bugs.launchpad.net/fwts/+bug/2121796

When using RTC_ALM_SET, the kernel forces the alarm to use the current
day/month/year and will wrap it into the next day if the requested time
is earlier than the current system time. This causes wakealarm_test5 to
fail. Skip this case when encountering an earlier RTC setting.

Signed-off-by: Ivan Hu <email address hidden>

5357. By Weizhao Ouyang on 2025-09-25

smccc_test: remove deprecated no_llseek to fix the compilation error

Signed-off-by: Weizhao Ouyang <email address hidden>
Acked-by: Ivan Hu <email address hidden>

5356. By Ivan Hu on 2025-09-18

fwts-test: add regression tests for MSCT

Signed-off-by: Ivan Hu <email address hidden>

5355. By Ivan Hu on 2025-09-18

acpi: msct: fix incorrect length check on max proximity domains

Buglink: https://bugs.launchpad.net/fwts/+bug/2121792

The total length should be checked for whether exceeding the maximum
possible proximity domain included rather than checking if it is
shorter.

Signed-off-by: Ivan Hu <email address hidden>

5354. By Ivan Hu on 2025-08-28

smccc: move the smccc folder out of pci

The smccc tests are no longer limited to the PCI features.
Move them out of the PCI folder.

Signed-off-by: Ivan Hu <email address hidden>