similar to: Do the build failure related to my commit?

I made a commit just now, and received many build failures. It seems they all began to fail after my commit. http://lab.llvm.org:8011/#/builders/112 http://lab.llvm.org:8011/#/builders/121 http://lab.llvm.org:8011/#/builders/33 I can't understand why. It seems my commit is only a small change. The "make check-all" does pass without any failure on my local PC. Ben Shi

Hi Renato, We're also seeing this on internal bots. My first guess is that it was triggered by the Flask package getting updated at Pypi on 29th of May, see https://pypi.python.org/pypi/Flask. I haven't investigated further at this point. Thanks, Kristof On 29 May 2016, at 14:28, Renato Golin <renato.golin at linaro.org<mailto:renato.golin at linaro.org>> wrote: Folks,

Folks, Its seems that the latest master restart has introduced a failure in *many* test-suite bots: File "/home/buildslave/buildslave/clang-cmake-aarch64-full/test/lnt/lnt/server/ui/decorators.py", line 6, in <module> frontend = flask.Module(__name__) AttributeError: 'module' object has no attribute 'Module'

Should "lit :: shtest-format.py" (from check-lit) be marked unsupported on PS4? It seems flakey there. This evening, it failed on my commit, r337514, and I'm fairly confident it wasn't my commit's fault. Then it recovered on the next commit. http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/33502

Renato, Kristof, I confirm this is due to the latest Flask --- Flask-0.11 was released this weekend --- and for some unknown (to me at least) reason, although LNT's requirements.txt pins Flask to version 0.10.1, pip installs Flask-0.11. Forcing Flask to 0.10.1 gets the situation back to normal. Reading pip's documentation makes me think it's not able to resolve dependencies

Hi All, I'm trying to reproduce a failure on llvm-ppc64-linux1 (http://lab.llvm.org:8011/builders/llvm-ppc64-linux1/builds/5382) and llvm-ppc64-linux2 builders caused by one of my patches yesterday. Some of the CodeGen/Hexagon tests failed to compile with stack dump problem. I tried to configure and build LLVM for PowerPC on my machine locally but don't see the failures. I had to remove

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:

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,

Folks, It seems we got the same issue with Clang alignment as before: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost/builds/3025 http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost-neon/builds/485 http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-sh/builds/118 Commits between 231213 and 231255. There are a few issues that could have brought it: *

Happened to me again: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/18273/steps/annotate/logs/stdio In fact, this whole bot has a 20% failure rate with the same failure mode, from looking at the history: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/?numbuilds=50 They all end with this: [100%] Running ThreadSanitizer tests -- Testing: 258 tests, 16 threads --

This bot was failing from http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/29505 until it went green on http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/29534 Anyone happen to know why? I can't quite figure it out from the commits - would be good to know if it's a buildbot issue or a genuine LLVM problem that was in the LLVM code and fixed by one of those

This buildbot has been failing for over a week straight ( http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/9387 ) - does anyone know/care about it? ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Wed, Sep 30, 2015 at 7:49 PM Subject: buildbot failure in LLVM on clang-cmake-mips To: Adrian Prantl <aprantl at apple.com>, Ahmed Bougacha

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

FWIW, I've seen it fail on some of my commits too, but I don't remember whether it was on the PS4 bot exclusively or not. Anyway, my understanding is that this test shouldn't inherently have different behaviour on PS4 specifically, but I could be mistaken. I suspect it's something more general to do with the configuration of the bot. James On 20 July 2018 at 03:52, Justin Bogner

On Sat, May 6, 2017, at 04:28 PM, llvm.buildmaster at lab.llvm.org wrote: > The Buildbot has detected a failed build on builder polly-amd64-linux > while building polly. > Full details are available at: > http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/6539 > > Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: grosser1 > > Build

Hi, many of the bots on http://lab.llvm.org:8011/console don't do anything in their compile phase, even if they should. For example, these bots all don't do anything in their compile phase in any builds, even if they should: http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/ http://lab.llvm.org:8011/builders/clang-ppc64be-linux

vitalybuka, sanitizer-x86_64-linux-gn is _still_ on http://lab.llvm.org:8011/console . Can we please get it removed? On Wed, Jul 3, 2019 at 7:07 AM Nico Weber <thakis at chromium.org> wrote: > https://reviews.llvm.org/D63909 landed. Maybe it needs a master restart > to have an effect? > > On Wed, Jul 3, 2019 at 1:03 PM Roman Lebedev <lebedev.ri at gmail.com> wrote: >

Alexey, I got mail from one of the tsan buildbots, claiming a breakage in tsan tests. But I cannot see anything on the logs it has for the build. http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17916/steps/run%2064-bit%20tsan%20unit%20tests/logs/stdio Any ideas? Thanks. Diego. ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Wed,

On Wed, May 13, 2015 at 10:39 AM, Reid Kleckner <rnk at google.com> wrote: > It's a 20m timeout without output. > > If you back up to the build and look at the 'annotate' step output, > there's this text: > > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17916/steps/annotate/logs/stdio > > -- Testing: 258 tests, 16 threads -- >

Hi, It seems the problem is that the bot is updating llvm.src, but trying to build from llvm. Galina, it looks like this is related to your recent changes to zorg, you probably missed a spot somewhere and I can't find it on a first glance. Could you have a look? Thanks, Diana On 5 September 2016 at 12:01, Diana Picus <diana.picus at linaro.org> wrote: > Hi Nico, > > Thanks