Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ppc64 builds are failing lock torture tests #1031

Closed
nickdesaulniers opened this issue May 20, 2020 · 1 comment
Closed

ppc64 builds are failing lock torture tests #1031

nickdesaulniers opened this issue May 20, 2020 · 1 comment
Labels
[ARCH] powerpc This bug impacts ARCH=powerpc [BUG] qemu A bug that should be fixed in upstream QEMU

Comments

@nickdesaulniers
Copy link
Member

nickdesaulniers commented May 20, 2020 •
edited

I noticed the CI was red again.
I emailed MPE about this.
https://groups.google.com/g/clang-built-linux/c/6W3Ee6PByyg
@nickdesaulniers nickdesaulniers added [ARCH] powerpc This bug impacts ARCH=powerpc [BUG] Untriaged Something isn't working Reported upstream This bug was filed on LLVM’s issue tracker, Phabricator, or the kernel mailing list. labels May 20, 2020
@nathanchance
Copy link
Member

Fixed on the CI side by ClangBuiltLinux/continuous-integration@6137298.

This has been resolved with QEMU 5.0.0 (ClangBuiltLinux/continuous-integration#262 and qemu/qemu@5ed1950), we just do not have access to it without building it in our Docker image, which I am not particularly interested in doing.

@nathanchance nathanchance added [BUG] qemu A bug that should be fixed in upstream QEMU and removed Reported upstream This bug was filed on LLVM’s issue tracker, Phabricator, or the kernel mailing list. [BUG] Untriaged Something isn't working labels Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[ARCH] powerpc This bug impacts ARCH=powerpc [BUG] qemu A bug that should be fixed in upstream QEMU
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nickdesaulniers @nathanchance