Hello,
This honestly looks like an infrastructure issue. How loaded are your workers when running this test? Also, I'm not sure how good is the rtc emulation in qemu (which is a good part of what is being tested here).
On 07/03/2023 12:47:50+0530, Naresh Kamboju wrote:
kselftest: rtc built with clang-16 getting failed but passed with gcc-12 build. Please find more details about test logs on clang-16 and gcc-12 and steps to reproduce locally on your machine by using tuxrun.
On the qemu-x86-64 clang builds it is intermittent failure; you could notice that from the test history link below.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Test log:
Linux version 6.3.0-rc1-next-20230307 (tuxmake@tuxmake) (Debian clang version 16.0.0 (++20230228093516+60692a66ced6-1~exp1~20230228093525.41), Debian LLD 16.0.0) #1 SMP PREEMPT @1678159722 ... kselftest: Running tests in rtc TAP version 13 1..1 # selftests: rtc: rtctest # TAP version 13 # 1..8 # # Starting 8 tests from 1 test cases. # # RUN rtc.date_read ... # # rtctest.c:54:date_read:Current RTC date/time is 07/03/2023 03:55:04. # # OK rtc.date_read # ok 1 rtc.date_read # # RUN rtc.date_read_loop ... # # rtctest.c:96:date_read_loop:Continuously reading RTC time for 30s (with 11ms breaks after every read). # # rtctest.c:122:date_read_loop:Performed 2630 RTC time reads. # # OK rtc.date_read_loop # ok 2 rtc.date_read_loop # # RUN rtc.uie_read ... # # OK rtc.uie_read # ok 3 rtc.uie_read # # RUN rtc.uie_select ... # # OK rtc.uie_select # ok 4 rtc.uie_select # # RUN rtc.alarm_alm_set ... # # rtctest.c:222:alarm_alm_set:Alarm time now set to 03:55:44. # # rtctest.c:241:alarm_alm_set:data: 1a0 # # OK rtc.alarm_alm_set # ok 5 rtc.alarm_alm_set # # RUN rtc.alarm_wkalm_set ... # # rtctest.c:284:alarm_wkalm_set:Alarm time now set to 07/03/2023 03:55:47. # # rtctest.c:290:alarm_wkalm_set:Expected -1 (-1) != rc (-1) # # alarm_wkalm_set: Test terminated by assertion # # FAIL rtc.alarm_wkalm_set # not ok 6 rtc.alarm_wkalm_set # # RUN rtc.alarm_alm_set_minute ... # # rtctest.c:332:alarm_alm_set_minute:Alarm time now set to 03:56:00. # # rtctest.c:351:alarm_alm_set_minute:data: 1a0 # # OK rtc.alarm_alm_set_minute # ok 7 rtc.alarm_alm_set_minute # # RUN rtc.alarm_wkalm_set_minute ... # # rtctest.c:394:alarm_wkalm_set_minute:Alarm time now set to 07/03/2023 03:57:00. # # rtctest.c:400:alarm_wkalm_set_minute:Expected -1 (-1) != rc (-1) # # alarm_wkalm_set_minute: Test terminated by assertion # # FAIL rtc.alarm_wkalm_set_minute # not ok 8 rtc.alarm_wkalm_set_minute # # FAILED: 6 / 8 tests passed. # # Totals: pass:6 fail:2 xfail:0 xpass:0 skip:0 error:0
Links,
qemu-x86_64:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230306/tes...
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230306/tes...
qemu-arm64:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230307/tes...
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230307/tes...
Test history:
Test log:
Linux version 6.3.0-rc1-next-20230307 (tuxmake@tuxmake) (aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT @1678159736 ... kselftest: Running tests in rtc TAP version 13 1..1 # selftests: rtc: rtctest # TAP version 13 # 1..8 # # Starting 8 tests from 1 test cases. # # RUN rtc.date_read ... # # rtctest.c:52:date_read:Current RTC date/time is 07/03/2023 03:48:22. # # OK rtc.date_read # ok 1 rtc.date_read # # RUN rtc.date_read_loop ... # # rtctest.c:95:date_read_loop:Continuously reading RTC time for 30s (with 11ms breaks after every read). # # rtctest.c:122:date_read_loop:Performed 2670 RTC time reads. # # OK rtc.date_read_loop # ok 2 rtc.date_read_loop # # RUN rtc.uie_read ... # # OK rtc.uie_read # ok 3 rtc.uie_read # # RUN rtc.uie_select ... # # OK rtc.uie_select # ok 4 rtc.uie_select # # RUN rtc.alarm_alm_set ... # # rtctest.c:221:alarm_alm_set:Alarm time now set to 03:49:02. # # rtctest.c:241:alarm_alm_set:data: 1a0 # # OK rtc.alarm_alm_set # ok 5 rtc.alarm_alm_set # # RUN rtc.alarm_wkalm_set ... # # rtctest.c:281:alarm_wkalm_set:Alarm time now set to 07/03/2023 03:49:05. # # OK rtc.alarm_wkalm_set # ok 6 rtc.alarm_wkalm_set # # RUN rtc.alarm_alm_set_minute ... # # rtctest.c:331:alarm_alm_set_minute:Alarm time now set to 03:50:00. <47>[ 106.383091] systemd-journald[98]: Sent WATCHDOG=1 notification. # # rtctest.c:351:alarm_alm_set_minute:data: 1a0 # # OK rtc.alarm_alm_set_minute # ok 7 rtc.alarm_alm_set_minute # # RUN rtc.alarm_wkalm_set_minute ... # # rtctest.c:391:alarm_wkalm_set_minute:Alarm time now set to 07/03/2023 03:51:00. # # OK rtc.alarm_wkalm_set_minute # ok 8 rtc.alarm_wkalm_set_minute # # PASSED: 8 / 8 tests passed. # # Totals: pass:8 fail:0 xfail:0 xpass:0 skip:0 error:0 ok 1 selftests: rtc: rtctest
Links, qemu-x86_64:
qemu-arm64:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230307/tes...
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230307/tes...
Steps to reproduce:
# To install tuxrun on your system globally: # sudo pip3 install -U tuxrun==0.37.2 # # See https://tuxrun.org/ for complete documentation.
tuxrun \ --runtime podman \ --device qemu-x86_64 \ --boot-args rw \ --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2McWP6obiL1x51zgkgLXR... \ --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2McWP6obiL1x51zgkgLXR... \ --rootfs https://storage.tuxboot.com/debian/bookworm/amd64/rootfs.ext4.xz \ --parameters SKIPFILE=skipfile-lkft.yaml \ --parameters KSELFTEST=https://storage.tuxsuite.com/public/linaro/lkft/builds/2McWP6obiL1x51zgkgLXR... \ --image docker.io/lavasoftware/lava-dispatcher:2023.01.0020.gc1598238f \ --tests kselftest-rtc \ --timeouts boot=15
-- Linaro LKFT https://lkft.linaro.org