https://autobuilder.yoctoproject.org/typhoon/#/builders/154/builds/271/steps/12/logs/stdio qemumips fedora37-ty-2 https://autobuilder.yoctoproject.org/typhoon/#/builders/154/builds/278/steps/13/logs/stdio qemumips64-tc ubuntu2204-ty-3 2023-07-29 01:22:56,015 - oe-selftest - INFO - ====================================================================== 2023-07-29 01:22:56,016 - oe-selftest - INFO - FAIL: rust.RustSelfTestSystemEmulated.test_rust (subunit.RemotedTestCase) 2023-07-29 01:22:56,016 - oe-selftest - INFO - ---------------------------------------------------------------------- 2023-07-29 01:22:56,016 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/qemumips64-tc/build/meta/lib/oeqa/selftest/cases/rust.py", line 83, in test_rust runCmd(cmd) File "/home/pokybuild/yocto-worker/qemumips64-tc/build/meta/lib/oeqa/utils/commands.py", line 212, in runCmd raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output)) AssertionError: Command ' export PATH=/home/pokybuild/yocto-worker/qemumips64-tc/build/build-st-1931533/tmp/work/mips64r2-poky-linux/rust/1.70.0-r0/recipe-sysroot-native/usr/bin:$PATH; export TARGET_VENDOR="-poky"; export PATH=/home/pokybuild/yocto-worker/qemumips64-tc/build/build-st-1931533/tmp/work/mips64r2-poky-linux/rust/1.70.0-r0/recipe-sysroot-native/usr/bin/mips64-poky-linux:/home/pokybuild/yocto-worker/qemumips64-tc/build/build-st-1931533/tmp/hosttools:$PATH; export RUST_TARGET_PATH=/home/pokybuild/yocto-worker/qemumips64-tc/build/build-st-1931533/tmp/work/mips64r2-poky-linux/rust/1.70.0-r0/rust-targets; export TEST_DEVICE_ADDR="192.168.7.2:12345"; cd /home/pokybuild/yocto-worker/qemumips64-tc/build/build-st-1931533/tmp/work/mips64r2-poky-linux/rust/1.70.0-r0/rustc-1.70.0-src; python3 src/bootstrap/bootstrap.py test --exclude tests/rustdoc --exclude src/tools/rust-analyzer --exclude tests/rustdoc-json --exclude tests/run-make-fulldeps --exclude src/tools/tidy --exclude src/tools/rustdoc-themes --exclude src/rustdoc-json-types --exclude src/librustdoc --exclude src/doc/unstable-book --exclude src/doc/rustdoc --exclude src/doc/rustc --exclude compiler/rustc --exclude library/panic_abort --exclude library/panic_unwind --exclude src/tools/lint-docs --exclude tests/rustdoc-js-std --doc --no-fail-fast --bless --target mips64-poky-linux-gnu > summary.txt 2>&1;' returned non-zero exit status 1:
If the test fails, please cat summary.txt so that the data is available.
*** Bug 15187 has been marked as a duplicate of this bug. ***
https://autobuilder.yoctoproject.org/typhoon/#/builders/154/builds/278/steps/13/logs/stdio qemumips64-tc opensuse154-ty-3
https://autobuilder.yoctoproject.org/typhoon/#/builders/154/builds/451/steps/12/logs/stdio qemumips64-tc debian11-ty-3
https://autobuilder.yoctoproject.org/typhoon/#/builders/153/builds/433/steps/12/logs/stdio qemuppc-tc ubuntu2004-ty-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/147/builds/851/steps/12/logs/stdio qemumips-tc ubuntu2304-ty-1
Are these issues still there after the latest patch series sent for rust oe-selftest? The patch series was checked on Ubuntu 22.04.
Yash, this build from Feb 2024 seems to be after your last comment so the problem is still happening: https://autobuilder.yoctoproject.org/typhoon/#/builders/154/builds/1366
In the last log the AssertionError: line is wrapped as 4096 bytes where a character also disappears and is replaced with a newline: tests/ui/asso iated-type-bounds/fn-dyn-apit.rs 4096 is a suspicious number.
Sundeep, Add a comment explaining where we are with this bug, please.
qemuppc-tc ubuntu2004-vk-1 https://valkyrie.yoctoproject.org/#/builders/49/builds/263/steps/12/logs/stdio
We have disabled the mips32/64 rust tests since those arches are not being supported on master by anyone and the upstream rust stopped supported these tests or the mips arches really. ppc32 is being worked on by people in YP (less so by Rust upstream)...
qemuarm64-tc ubuntu2004-vk-2 https://valkyrie.yoctoproject.org/#/builders/5/builds/281/steps/12/logs/stdio qemuarm64-tc ubuntu2404-vk-2 https://valkyrie.yoctoproject.org/#/builders/5/builds/294/steps/12/logs/stdio
Working on reproducing the issue but not yet reproduced on my side.
Bulk move.
qemuarm64-tc debian11-vk-1 mathieu/master-next completed at 2025-01-17T08:14:20Z https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/806/steps/12/logs/stdio
Moving to 5.2-M4 to give us time to see if there is actually a requirement to support powerpc. YP has disabled the powerpc tests.
Hi all, For tests/ui/process/process-sigpipe.rs testcase failure is fixed with below commit https://git.openembedded.org/openembedded-core/commit?h=master&id=fb19e038582a2bfc414465ef396c30197f67128f After the above fix, this testcase failure is not seen in AB. Regarding the failure of the tests/ui/threads-sendsync/tcp-stress.rs testcase in conf/local.conf, I set RUST_TEST_THREADS="96" as seen in the AB logs. The issue is not reproducible for both ARM64 and PPC32. Thanks, Deepesh
Not reported for 1.5 years so resolving as works for me. Not that YP also stopped testing ppc32 and mips32/64 so if you happen to have a requirement for these targets (with out without rust being involved), please discuss on the email list.
My comment about this not being seen for 1.5 years was wrong. Deepesh pointed to Adrian's timeout increase which seem to have helped. Still marking as resolved and unless someone re-opens we'll focus on targets other than ppc32, mips*.
qemuarm-tc rocky9-vk-3 master completed at 2025-05-05T01:51:31Z https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/1490/steps/12/logs/stdio
Mathieu, Is this really the same bug? This one happened for: build/x86_64-unknown-linux-gnu/stage1-std/armv7-poky-linux-gnueabihf/ and the first error in the log is: failures: ---- fs::tests::file_lock_drop stdout ---- thread 'fs::tests::file_lock_drop' panicked at library/std/src/fs/tests.rs:271:5: assertion failed: check!(f2.try_lock()) failures: fs::tests::file_lock_drop test result: FAILED. 1068 passed; 1 failed; 22 ignored; 0 measured; 0 filtered out; finished in 24.48s error: test failed, to rerun pass `-p std --lib`
Hum, yes, on second thought this might be a different one.
Mathieu, Richard asks that you create a new bug rather than re-open this one since it's an arm issue and the previous ones were mips/ppc and we're not testing them anymomre.