similar to: [LLVMdev] LNT Perf Base change

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

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:

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

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:

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 12 February 2014 22:06, Chris Matthews <chris.matthews at apple.com> wrote: > 1) Change the default logging strategy in LNT. We should be emailing the sysadmin on all ISEs. > > 2) Update the bots to make submission optional, and don't submit when not wanted. > > 3) Split the bot's use of LNT up to have a separate submission step. Then mark this new submission step

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,

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

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

In terms of cost, I thought an LNT instance would exhaust the free database rows much faster than the free dynos. The price for the small database was only 8 dollars a month though. > On Aug 12, 2014, at 1:23 PM, Renato Golin <renato.golin at linaro.org> wrote: > > Hi Chris, > > Nice setup! > > > On 12 August 2014 19:01, Chris Matthews <chris.matthews at

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

On Mon, Jan 28, 2013 at 8:57 AM, Redmond, Paul <paul.redmond at intel.com> wrote: > Is there a reason why existing buildbots are not generating LNT results? Those running LNT should be/are: http://llvm.org/perf/db_default/v4/nts/recent_activity Shows all 3 of the lab.llvm.org machines that run LNT ( http://lab.llvm.org:8011/buildslaves - you can see these 3 macminis run "-nt"

The -vectorize build bots test the BB-vectorizer. Thanks, Nadav On Jan 28, 2013, at 9:39 AM, "Redmond, Paul" <paul.redmond at intel.com> wrote: > Is O3-vectorize redundant now that the loop vectorizer is enabled by default? > > > On 2013-01-28, at 12:25 PM, David Blaikie wrote: > >> On Mon, Jan 28, 2013 at 8:57 AM, Redmond, Paul <paul.redmond at

Is O3-vectorize redundant now that the loop vectorizer is enabled by default? On 2013-01-28, at 12:25 PM, David Blaikie wrote: > On Mon, Jan 28, 2013 at 8:57 AM, Redmond, Paul <paul.redmond at intel.com> wrote: >> Is there a reason why existing buildbots are not generating LNT results? > > Those running LNT should be/are: > >

Renato, Kristof, I confirm this is due to the latest Flask --- Flask-0.11 was released this weekend --- and for some unknown (to me at least) reason, although LNT's requirements.txt pins Flask to version 0.10.1, pip installs Flask-0.11. Forcing Flask to 0.10.1 gets the situation back to normal. Reading pip's documentation makes me think it's not able to resolve dependencies

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,

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

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

Is there a reason why existing buildbots are not generating LNT results? On 2013-01-28, at 11:37 AM, David Blaikie wrote: They're just build bots running LNT - check the build bot configuration code in the zorg llvm project repository. You'll probably need to do some work to get a machine quiet enough to have reliable/useful performance results, though On Jan 28, 2013 8:33 AM,

On 2 August 2014 00:40, Renato Golin <renato.golin at linaro.org> wrote: > If memory serves me well (it doesn't), these are the list of things we > agreed on making, and their progress: > > 1. Performance-specific test-suite: a group of specific benchmarks > that should be tracked with the LNT infrastructure. Hal proposed to > look at this, but other people helped