similar to: [LLVMdev] test-suite and lnt

On 4 June 2013 22:08, Reed Kotler <rkotler at mips.com> wrote: > is test-suite being run still by itself (independent of llvm)? > AFAIK, yes. http://llvm.org/docs/lnt/quickstart.html if so, are there public build bots for this? > We have one: http://lab.llvm.org:8011/builders/clang-native-arm-lnt Setting it up was just copy&paste on Zorg's config (and fixing the bugs

On Tue, Jun 4, 2013 at 5:52 PM, Renato Golin <renato.golin at linaro.org>wrote: > On 4 June 2013 22:08, Reed Kotler <rkotler at mips.com> wrote: > >> is test-suite being run still by itself (independent of llvm)? >> > > AFAIK, yes. http://llvm.org/docs/lnt/quickstart.html > > > if so, are there public build bots for this? >> > > We have

Hi all, I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html). --- $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt $ ~/mysandbox/bin/python ~/lnt/setup.py develop $ cd mysandbox; source bin/activate $ $ lnt runtest nt \ --sandbox SANDBOX \ --cc

I followed the LNT quickstart guide ( http://llvm.org/docs/lnt/quickstart.html) on my debian machine, and it seems to have a problem running. When I consult test.log, every single test has a section like this # Pretend that the reference output was produced instantaneously. > cp /home/jeremy/hardware/llvm/test-suite/instant.txt > Output/sse.expandfft.out-nat.time >

I followed the lnt quickstart <http://llvm.org/docs/lnt/quickstart.html> directions but got this diagnostic when doing the setup: bash-3.2$ ~/mysandbox/bin/python ~/lnt/setup.py develop /Users/dcallahan/mysandbox/lib/python2.7/site-packages/setuptools/dist.py:284: UserWarning: The version spec\ ified requires normalization, consider using '0.4.1.dev0' instead of

On 17 June 2013 19:01, Daniel Dunbar <daniel at zuster.org> wrote: > There are several individual users who still use the full Makefile > infrastructure. I think we pretty much use LNT exclusively for automated > runs now, but for development purposes the Makefile setup still has various > features that make it more amenable to incremental development. > Hi Daniel, I have

Hi, I followed the instructions on http://llvm.org/docs/lnt/quickstart.html, and got stuck on installation Step 4. ~/mysandbox/bin/python ~/lnt/setup.py develop said running develop error: None and returned error code 1. The lnt binary wasn't installed anywhere. Any clue? Thanks much, Jingyue -------------- next part -------------- An HTML attachment was scrubbed... URL:

The attached patch didn't fix it, but when I also changed another == to = a few lines further down it seemed to work. Jeremy On Tue, Jun 24, 2014 at 10:07 PM, Justin Bogner <mail at justinbogner.com> wrote: > Jeremy Salwen <jeremysalwen at gmail.com> writes: > > I followed the LNT quickstart guide > > (http://llvm.org/docs/lnt/quickstart.html) on my debian

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

It has just been brought to my attention that our buildbots no longer report failures to compile/link files in the test-suite as failures for the build. As a result, we have at least one bot that is currently showing a green status, yet it aborts when building 3 test cases. I assume that something has changed with how (presumably LNT) reports these failures and the Zorg code does not adequately

I want to get lnt to use qemu for the execution. In that case, RHOST= is not set. But I change the Arch because I am going to run in cross mode. Then I'm setting RUNUNDER to be a script which runs qemu. In this case it builds timeit-target as a Mips which fails because this is running on x86. ~/mysandbox/bin/lnt runtest nt --sandbox ~/mysandbox --cc /local/llvmpb_a/install/bin/clang

Hi All, Could anyone please give your suggestions on how to generate/get Code Size of each test in LLVM TEST Suite. Thanks & Regards, Ramakota Reddy. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person,

Hi David, That's weird, I have setup LNT in multiple different distros and have never seen this. Looks like no one ever tested on the system you're running. Can you share a bit more of your environment? Also, you can check the setup.py to see if it does any stripping of package names, which could go wrong in the wrong environment. cheers, --renato On 29 January 2015 at 20:13, David

Hi Folks, Looks like our LNT ARM buildbot with the vectorizer is running and producing good results. There are only 11 failures: FAIL: MultiSource/Applications/Burg/burg.execution_time (1 of 1104) FAIL: MultiSource/Applications/ClamAV/clamscan.execution_time (2 of 1104) FAIL: MultiSource/Applications/lemon/lemon.execution_time (3 of 1104) FAIL:

Hi, I'm trying to setup the test-suite and am getting short of running it... Following the steps here: http://llvm.org/docs/lnt/quickstart.html I got as far as getting lnt installed, but when I run the "lnt runtest nt" it fails: compilers.py:81: error: unable to determine compiler version: 'clang++': 'clang version 3.2 ' Seems my string doesn't have a

On Wed, Apr 11, 2012 at 7:59 PM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi all, > >  I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my > flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html). > > --- > $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt > $ ~/mysandbox/bin/python ~/lnt/setup.py develop >

Hi, I'm trying to use LNT to run the test-suite. I followed the instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I get this error: (mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox --cc ~/pg/others/llvm/release/bin/clang --test-suite test-suite nt.py:1185: note: inferred C++ compiler under test as:

I got Python 2.7.3 Sounds right? On Fri Aug 08 2014 at 4:45:01 PM Yi Kong <kongy.dev at gmail.com> wrote: > Hi Jingyue, > > I've never seen this error before. It looks like something to do with > virtualenv. > > What do you get by running `~/mysandbox/bin/python --version`? > > -Yi > > On 8 August 2014 23:48, Jingyue Wu <jingyue at google.com>

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'

The issues seems to be this line in the tools Makefile timeit-target: timeit.c $(LD_ENV_OVERRIDES) $(LCC) -o $@ $< $(LDFLAGS) $(CFLAGS) $(TARGET_FLAGS) -O3 It should not add target flags if we are simulating the target on the host. On 06/06/2013 06:59 PM, reed kotler wrote: > I want to get lnt to use qemu for the execution. > > In that case, RHOST= is not set. > > But I