similar to: LNT Buildbots broken

Great, good to know it's not just a problem with our bot. Thanks! On 28 August 2017 at 16:24, Chris Matthews <cmatthews5 at apple.com> wrote: > Hi Diana, > > I have seen that issue on some other bots too. I will fix it this week. It is something about how MySQL treats character encodings differently than Postgres. We are checking for the value in the table beforehand, and this

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

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

Hi, I have recently moved the clang-native-arm-lnt-perf bot from the nt producer to the test-suite producer. It seems to be working fine but it doesn't manage to submit the results to http://lnt.llvm.org/submitRun. If you scroll down to the bottom of [1], you can see this error message: 2017-08-28 07:06:32: submitting result to 'http://lnt.llvm.org/submitRun' error: lnt server:

Hi Bill, The PPC LNT buildbot is randomly failing on LNT because of timeouts. http://lab.llvm.org:8011/builders/clang-ppc64le-linux-lnt I've checked all recent LNT failures and they were spotted on some processes (lua, sqlite3, tramp3d, expandfft, etc), so I doubt this is in any was a real time out due to code-gen issues. I imagine they're all at the edge already and the standard

Hi Since the buildbot host was updated to Fedora F20 levels, the clang buildbot has been failing with the following: $ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt --no-timestamp --cc /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++

Hi James/Chris, You guys have done this before, so I'm guessing you can help me understand what's going on. If my buildbot config is: jobs=2, nt_flags=['--cflag', '-mcpu=cortex-a15', '--use-perf', '--threads=1', '--build-threads=4'] It uses -j4 for build, -j2 for running the tests:

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

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,

Folks, I'm scratching my head to understand what's wrong with this bot: http://lab.llvm.org:8011/builders/clang-native-arm-lnt/builds/7783/steps/lnt.nightly-test/logs/stdio There were no recent commits to lnt or the test-suite and I've cleaned the lnt.venv on the bot, but it's still failing. I also haven't updated the packages or anything on the bot. Can any LNT specialist

LNT executes: cc_version = capture([cc, '-v', '-E'] + cc_flags + ['-x', 'c', '/dev/null', '-###'], include_stderr=True).strip() Then parses the result Perhaps that output has changed in an unexpected way? > On Aug 6, 2014, at 3:06 PM, Chris Matthews <chris.matthews at apple.com> wrote:

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

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

Hi folks, I got ISE when submitting the LNT logs to perf: http://lab.llvm.org:8011/builders/clang-native-arm-lnt/builds/4663/steps/lnt.nightly-test/logs/stdio I think this is the first time that I get this, is there something happening to the server? Can I disable submitting the results? I don't really care much about the performance of those runs, since that's just the conformance

I think that will work. We should actually fix it to work with .11. It is a dot release, the changes are minor. Sent from my iPhone > On May 31, 2016, at 6:34 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I hope I've fixed this properly just now in http://llvm.org/viewvc/llvm-project?view=revision&revision=271274. > Fingers crossed that the

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'

It has just been brought to my attention that our buildbots no longer report failures to compile/link files in the test-suite as failures for the build. As a result, we have at least one bot that is currently showing a green status, yet it aborts when building 3 test cases. I assume that something has changed with how (presumably LNT) reports these failures and the Zorg code does not adequately

Hello, as of Jul 9, the LNT build bot on SystemZ shows red. The problem occurs in the "setup lit" test, which fails due to: Processing dependencies for LNT==0.4.2.dev0 Searching for typing Reading https://pypi.org/simple/typing/ Downloading

http://lab.llvm.org:8011/builders/clang-cmake-aarch64-quick/builds/8218 Searching for aniso8601>=0.82 Reading https://pypi.python.org/simple/aniso8601/ Download error on https://pypi.python.org/simple/aniso8601/: [Errno 107] Transport endpoint is not connected -- Some packages may not be found! Couldn't find index page for 'aniso8601' (maybe misspelled?) Scanning index of all

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,