[llvm-dev] buildbot failure in LLVM on llvm-clang-x86_64-expensive-checks-win
Don Hinton via llvm-dev
llvm-dev at lists.llvm.org
Thu Dec 7 13:16:22 PST 2017
This might be related this change rL319620.
While the first build with this change seems to build fine, all the ones
after it fail to re-run the clean-build-dir and cmake-configure steps.
http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-win/builds/6535
There have been a couple of tweaks to it, but basically this change defers
creating the NATIVE subdir and running cmake until needed (it was always
getting called twice -- once at config time and again at build time).
I don't have windows, so I have no way to test this.
hth...
don
On Thu, Dec 7, 2017 at 12:53 PM, Daniel Sanders via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I've been having the same problem for a while on the GlobalISel work. We
> didn't get to the bottom of it, but it seems likely that the CMake
> Generator this bot uses forgets to create a dependency.
>
> On 6 Dec 2017, at 09:40, Oliver Stannard via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> I’ve had another look, and some of the failing tests don’t use temporary
> files, so I don’t think this is a case of tests having side-effects.
>
> Instead, I’ve noticed that in the build log (http://lab.llvm.org:8011/
> builders/llvm-clang-x86_64-expensive-checks-win/builds/
> 6552/steps/build-unified-tree/logs/stdio), llvm-tblgen.exe is built (my
> patch modified it), but the table-generation steps of the main build
> (importantly, ARMGenAsmMatcher.inc) do not appear to be running. I think
> this would explain the FileCheck output from those failing tests.
>
> Could there be a buildbot misconfiguration which is preventing the
> newly-built llvm-tblgen from being used?
>
> Oliver
>
> *From:* Galina Kistanova [mailto:gkistanova at gmail.com
> <gkistanova at gmail.com>]
> *Sent:* 04 December 2017 22:30
> *To:* Oliver Stannard
> *Cc:* Sander De Smalen; nd
> *Subject:* Re: buildbot failure in LLVM on llvm-clang-x86_64-expensive-
> checks-win
>
> Hi Oliver,
>
> I have requested a clean build of that exact revision and all the tests
> passes.
> http://lab.llvm.org:8011/builders/llvm-clang-x86_64-
> expensive-checks-win/builds/6561
>
> This is kind of bad, as it seems some tests have side effects.
>
> Thanks
>
> Galina
>
>
>
> On Mon, Dec 4, 2017 at 5:47 AM, Oliver Stannard <Oliver.Stannard at arm.com>
> wrote:
> Hi Galina,
>
> This buildbot failure looks related to my patch (blamelist of 1, the
> failing tests are ones I modified), but it's not clear what is wrong from
> the lit output, and I haven't been able to reproduce this locally. Would it
> be possible for you to send me the output of one of the failing llvm-mc
> commands on that bot?
>
> Sander also hit a similar problem with the same bot in
> https://reviews.llvm.org/D40011.
>
> Thanks,
> Oliver
>
>
> > -----Original Message-----
> > From: llvm.buildmaster at lab.llvm.org
> > [mailto:llvm.buildmaster at lab.llvm.org]
> > Sent: 04 December 2017 12:51
> > To: Oliver Stannard
> > Cc: gkistanova at gmail.com
> > Subject: buildbot failure in LLVM on llvm-clang-x86_64-expensive-checks-
> > win
> >
> > The Buildbot has detected a new failure on builder llvm-clang-x86_64-
> > expensive-checks-win while building llvm.
> > Full details are available at:
> > http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-
> > win/builds/6552
> >
> > Buildbot URL: http://lab.llvm.org:8011/
> >
> > Buildslave for this Build: ps4-buildslave2
> >
> > Build Reason: scheduler
> > Build Source Stamp: [branch trunk] 319649
> > Blamelist: olista01
> >
> > BUILD FAILED: failed test-check-all
> >
> > sincerely,
> > -The Buildbot
> >
> >
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171207/f46ccf88/attachment.html>
More information about the llvm-dev
mailing list