14228 2021-02-09 00:44:49 +0000 valgrind ptest failing on qemuarm64 2021-03-04 16:30:20 +0000 1 1 10 QA/Testing Package Testing (ptest) ptest 3.3 Other arm64 RESOLVED FIXED AB-INT Medium+ normal 3.3 M3 1 flowergom yf3yu alexandre.belloni Jagadheesan_Duraisamy randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 89169 0 flowergom 2021-02-09 00:44:49 +0000 https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1503/steps/12/logs/stdio Traceback (most recent call last): File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 25, in test_ptestrunner_expectfail self.do_ptestrunner() File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 112, in do_ptestrunner self.fail(failmsg) AssertionError: Failed ptests: {'valgrind': ['drd/tests/std_list']} Cannot run ptests without @expectedFailure as ptests are expected to fail RESULTS: RESULTS - ping.PingTest.test_ping: PASSED (0.16s) RESULTS - ssh.SSHTest.test_ssh: PASSED (0.30s) RESULTS - ptest.PtestRunnerTest.test_ptestrunner_expectsuccess: SKIPPED (0.00s) RESULTS - ptest.PtestRunnerTest.test_ptestrunner_expectfail: EXPECTEDFAIL (12180.10s) SUMMARY: 89173 1 flowergom 2021-02-09 01:08:39 +0000 This issue happened again: https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1511/steps/12/logs/stdio WARNING: core-image-sato-sdk-ptest-1.0-r0 do_testimage: There were failing ptests. Traceback (most recent call last): File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 25, in test_ptestrunner_expectfail self.do_ptestrunner() File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 112, in do_ptestrunner self.fail(failmsg) AssertionError: Failed ptests: {'valgrind': ['drd/tests/std_list']} 89317 2 Jagadheesan_Duraisamy 2021-02-19 11:34:32 +0000 Happened again in: https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1542/steps/12/logs/stdio 89326 3 Jagadheesan_Duraisamy 2021-02-19 18:42:52 +0000 Seen in https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1534/steps/12/logs/stdio 89341 4 yf3yu 2021-02-22 20:49:48 +0000 noticing that valgrind ptest runs pretty slow on qemuarm compared the x86-64 kvm . on a local test (also a pretty heavily loaded server building chromium), many tests fail due to timeout. will increase the timeout to see if this specific test fails again 89350 5 yf3yu 2021-02-23 15:14:48 +0000 this specific test `drd/tests/std_list` takes around 47s with glibc2.33 timeout on all tests is 30s. could consider bumping up the timeout to 60s but from experience this doesn't scale well since the autobuilder could have a much heavier load 89370 6 yf3yu 2021-02-24 19:33:33 +0000 drd/tests/std_list takes around 45s on my system to run (its pretty consistent) same thing with glibc2.32 Proposing just bumping timeout to 90s to remove the possible noise 89371 7 randy.macleod 2021-02-24 19:38:01 +0000 Sure a 90 second timeout for valgrind seems reasonable. 89372 8 yf3yu 2021-02-24 19:46:46 +0000 Side note: Tested with increased timeout and the following tests (not reported by AB) fail on qemuarm64 building a core-image-minimal with ptest only for valgrind FAIL: memcheck/tests/linux/timerfd-syscall FAIL: massif/tests/new-cpp FAIL: massif/tests/overloaded-new 89432 9 alexandre.belloni 2021-02-27 01:52:19 +0000 More of {'valgrind': ['drd/tests/std_list']} https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1564/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1559/steps/12/logs/stdio 89447 10 alexandre.belloni 2021-03-01 00:04:34 +0000 https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1562/steps/12/logs/stdio 89479 11 yf3yu 2021-03-02 21:59:09 +0000 sent a server-side patch http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/commit/?id=178da5ccf6154ecf5968261a16bd245971b909cf might also change the MACHINE=False to MACHINE=Unknown 89499 12 yf3yu 2021-03-04 16:30:20 +0000 (In reply to comment #11) > sent a server-side patch > http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/commit/ > ?id=178da5ccf6154ecf5968261a16bd245971b909cf > > might also change the MACHINE=False to MACHINE=Unknown ignore this... wrong bug Resolved : timeout is increased https://git.openembedded.org/openembedded-core/commit/?id=aac00b1c8042e41cd6bb1aea8e3033a1c6dd2b05