similar to: [LLVMdev] Getting LNT to work with non-bash shell

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

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 >

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

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

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>

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:

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:

On Wed, Sep 5, 2012 at 7:23 PM, Sean Silva <silvas at purdue.edu> wrote: > 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

> And it doesn't match probably because of one of two things (& I forget > which of the two, if either, have been addressed/workaround): > > 1) using cmake instead of configure/make > 2) using git instead of svn > > One or both of these create versions that lnt doesn't understand > (because they don't include the SVN revision number in the clang > version

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

The first one failed on a diff: ******************** TEST (simple) 'sse.expandfft' FAILED! ******************** Execution Context Diff: /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: 1.139094e-07 and 1.159249e-07 abs. diff = 2.015500e-09 rel.diff = 1.738626e-02 Out of tolerance: rel/abs: 1.600000e-02/0.000000e+00 ******************** TEST (simple)

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

when I create the report, there are no failures in it. so maybe these are being filtered for known failures. On 12/12/2012 05:03 PM, reed kotler wrote: > The first one failed on a diff: > ******************** TEST (simple) 'sse.expandfft' FAILED! > ******************** > Execution Context Diff: > /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: >

I use the 'make TEST=simple' as a pre-commit test. I think that everybody should run these tests before committing to LLVM. On Dec 12, 2012, at 5:06 PM, reed kotler <rkotler at mips.com> wrote: > when I create the report, there are no failures in it. so maybe these are being filtered for known failures. > > On 12/12/2012 05:03 PM, reed kotler wrote: >> The first

Thanks for your help! After I installed the sandbox to /tmp/mysandbox instead of ~/mysandbox, everything starts to work. It still looks weird though. My home folder is not symlinked by the way. Jingyue On Sat Aug 09 2014 at 10:59:49 AM Renato Golin <renato.golin at linaro.org> wrote: > On 9 August 2014 02:56, Jingyue Wu <jingyue at google.com> wrote: > > I got > >

> >  But I got the error message below, > > > > --- > > 2012-04-12 02:39:48: executing test modules > > 2012-04-12 02:39:49: loading nightly test data... > > nt.py:737: fatal error: nightly test failed, no report generated > > --- > > > >  Any idea on how I can figure out what the fatal error is? Thanks! > > Inside the sandbox there will

Hi Bill, The PPC LNT buildbot is randomly failing on LNT because of timeouts. http://lab.llvm.org:8011/builders/clang-ppc64le-linux-lnt I've checked all recent LNT failures and they were spotted on some processes (lua, sqlite3, tramp3d, expandfft, etc), so I doubt this is in any was a real time out due to code-gen issues. I imagine they're all at the edge already and the standard

I forgot to mention that you can also run "make TEST=simple report" which will generate a nice report. Do you know why these tests fail ? You can step into the test directory and run 'make TEST=simple' from there. It will save you some time. On Dec 12, 2012, at 4:04 PM, reed kotler <rkotler at mips.com> wrote: > I'm getting three failures. > > TEST-FAIL:

I'm getting three failures. TEST-FAIL: exec /home/rkotler/llvmpb3/build/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.expandfft TEST-RESULT-exec-time: user 0.3200 TEST-RESULT-exec-real-time: real 0.3172 TEST-FAIL: exec /home/rkotler/llvmpb3/build/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.stepfft TEST-RESULT-exec-time: user 0.4000