On 8 October 2014 12:38, Evgeniy Stepanov <eugenis at google.com> wrote:> When running the final binary.Same thing... :( Should I bisect where that got broken? Do you have any way of testing that locally? This is just a basic CMake build on ARM, nothing special. "ninja check-asan". cheers, --renato
On Wed, Oct 8, 2014 at 3:44 PM, Renato Golin <renato.golin at linaro.org> wrote:> On 8 October 2014 12:38, Evgeniy Stepanov <eugenis at google.com> wrote: >> When running the final binary. > > Same thing... :( > > Should I bisect where that got broken? Do you have any way of testing > that locally? This is just a basic CMake build on ARM, nothing > special. "ninja check-asan".Did it ever work? The test says XFAIL: arm-linux-gnueabi. We know that it works on Android-arm, which is essentially the same, maybe with a few different default settings in the driver.> cheers, > --renato
On 8 October 2014 13:17, Evgeniy Stepanov <eugenis at google.com> wrote:> Did it ever work?I really don't know. I'm just trying to make it work now and haven't tried it before for real.> The test says XFAIL: arm-linux-gnueabi. > We know that it works on Android-arm, which is essentially the same, > maybe with a few different default settings in the driver.This platform is hard-float, that's why the XFAIL doesn't work. But I'm surprised that it passes on Android (which is arm-gnueabi) and not on "arm-linux-gnueabi". Anyway, do you think we should mark all the failing tests XFAIL on gnueabihf for now? http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full/builds/713 We can at least have a green buildbot and work on them later. I'm not particularly worried about ASAN for now, just making sure I can compile compiler-rt and use it for the next step, running the test-suite with it. But I can't do that while this bot is red. cheers, --renato