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