similar to: [LLVMdev] Perf is dead again... :(

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

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 >

On 27.11.2014 20:39, Chris Matthews wrote: > I can look into it if I get access. Anton, any chance we can get Renato or Chris access to llvm.org to fix this? Tobias

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

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,

On 29.11.2014 23:03, Renato Golin wrote: > On 29 November 2014 at 20:28, Dan Liew <dan at su-root.co.uk> wrote: >> Just a thought. Would it make sense to put LNT server into a Docker >> [1] container so it's portable and then we can move it over to any >> (Linux based) host we like easily and reliably? > > I think this is a great idea. We should at least try,

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

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

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

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

I don’t have access to that server. I have been using a cloud LNT instance for the performance runs on the green-dragon cluster. So far it has provided 100% uptime! http://llvm-lnt.herokuapp.com <http://llvm-lnt.herokuapp.com/> > On Nov 24, 2014, at 3:24 PM, Tobias Grosser <tobias at grosser.es> wrote: > > On 24.11.2014 23:54, Galina Kistanova wrote: >> Hello

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, 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. Chris, could you have a look? Thanks, Tobias

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

On 08/26/2015 04:38 PM, Renato Golin via llvm-dev wrote: > On 26 August 2015 at 15:32, Tobias Grosser <tobias at grosser.es> wrote: >> What's the problem with increasing the timeout? Asking people to ignore >> buildbot mails does not seem right. If the buildbot is flaky I believe >> the buildbot owner should ensure it shuts up until the problems have >> been

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/ Patch is updated to pin the process to a single core, the readings are even more accurate. It's hard coded to run everything on core 0, so don't run parallel testing with it for now. The tool now depends on Linux perf and schedtool.

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

Hello build bot owners! The staging master is ready. Please feel free to use it to make sure your bots would work well with the monorepo and github. The following builders could be configured to build monorepo: * clang-atom-d525-fedora-rel * clang-native-arm-lnt-perf * clang-cmake-armv7-lnt * clang-cmake-armv7-selfhost-neon * clang-cmake-armv7-quick * clang-cmake-armv7-global-isel *

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