similar to: [LLVMdev] llvm.org/perf internal server error

Displaying 20 results from an estimated 50000 matches similar to: "[LLVMdev] llvm.org/perf internal server error"

2014 Feb 12
2
[LLVMdev] llvm.org/perf internal server error
On 02/12/2014 11:43 AM, Renato Golin wrote: > On 12 February 2014 13:52, Tobias Grosser <tobias at grosser.es> wrote: >> I get an internal server error when accessing llvm.org/perf. This error >> causes buildbot failures as they can not properly report their performance >> findings. > > To be honest, I'd like to stop reporting performance altogether, since >
2014 Feb 22
2
[LLVMdev] llvm.org/perf error 500
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
2014 Feb 12
2
[LLVMdev] llvm.org/perf internal server error
I agree that we should add this feature. No point in submitting results that we don’t plan to use. On Feb 12, 2014, at 10:23 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 12 February 2014 18:21, Tobias Grosser <tobias at grosser.es> wrote: >> lnt has a flag to do not report the results. > > Not in the bots config. > > I had a look at it last time,
2014 Jan 17
3
[LLVMdev] LNT buildbot Internal Server Error
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
2014 Jan 17
2
[LLVMdev] LNT buildbot Internal Server Error
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
2017 Jul 31
2
Internal server error when submitting LNT to lnt.llvm.org
Dear all, I recently started to see internal server errors when submitting perf results to lnt.llvm.org http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly-before-vectorizer/builds/1154/steps/lnt.nightly-test/logs/stdio nt /home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer/tests/nt/build/sample-0/report.simple.csv
2012 Jun 24
3
[LLVMdev] buildbot with -vectorize
On Sun, 24 Jun 2012 08:17:32 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/24/2012 05:42 AM, Hal Finkel wrote: > > On Thu, 21 Jun 2012 16:25:13 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 06/21/2012 04:23 PM, Hal Finkel wrote: > >>> On Thu, 21 Jun 2012 01:03:46 +0200 > >>> Tobias
2014 Jan 16
2
[LLVMdev] LNT buildbot Internal Server Error
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
2014 May 16
5
[LLVMdev] Use perf tool for more accurate time measuring on Linux
Hi all, The LLVM benchmarking system produces very noisy results even on quiet machines. One of the sources of inaccuracy is the timing tool we are using. Because it is a user-space tool, the OS can context switch it and we will get an outlier result. Perf stat uses SW_TASK_CLOCK counter in kernel to measure time, therefore more accurate. It also does not get context switched. I've
2012 Jun 24
2
[LLVMdev] buildbot with -vectorize
On Thu, 21 Jun 2012 16:25:13 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/21/2012 04:23 PM, Hal Finkel wrote: > > On Thu, 21 Jun 2012 01:03:46 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 06/20/2012 11:07 PM, Hal Finkel wrote: > >>> On Tue, 12 Jun 2012 11:15:12 +0200 > >>> Tobias
2014 Mar 20
3
[LLVMdev] LNT internal server error
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
2012 Jun 24
0
[LLVMdev] buildbot with -vectorize
On 06/24/2012 02:42 PM, Hal Finkel wrote: > On Sun, 24 Jun 2012 08:17:32 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 06/24/2012 05:42 AM, Hal Finkel wrote: >>> On Thu, 21 Jun 2012 16:25:13 +0200 >>> Tobias Grosser<tobias at grosser.es> wrote: >>> >>>> On 06/21/2012 04:23 PM, Hal Finkel wrote: >>>>>
2017 Aug 03
2
[LNT] new server instance http://lnt.llvm.org seems unstable
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
2017 Aug 02
2
[LNT] new server instance http://lnt.llvm.org seems unstable
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`,
2017 Jun 27
5
LNT Server offline
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
2014 Nov 27
2
[LLVMdev] Perf is dead again... :(
The LNT Perf reporting website is down for a few days now, should I disable my perf bot to avoid noise while that gets fixed? cheers, --renato
2014 May 16
2
[LLVMdev] Use perf tool for more accurate time measuring on Linux
On 16 May 2014 18:08, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> From: "Yi Kong" <kongy.dev at gmail.com> >> To: "Hal Finkel" <hfinkel at anl.gov>, "Renato Golin" <renato.golin at linaro.org>, "Tobias Grosser" <tobias at grosser.es> >> Cc: "LLVM Dev" <llvmdev at
2014 May 20
3
[LLVMdev] Use perf tool for more accurate time measuring on Linux
On 20 May 2014 16:40, Tobias Grosser <tobias at grosser.es> wrote: > On 20/05/2014 16:01, Yi Kong wrote: >> >> I've set up a public LNT server to show the result of perf stat. There >> is a huge improvement compared with timeit tool. >> http://parkas16.inria.fr:8000/ > > > Hi Yi Kong, > > thanks for testing these changes. > > >> Patch
2012 Jun 24
0
[LLVMdev] buildbot with -vectorize
On 06/24/2012 05:42 AM, Hal Finkel wrote: > On Thu, 21 Jun 2012 16:25:13 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 06/21/2012 04:23 PM, Hal Finkel wrote: >>> On Thu, 21 Jun 2012 01:03:46 +0200 >>> Tobias Grosser<tobias at grosser.es> wrote: >>> >>>> On 06/20/2012 11:07 PM, Hal Finkel wrote: >>>>>
2014 Dec 01
2
[LLVMdev] Perf is dead again... :(
This was part of the motivation my cloud LNT instance. The Heroku cloud which I am running on is using a postgres cluster, not a single machine. It is well tuned for large databases. > On Nov 30, 2014, at 6:59 AM, Renato Golin <renato.golin at linaro.org> wrote: > > On 30 November 2014 at 13:29, Tobias Grosser <tobias at grosser.es> wrote: >> Proving