You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rust-lang/libc#1235 added an integration test with the test harness enabled. It's libc's first integration test that uses the test harness, and it's hanging on s390x even though there are no tests enabled for that architecture. @gnzlbg thinks that the bug might lie in rustc, not QEMU.
After more investigation, this looks like a QEMU issue. At least, QEMU doesn't spit out enough information to prove otherwise. The qemu process core dumps before it prints anything Rust-related.
Activity
nagisa commentedon Feb 4, 2019
I think it is a QEMU issue. At least I think there is a build of s390x rustc done on real hardware for I think debian.
gnzlbg commentedon Feb 4, 2019
@asomers same here as with the #58148 issue. It might be worth it to try to find if there is a qemu bug open upstream, and if not, fill one.
asomers commentedon Feb 5, 2019
After more investigation, this looks like a QEMU issue. At least, QEMU doesn't spit out enough information to prove otherwise. The qemu process core dumps before it prints anything Rust-related.
greg5678 commentedon Mar 27, 2019
If you want to try Rust on an x390x system you can request access here.
gnzlbg commentedon Mar 27, 2019
The problem is more all the work required to set up that in CI, than getting access itself.