similar to: [LLVMdev] tools build issue with lnt in cross platform testing

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

> > 1. I checked out and built llvm, clang, and test-suite from svn tip. > When I > > run llvm/test *without* my changes on x86, I see 3 failures. Is it > expected? > > I was expecting svn tip on x86 to be clean. Is there a nightly > regression > > result available somewhere that I can check for broken tests. Here is > the > > report from my log: > >

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 Jul 28, 2011, at 8:18 AM, Sundeep wrote: >>> 1. I checked out and built llvm, clang, and test-suite from svn tip. >> When I >>> run llvm/test *without* my changes on x86, I see 3 failures. Is it >> expected? >>> I was expecting svn tip on x86 to be clean. Is there a nightly >> regression >>> result available somewhere that I can check for

Reed, On Nov 7, 2011, at 2:11 PM, reed kotler wrote: > We have a modified version of projects/test-suite that we can run cross > using Qemu. > > We would like to put that back so that other people can test MIPS > before putting back. > Well, this would be easily modifiable for ARM and other targets that are > supported by QEMU. > > But in this case, we would need

Hi all, The LLVM benchmarking system produces very noisy results even on quiet machines. One of the sources of inaccuracy is the timing tool we are using. Because it is a user-space tool, the OS can context switch it and we will get an outlier result. Perf stat uses SW_TASK_CLOCK counter in kernel to measure time, therefore more accurate. It also does not get context switched. I've

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

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

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

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 am not sure if this is the right forum. Please direct me to the appropriate place if it isn't so. Please keep in CC as i am not subscribed to this mailing list. I am trying to test riscv llvm tools in QEMU using llvm testsuite. As a trial i am trying only the Single Source C Regression folder. The steps that i took are : ]$ cmake -DCMAKE_C_COMPILER=/opt/riscv-tools/bin/clang

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

Hi, people. A tiny suggestion for the system.time function. Could the returned vector have names? These could be like: c("User", "System", "Elapsed", "Sub.User", "Sub.System") That would then produce self-documenting output. -- Fran?ois Pinard http://pinard.progiciels-bpi.ca

Hello everyone, I am working to run the LLVM Nightly Testsuite on embedded arm devices. Not all of these devices can mount NFS to share a common directory tree. To mitigate this I have patched test-suite/RunSafely.sh (attached) to create a temporary directory, run the test remotely, collect the output, and cleanup after itself. The patch breaks compatibility with the current remote device model

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

> On Feb 27, 2017, at 1:36 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Mikael, > > Some noisiness in benchmark results is expected, but the numbers you see seem to be higher than I'd expect. > A number of tricks people use to get lower noise results are (with the lnt runtest nt command line options to enable it between brackets): > *

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 >

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