similar to: [LLVMdev] Proposal: REST and Ajax in LNT

Daniel, Tobias, Renato and myself have been looking a little bit at the potential underlying reason for why http://llvm.org/perf/ is instable, and have found some clues. I want to share them here to give people with more experience in the frameworks used by LNT (flask, sqlalchemy, wsgi, .) a chance to check if our reasoning below seems plausible. Daniel noticed the following backtrace in the

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,

I honestly do not know how to fix that --- I would otherwise I've committed a fix. I've been able to hack it locally exploiting the very same lit limitation then the one we're stumbling on (i.e it does not resolve dependency correctly and only pick-up the first constraint). You need to make sure the Flask constraint is seen first, even before using the requirements.txt so on the

I think that will work. We should actually fix it to work with .11. It is a dot release, the changes are minor. Sent from my iPhone > On May 31, 2016, at 6:34 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I hope I've fixed this properly just now in http://llvm.org/viewvc/llvm-project?view=revision&revision=271274. > Fingers crossed that the

Folks, Its seems that the latest master restart has introduced a failure in *many* test-suite bots: File "/home/buildslave/buildslave/clang-cmake-aarch64-full/test/lnt/lnt/server/ui/decorators.py", line 6, in <module> frontend = flask.Module(__name__) AttributeError: 'module' object has no attribute 'Module'

On 30 May 2016 at 12:25, Arnaud De Grandmaison <Arnaud.DeGrandmaison at arm.com> wrote: > 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. Do

I hope I've fixed this properly just now in http://llvm.org/viewvc/llvm-project?view=revision&revision=271274. Fingers crossed that the bots will come back now... On 30 May 2016, at 21:01, Arnaud De Grandmaison <Arnaud.DeGrandmaison at arm.com<mailto:Arnaud.DeGrandmaison at arm.com>> wrote: I honestly do not know how to fix that --- I would otherwise I've committed a fix.

It seem like it does fix the issue: http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4405. I agree with making LNT work with .11 too - but I'm not familiar with the part of LNT that has this dependency, so someone else may have to look into that. Thanks, Kristof On 31 May 2016, at 15:41, Chris Matthews <cmatthews5 at apple.com<mailto:cmatthews5 at apple.com>>

Hi folks, I noticed our test-suite bot is failing randomly when getting a timeout on the install phase: http://lab.llvm.org:8011/builders/clang-native-arm-lnt/builds/666/steps/venv.lnt.install/logs/stdio Downloading/unpacking Werkzeug>=0.6.1 (from Flask->LNT==0.4.1dev) Exception: File

Ping? This is getting as often as every other run... Is that process downloading from an internal server? If not, should we? If yes, should we not? thanks, --renato On 20 April 2013 14:03, Renato Golin <renato.golin at linaro.org> wrote: > Hi folks, > > I noticed our test-suite bot is failing randomly when getting a timeout on > the install phase: > > >

tl;dr in low data situations we don’t look at past information, and that increases the false positive regression rate. We should look at the possibly incorrect recent past runs to fix that. Motivation: LNT’s current regression detection system has false positive rate that is too high to make it useful. With test suites as large as the llvm “test-suite” a single report will show hundreds of

On 31 May 2016 at 15:06, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > It seem like it does fix the issue: > http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4405. Great, thanks! > I agree with making LNT work with .11 too - but I'm not familiar with the > part of LNT that has this dependency, so someone else may have to look into >

The cloud instance would need funding to run at the scale the llvm.org <http://llvm.org/> server runs at. It can only accommodate about 5k submissions worth of data at its current size. I assume that would be exhausted pretty fast with a bunch of machines submitting several times per day. > On Dec 1, 2014, at 9:49 AM, Tobias Grosser <tobias at grosser.es> wrote: > > On

These patches update the example FLASK policy shipped with Xen and enable its build if the required tools are present. The third patch requires rerunning autoconf to update tools/configure. [PATCH 1/3] flask/policy: sort dom0 accesses [PATCH 2/3] flask/policy: rework policy build system [PATCH 3/3] tools/flask: add FLASK policy to build

From: Elena Lepilkina Sent: Monday, April 25, 2016 2:33 PM To: 'James Molloy' <james at jamesmolloy.co.uk>; Kristof Beyls <Kristof.Beyls at arm.com>; Mehdi Amini <mehdi.amini at apple.com> Cc: nd <nd at arm.com>; Matthias Braun <matze at braunis.de> Subject: RE: [llvm-dev] RFC: LNT/Test-suite support for custom metrics and test parameterization Hi everyone,

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm:

I have a server where we use tmpfs as a cache for temporary files used by a web application. But occasionally this tmpfs thinks it is full when it isn't. [root at flask-yellow tmpfs]# touch file touch: cannot touch `file': No space left on device [root at flask-yellow tmpfs]# df -k Filesystem 1K-blocks Used Available Use% Mounted on none 393216 19296

Adds support for assigning a label to domains, obtaining and setting the current enforcing mode, and loading a policy with xl command and libxl header when the Flask XSM is in use. Adheres to the changes made by the patch to remove exposure of libxenctrl/libxenstore headers via libxl.h. tools/libxl/libxl_flask.c | 71 ++++++++++++++++++ tools/libxl/Makefile | 2

Adds support for assigning a label to domains, obtaining and setting the current enforcing mode, and loading a policy with xl command when the Flask XSM is in use. libxl.c | 1 libxl.idl | 3 - xl.h | 3 + xl_cmdimpl.c | 171 +++++++++++++++++++++++++++++++++++++++++++++++++++++++--- xl_cmdtable.c | 18 +++++- 5 files changed, 187 insertions(+), 9