[Bug 1181479] New: LLVM 11 can not be built because of a kernel or hardware problem
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479 Bug ID: 1181479 Summary: LLVM 11 can not be built because of a kernel or hardware problem Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: sarah.kriesch@ibm.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: OBS has got a failed build of LLVM 11 for s390x with the following message: [41008s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [41008s] or the build host has a kernel or hardware problem... Reproducible: Always Steps to Reproduce: see: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/... Actual Results: faild builds of LLVM11 because of a kernel or hardware problem on the base system (the VM) Expected Results: successful builds of LLVM11 in the OBS -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
Sarah Julia Kriesch
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c1
--- Comment #1 from Ruediger Oertel
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c2
Aaron Puchert
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/...
Checked the link right now, and the latest build was successful, also the history shows the previous build as the only failing build. (In reply to Ruediger Oertel from comment #1)
so a VM with 12G memory gets stuck with 6 jobs. might be a compiler bug or the processes really get large enough to stall the machine due to memory pressure. these are already the largest worker instances we run, so you might try with manually setting a different (lower) number of jobs in the specfile or similar.
Generally I would have gone with OOM, but 2G per job should be more than enough. Ninja's job pools are strange, so we could have up to 5 compile jobs plus 1 ThinLTO link job running at the same time. But even that is unlikely to consume something remotely close to 12G. Though a ThinLTO job being involved is likely: this is pretty late in the build, and while the compiler itself is single-threaded, so whatever it does is pretty well reproducible, ThinLTO jobs are multi-threaded. So it could be a deadlock, but also a race condition if s390x has weaker memory ordering than x86. (Which it likely has, x86 is pretty constrained.) So there could be a bug, but unless we can observe this live there is too little to go on I think. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c3
--- Comment #3 from Aaron Puchert
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c4
Sarah Kriesch
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c5
--- Comment #5 from Aaron Puchert
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c6
--- Comment #6 from Aaron Puchert
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
Aaron Puchert
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479
http://bugzilla.opensuse.org/show_bug.cgi?id=1181479#c7
--- Comment #7 from Sarah Kriesch
participants (1)
-
bugzilla_noreply@suse.com