Ulrich Weigand/Germany/IBM wrote on 14.04.2016 18:20:20: > So there seem to be at least two different issues, looking at the build bot > logs. After the main SystemZ patch went it, there was just a single > failure, a timeout on the new s390x.core test. I guess we can just disable > that test until we know what's going on here. > > After the rest of the patches went in, we're additionally seeing all those > 32-bit failures. Not sure which of the patches is responsible (most likely > the Scalar / APInt patch, just from the amount of changes). > > I'm currently rebuilding the Intel LLDB to see if I can reproduce locally.
The current status is: - I've disabled the s390x.core test on all architectures except s390x; there seems to be some problem with reading cross-architecture cores. - There was a regression introduced due to a thinko in my gnu_libstdcpp.py patch; I've checked in a fix for that. - Support for the new files was missing in the XCode project file; Greg checked in a fix for that. Thanks! - I was unable to reproduce the 32-bit failures on my system, so I just reverted the Scalar / APInt patch, and that got the build bot going again. Looking at the results, I think I now understand why I wasn't able to reproduce: I was using gcc to compile the test cases, but apparently the failure occurred only when using clang. I'll try again to reproduce. Right now, the build bots seem to be going green again one by one, hopefully we'll be back to normal soon. Sorry for the breakage! Bye, Ulrich
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits