similar to: Internal server error when submitting LNT to lnt.llvm.org

On Wed, Aug 2, 2017, at 21:55, Tobias Grosser via llvm-dev wrote: > This started since about 1-2 weeks, I guess. I am not sure about it > either, but seems unfortunate. Maybe we run into some kind of timeout? And another one :( http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly/builds/1986/steps/lnt.nightly-test/logs/stdio 2017-08-03 00:24:44 CRITICAL: Results were not

Actually I just remember LNT has a page for viewing the log: http://lnt.llvm.org/log ... OperationalError: (OperationalError) (2006, 'MySQL server has gone away') 'SELECT `NT_Run`.`ID` AS `NT_Run_ID`, `NT_Run`.`MachineID` AS `NT_Run_MachineID`, `NT_Run`.`OrderID` AS `NT_Run_OrderID`, `NT_Run`.`ImportedFrom` AS `NT_Run_ImportedFrom`, `NT_Run`.`StartTime` AS `NT_Run_StartTime`,

The run page problem were triggered by one of my commits (sorry) and should be mitigated now, see the thread at http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html <http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html> I don't know about the submission problems, could they just an occasional network problem or are they a common phenomenon? Chris did some

Hi, The new LNT server instance http://lnt.llvm.org seems to fail in many cases. Any entrance to a 'Run page' (e.g. http://lnt.llvm.org/db_default/v4/nts/62475) and lately also many perf bots result submissions (e.g. http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio ) fails with: "500 Internal Server Error". Any ideas? Thanks,

Hi Renato, on our public LNT servers I see again error 500 messages every once in a while: http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly-fast Could you possibly have a look? Tobias

Hi Chris, llvm.org/perf gives again error 500s. I remember you had a look the last time. Would you mind looking again? Also, is there something which we could do to make LNT more robust. Do you have an idea what the last issue was about? Thanks, Tobias -------- Original Message -------- Subject: buildbot failure in LLVM on polly-perf-O3-polly-scev-codegen-isl Date: Fri, 21 Feb 2014 17:08:44

Re-poked. - Daniel On Wed, Mar 19, 2014 at 12:04 PM, Tobias Grosser <tobias at grosser.es> wrote: > On 03/11/2014 12:41 PM, Tobias Grosser wrote: > >> Hi Chris, hi Daniel, >> >> I see again internal server errors when visiting llvm.org/perf. I >> remember you have been restarting the service several times, but it >> seems it is happening again. Did

Hello everyone, Below are some buildbot numbers for the last week of 6/05/2016 - 6/11/2016. Thanks Galina buildername | was_red -----------------------------------------------------------+----------- sanitizer-x86_64-linux-bootstrap | 134:12:25 perf-x86_64-penryn-O3-polly-parallel-fast | 46:29:26

Hello everyone, Below are some buildbot numbers for the week of 7/10/2016 - 7/16/2016. 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, failed

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

Hello everyone, Below are some buildbot numbers for the last week of 9/25/2016 - 10/1/2016. Please see the same data in attached csv files: The longest time each builder was red during the last 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

I will take a peek at the server log. On Jan 16, 2014, at 4:09 PM, Tobias Grosser <tobias at grosser.es> wrote: > On 01/17/2014 01:07 AM, Tobias Grosser wrote: >> On 01/17/2014 12:59 AM, Chris Matthews wrote: >>> Do you guys have examples of a LNT results file that causes the failure? >> >> Hi Chris, >> >> thanks for the quick reply. Here a link

The bot hiccupped earlier but looks stable now. The average turnaround seems to be 3.5 hours. clang: http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html lld: http://lab.llvm.org:8080/coverage/coverage-reports/lld/index.html polly: http://lab.llvm.org:8080/coverage/coverage-reports/polly/index.html > On Sep 23, 2016, at 11:58 PM, Tobias Grosser via llvm-dev

Hi Tobi, http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly Looks like one of your boxes are bad and the other is good, but since they're both on the same bot, it looks to use as if it's unstable, spamming people every other build. :) Can you have a look, please? cheers, --renato

I've configured the bot to test lld and polly. The first batch of reports for the new tools are not ready yet, but anyone can monitor the build: http://lab.llvm.org:8080/green/view/Experimental/job/clang-stage2-coverage-R/ Matthias, I will ask around about adding a link to this bot on llvm.org once it graduates from the Experimental pane on greendragon. thanks, vedant > On Sep 23,

Hi Tobi, I'm familiar with Zorg, but sometimes people have plans for existing bots I might not be aware of. Are there specific bots for linux/windows I should add this to, or should I leave the existing polly bots alone and create one or two new ones? Of course, Any change would be backward compatible to all other users of the builder. The plan would be have linux and windows cmake

On 01/17/2014 12:59 AM, Chris Matthews wrote: > Do you guys have examples of a LNT results file that causes the failure? Hi Chris, thanks for the quick reply. Here a link to the most recent failing results file: http://lab.llvm.org:8011/builders/polly-perf-O3/builds/704/steps/lnt.nightly-test/logs/report.json Please download it as the buildbots will delete it at some point. Tobias

On 05/19/2015 08:50 PM, Chris Matthews wrote: > Just some stats, after looking through lab.llvm.org > <http://lab.llvm.org>:8011 > > Maybe these should be marked as experimental, and removed from the > builders link on the main page. > > Never passed at all: > libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03 > libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan >

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'

On 01/16/2014 11:47 PM, Chris Matthews wrote: > The error you are seeing there is the client side error of a server side exception. It is probably best to address the actual failure. Those will probably be in the apache log on the server. > > That said, I think if a bot really is just for testing and not performance there is no harm in not submitting the results. I have the same