Skip to content

s390x-unknown-linux-gnu hangs in QEMU #58149

Closed

Description

@asomers

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.

Activity

  1. nagisa commented on Feb 4, 2019

    @nagisa
    Member

    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.

  2. gnzlbg commented on Feb 4, 2019

    @gnzlbg
    Contributor

    @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.

  3. asomers commented on Feb 5, 2019

    @asomers
    ContributorAuthor

    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.

  4. greg5678 commented on Mar 27, 2019

    @greg5678

    If you want to try Rust on an x390x system you can request access here.

  5. gnzlbg commented on Mar 27, 2019

    @gnzlbg
    Contributor

    The problem is more all the work required to set up that in CI, than getting access itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    O-SystemZTarget: SystemZ processors (s390x)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions