search for: multistaging

Seems there were a couple of correlated failures that appear to be flakes on this buildbot recently: green: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/13974 red: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/13975 (target-override.c during stage 1, seems to be missing the directory/symlink it just created) red:

Well, I am at my wit's end. I have copied over the script and directories for this test case and run it a few million times. First I was running one at a time, then I switched to kicking off 1000 at a time. All the while, the bots continued to run on the same machine. The script never failed even once. I am not sure if this has something to do with Python as part of llvm-lit or what is going

Sure. I didn't use lit or ninja. I simply copied the script produced by lit (/home/buildbots/ppc64le-clang-multistage-test/clang-ppc64le-multistage/stage1/tools/clang/test/Driver/Output/target-override.c.script) into a temporary directory (along with a deep copy of the build directory). I modified the paths in the script to point to the temporary directory. Then I ran the script in a loop. For

I think that was maybe the discussion on https://reviews.llvm.org/D78245 On Thu, Sep 3, 2020 at 6:22 PM Robinson, Paul <paul.robinson at sony.com> wrote: > I have a vague memory that libcxx wanted it for something, and claimed it > would be hard to work around not having it. > > Anyone else remember that? I can’t dredge up the details, sorry… > > In any event, a separate

This is likely due to a race condition (%T is a shared parent directory). I'll put up a patch to fix it. On Thu, Sep 3, 2020 at 10:00 AM David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Is the machine running any jobs in parallel? Would it be worth trying running lit in the loop, rather than the script? (perhaps lit's doing something interesting) or maybe the

https://llvm.org/docs/CommandGuide/lit.html already lists %T as "parent directory of %t (not unique, deprecated, do not use)". See also https://reviews.llvm.org/D35396 On Thu, Sep 3, 2020 at 3:37 PM David Blaikie <dblaikie at gmail.com> wrote: > Yeah, I think I'd be up for considering deprecation of %T due to the risk > of race conditions/conflicts between tests. %t

Should be fixed by https://reviews.llvm.org/D87103 Shall we consider deprecating(emitting a warning)/removing %T from lit? lldb, lld/COFF and clang-tools-extra are the three major users of %T. There are a few other %T in other places but there are not too many. We will also investigate whether other projects using lit are using %T. On Thu, Sep 3, 2020 at 11:25 AM David Blaikie <dblaikie at

Thanks everyone for this discussion. Turns out that in my effort to make it possible to run multiple instances of this script in parallel, I inadvertently hid the issue. I made each instance use a directory that has $1 appended to the name and the wrapper script provided a unique value with $LINENO. :( MaskRay, thanks for fixing the problem. All the PPC bots are back to green now. On Thu, Sep 3,

in a multi-stage form, what is the proper way for handling the passing of the object thru each step ? If i have a database called events, and my controller looks like step = @params[:step] || 1 if step == 1 @event = Event.new @event = @session[:event] if @session[:event] elsif step == 2 @event = Event.new @event = @params[:event] elsif step == 3 @event = Event.new @event =

This just failed again: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/1579 Bill, could you take a look at this? This is like the 3rd time I've been incorrectly pinged by this buildbot due to this issue. -- Sean Silva On Mon, Jun 13, 2016 at 8:07 PM, Sean Silva <chisophugis at gmail.com> wrote: > Thanks for taking a look. The flaky ASan test failure in the

I threw all the sanitizers I had access to on this test and didn't find anything. The merging uses threads so I can't rule out nondeterminism. It's strange that it only happens on ppc64le and only on stage 2, so an actual miscompile wouldn't surprise me either. On Sun, Jun 12, 2016 at 4:26 PM, Sean Silva <chisophugis at gmail.com> wrote: > Also, `Clang Tools ::

http://lab.llvm.org:8011/builders/clang-ppc64be-linux-multistage/builds/60 probably didn't use OS X? On Tue, Feb 2, 2016 at 11:20 AM, David Blaikie <dblaikie at gmail.com> wrote: > Can we XFAIL it only on OSX/Darwin & file a bug? It sounds like the issue > may be restricted to that platform & there's incomplete (possibly ongoing) > investigation? That way we

Dear WizaRds, dear Thomas, First of all, I want to tell you how grateful I am for all your support. I wish I will be able to help others along one day the same way you do. Thank you so much. I am struggling with a multistage sampling design: library(survey) multi3 <- data.frame(cluster=c(1,1,1,1 ,2,2,2, 3,3), id=c(1,2,3,4, 1,2,3, 1,2), nl=c(4,4,4,4, 3,3,3, 2,2), Nl=c(100,100,100,100,

Thanks for taking a look. The flaky ASan test failure in the OP was stage1 so it sounds like there may be multiple problems :( -- Sean Silva On Sun, Jun 12, 2016 at 7:32 AM, Benjamin Kramer <benny.kra at gmail.com> wrote: > I threw all the sanitizers I had access to on this test and didn't > find anything. The merging uses threads so I can't rule out > nondeterminism.

I looked at this a bit a while back when you first asked but I didn't see anything obviously wrong. Benjamin, at least one of the referenced failures was on BE powerpc64. I don't remember if that one (http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883) failed on stage 1 or 2 and the results pages are no longer available. BTW, I tried testing the same revision many

On Tue, Feb 2, 2016 at 5:24 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Tue, Feb 2, 2016 at 8:23 AM, Nico Weber <thakis at google.com> wrote: >> >> http://lab.llvm.org:8011/builders/clang-ppc64be-linux-multistage/builds/60 >> probably didn't use OS X? > > > Fair point - Kostya/Dmitry, any ideas here? > >> >> >>

On Tue, Sep 1, 2020 at 3:57 PM David Blaikie <dblaikie at gmail.com> wrote: > > > On Tue, Sep 1, 2020 at 12:42 PM Nico Weber <thakis at chromium.org> wrote: > >> On Tue, Sep 1, 2020 at 3:32 PM David Blaikie <dblaikie at gmail.com> wrote: >> >>> On Tue, Sep 1, 2020 at 12:07 PM Nico Weber via cfe-dev < >>> cfe-dev at lists.llvm.org>

Hi Bill, just a heads up but this bot seems to have spuriously failed on a build that only pulled in my commit r272505 which is unrelated. http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883 -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160612/8b2c4493/attachment.html>

On 01/22/2016 09:47 PM, Nico Weber via llvm-dev wrote: > Here's another one: > http://lab.llvm.org:8011/builders/clang-ppc64be-linux-multistage/builds/60 I just got another error. Could we possibly disable this test until this issue has been resolved? Best, Tobias

Hello everyone, Below are some buildbot numbers for the last week of 4/15/2018 - 4/21/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds,