similar to: [LLVMdev] Buildbot try builds to get pre-commit performance number

Displaying 20 results from an estimated 40000 matches similar to: "[LLVMdev] Buildbot try builds to get pre-commit performance number"

2012 Jun 21
2
[LLVMdev] buildbot with -vectorize
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 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 >
2012 Jun 20
2
[LLVMdev] buildbot with -vectorize
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: > >
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
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
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: >>>>>
2012 Jun 20
0
[LLVMdev] buildbot with -vectorize
On 06/20/2012 11:07 PM, Hal Finkel wrote: > 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? >>
2012 Jun 21
0
[LLVMdev] buildbot with -vectorize
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 Grosser<tobias at grosser.es> wrote: >>> >>>> On 02/05/2012 02:42 PM, Hal Finkel wrote: >>>>>
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: >>>>>
2012 Jun 12
0
[LLVMdev] buildbot with -vectorize
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: http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize The first run shows that there are a couple of test-suite failures with the
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
2013 Dec 19
2
[LLVMdev] How to XFAIL test cases with buildbot LNTFactory
Hi, I am currently trying to set up new performance and regression testers for Polly and LLVM and would like to XFAIL two test cases. I am using the LNTBuilder instead of the NightlyTestBuilder out of the assumption that the LNTBuilder is the more modern solution. However, when trying to xfail test cases I realized the xfail=[] parameter of getLNTFactor is ignored. Previously this was not an
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
2013 Jun 06
2
[LLVMdev] [Polly] Set up performance tester for GSOC2013 FastPolly project
Hi Tobias, I am recently trying to set up the performance tester for FastPolly project. According to your suggestion, I plan to use the LNT infrastructure to set up the performance tester. For this purpose, I think I should do this job in three steps: First, I will add PolyBench to LLVM test-suite since PolyBench is the critical benchmarks for FastPolly. I have adjust the PolyBench-c-3.2 so we
2012 Feb 05
3
[LLVMdev] buildbot with -vectorize
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? Thanks again, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory
2013 Jun 09
0
[LLVMdev] [Polly] Set up performance tester for GSOC2013 FastPolly project
On 06/06/2013 11:17 AM, Star Tan wrote: > Hi Tobias, > > > I am recently trying to set up the performance tester for FastPolly project. According to your suggestion, I plan to use the LNT infrastructure to set up the performance tester. For this purpose, I think I should do this job in three steps: > > > First, I will add PolyBench to LLVM test-suite since PolyBench is the
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 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
2012 Jun 28
2
[LLVMdev] buildbot with -vectorize
On Sun, 24 Jun 2012 14:44:45 +0200 Tobias Grosser <tobias at grosser.es> wrote: > 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
2017 Jul 04
1
Performance metrics with LLVM
Hi Tobias, The metrics that you can collect in LNT are fixed per "test suite". There are 2 such "test suite"s defined in LNT at the moment: nts and compile. For more details on this, see http://llvm.org/docs/lnt/concepts.html#test-suites. AFAIK, If you need to collect different metrics, you'll need to define a new "test suite". I'm afraid I don't really
2017 Jul 04
2
Performance metrics with LLVM
Dear all, I wanted to gather LLVM statistics with lnt and found a nice flag, but am unsure how such statistics can be made available in the LNT web interface. --cmake-define=TEST_SUITE_COLLECT_STATS=ON which allows me to gather all the LLVM "-stats" output. On top of this I see that the LNT cmake test-suite also dumps code-size statistics when running, that look as follows: size: