similar to: [LLVMdev] LNT buildbot Internal Server Error

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 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++

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

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

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 19 February 2013 15:16, Arnold Schwaighofer <aschwaighofer at apple.com>wrote: > Do you have a base run with vectorization turned off? So we could see > where we are degrading things? > I wanted to, but after a few failed attempts, I couldn't pass the option to clang to disable vectorization. I don't want to make Galina reconfig the master every time, so I set up a

Hi Renato, I noticed the bot yesterday. Thanks for working on this! On Feb 19, 2013, at 7:45 AM, Renato Golin <renato.golin at linaro.org> wrote: > Hi Folks, > > Looks like our LNT ARM buildbot with the vectorizer is running and producing good results. Do you have a base run with vectorization turned off? So we could see where we are degrading things? When you say good

On Tue, Feb 19, 2013 at 7:36 AM, Renato Golin <renato.golin at linaro.org>wrote: > On 19 February 2013 15:16, Arnold Schwaighofer <aschwaighofer at apple.com>wrote: > >> Do you have a base run with vectorization turned off? So we could see >> where we are degrading things? >> > > I wanted to, but after a few failed attempts, I couldn't pass the option

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 Folks, Looks like our LNT ARM buildbot with the vectorizer is running and producing good results. There are only 11 failures: FAIL: MultiSource/Applications/Burg/burg.execution_time (1 of 1104) FAIL: MultiSource/Applications/ClamAV/clamscan.execution_time (2 of 1104) FAIL: MultiSource/Applications/lemon/lemon.execution_time (3 of 1104) FAIL:

Hi, I am currently investigating how to ensure that LNT only shows relevant performance regressions for the -O3 performance tests I am running. One question that came up here is why the default aggregate function for LNT is 'min' instead of 'mean'. This looks a little surprising from the statistical point, but also from looking at my test results picking 'min' seems

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, It seems all LNT buildbots are broken due to the error: error: The 'six==1.9.0' distribution was not found and is required by LNT The module seems to be in version 1.10 and probably the old binary is no longer there. Do we really need it to be 1.9? Can't that be >1.9? cheers, --renato

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

Right - you usually won't see a normal distribution in the noise of test results. You'll see results clustered around the lower bound with a long tail of slower and slower results. Depending on how many samples you do it might be appropriate to take the mean of the best 3, for example - but the general approach of taking the fastest N does have some basis in any case. Not necessarily the

Hi, So, I owe you all an apology. I was totally unaware that the llvm.org server, running at UIUC, was still in operation and hosting an active LNT instance. I was under the assumption the LNT server ran elsewhere. As a result, the ability for the LNT bots to submit run information to the "old" LNT server is now gone. I am very sorry for this oversight. In speaking with Chris

Hi Renato, I'm playing with A15 bots too (running Ubuntu). This is probably what you want to have predictable performance: Disable auto-resetting the CPU scaling governor to ondemand: sudo update-rc.d -f ondemand remove Then add this to /etc/rc.local: # Disable power management. for cpu in `find /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor`; do echo performance > $cpu

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:

I’d like to propose a new LNT feature that I plan to start working on immediately: formal performance change tracking. Motivation: LNT produces a lot of data, but it is not very actionable. Unless you are watching the nightly reports, or checking LNT regularly, performance changes can happen and be missed. Oh no! Once commits have been in tree for a long time, it is harder to fix them even if

On Tue, 12 Jun 2012 11:15:12 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 02/05/2012 02:42 PM, Hal Finkel wrote: > > I think that it would be a good idea to have a buildbot set up to > > run the test suite with -vectorize. Could one of the existing > > machines do this also? > > It took some time, but we have this now: > >