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 "(branch rev)" at the end, ok hard-coded it to "(branch rev)" and got a new error: $ sandbox/bin/python sandbox/bin/lnt runtest nt --sandbox sandbox --cc debug/bin/clang++ --test-suite test-suite nt.py:1197: note: inferred C++ compiler under test as: '/home/rengolin/devel/llvm/debug/bin/clang++' 2012-10-26 21:43:48: checking source versions 2012-10-26 21:43:49: scanning for LNT-based test modules 2012-10-26 21:43:49: found 0 LNT-based test modules 2012-10-26 21:43:49: using nickname: 'brubeck__clang_DEV__x86_64' 2012-10-26 21:43:49: starting test in '/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48' 2012-10-26 21:43:49: configuring... 2012-10-26 21:43:56: building test-suite tools nt.py:748: fatal error: unable to build tools, aborting! Going to the dir where it built, and typing: $ make -C tools/ make: Entering directory `/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools' make -C /home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools all \ ORIGINAL_CC="cc" \ ORIGINAL_CXX="cc" o timeit-target /home/rengolin/devel/llvm/test-suite/tools/timeit.c -O3 make: o: Command not found make: [timeit-target] Error 127 (ignored) E -o TargetConfig.mk -x c /home/rengolin/devel/llvm/test-suite/tools/TargetConfig.mk.in make: E: Command not found make: [TargetConfig.mk] Error 127 (ignored) ... o? E? Might be environment messup, but I'm a little lost. Does this work out-of-the box to anyone? -- cheers, --renato http://systemcall.org/
I hit the same problems as you did when I tried it a few weeks ago. Haven't bothered with it since. There is a way to run tests without using lnt. You can use the Makefiles directly in your test-suite build directory. For running nightly tests, you can do: make report.html TEST=nightly That will generate a html file with the test results in. Amara On 26 October 2012 22:53, Renato Golin <rengolin at systemcall.org> wrote:> 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 "(branch rev)" at the end, ok > hard-coded it to "(branch rev)" and got a new error: > > $ sandbox/bin/python sandbox/bin/lnt runtest nt --sandbox sandbox --cc > debug/bin/clang++ --test-suite test-suite > nt.py:1197: note: inferred C++ compiler under test as: > '/home/rengolin/devel/llvm/debug/bin/clang++' > 2012-10-26 21:43:48: checking source versions > 2012-10-26 21:43:49: scanning for LNT-based test modules > 2012-10-26 21:43:49: found 0 LNT-based test modules > 2012-10-26 21:43:49: using nickname: 'brubeck__clang_DEV__x86_64' > 2012-10-26 21:43:49: starting test in > '/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48' > 2012-10-26 21:43:49: configuring... > 2012-10-26 21:43:56: building test-suite tools > nt.py:748: fatal error: unable to build tools, aborting! > > Going to the dir where it built, and typing: > > $ make -C tools/ > make: Entering directory > `/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools' > make -C /home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools all \ > ORIGINAL_CC="cc" \ > ORIGINAL_CXX="cc" > o timeit-target /home/rengolin/devel/llvm/test-suite/tools/timeit.c -O3 > make: o: Command not found > make: [timeit-target] Error 127 (ignored) > E -o TargetConfig.mk -x c > /home/rengolin/devel/llvm/test-suite/tools/TargetConfig.mk.in > make: E: Command not found > make: [TargetConfig.mk] Error 127 (ignored) > ... > > o? E? Might be environment messup, but I'm a little lost. Does this > work out-of-the box to anyone? > > -- > cheers, > --renato > > http://systemcall.org/ > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
[+Daniel, in case he knows what's going on here] On Fri, Oct 26, 2012 at 3:56 PM, Amara Emerson <amara.emerson at gmail.com> wrote:> I hit the same problems as you did when I tried it a few weeks ago. > Haven't bothered with it since. > > There is a way to run tests without using lnt. You can use the > Makefiles directly in your test-suite build directory. For running > nightly tests, you can do: > make report.html TEST=nightly > > That will generate a html file with the test results in. > > Amara > > On 26 October 2012 22:53, Renato Golin <rengolin at systemcall.org> wrote: >> 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 "(branch rev)" at the end, ok >> hard-coded it to "(branch rev)" and got a new error: >> >> $ sandbox/bin/python sandbox/bin/lnt runtest nt --sandbox sandbox --cc >> debug/bin/clang++ --test-suite test-suite >> nt.py:1197: note: inferred C++ compiler under test as: >> '/home/rengolin/devel/llvm/debug/bin/clang++' >> 2012-10-26 21:43:48: checking source versions >> 2012-10-26 21:43:49: scanning for LNT-based test modules >> 2012-10-26 21:43:49: found 0 LNT-based test modules >> 2012-10-26 21:43:49: using nickname: 'brubeck__clang_DEV__x86_64' >> 2012-10-26 21:43:49: starting test in >> '/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48' >> 2012-10-26 21:43:49: configuring... >> 2012-10-26 21:43:56: building test-suite tools >> nt.py:748: fatal error: unable to build tools, aborting! >> >> Going to the dir where it built, and typing: >> >> $ make -C tools/ >> make: Entering directory >> `/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools' >> make -C /home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools all \ >> ORIGINAL_CC="cc" \ >> ORIGINAL_CXX="cc" >> o timeit-target /home/rengolin/devel/llvm/test-suite/tools/timeit.c -O3 >> make: o: Command not found >> make: [timeit-target] Error 127 (ignored) >> E -o TargetConfig.mk -x c >> /home/rengolin/devel/llvm/test-suite/tools/TargetConfig.mk.in >> make: E: Command not found >> make: [TargetConfig.mk] Error 127 (ignored) >> ... >> >> o? E? Might be environment messup, but I'm a little lost. Does this >> work out-of-the box to anyone? >> >> -- >> cheers, >> --renato >> >> http://systemcall.org/ >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On Fri, Oct 26, 2012 at 2:53 PM, Renato Golin <rengolin at systemcall.org> wrote:> 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 'Fixed LNT to recognize this compiler in http://llvm.org/viewvc/llvm-project?view=rev&revision=166842> Seems my string doesn't have a "(branch rev)" at the end, ok > hard-coded it to "(branch rev)" and got a new error: > > $ sandbox/bin/python sandbox/bin/lnt runtest nt --sandbox sandbox --cc > debug/bin/clang++ --test-suite test-suite > nt.py:1197: note: inferred C++ compiler under test as: > '/home/rengolin/devel/llvm/debug/bin/clang++' > 2012-10-26 21:43:48: checking source versions > 2012-10-26 21:43:49: scanning for LNT-based test modules > 2012-10-26 21:43:49: found 0 LNT-based test modules > 2012-10-26 21:43:49: using nickname: 'brubeck__clang_DEV__x86_64' > 2012-10-26 21:43:49: starting test in > '/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48' > 2012-10-26 21:43:49: configuring... > 2012-10-26 21:43:56: building test-suite tools > nt.py:748: fatal error: unable to build tools, aborting!Can you include the output of build-tools.log in that directory, please?> Going to the dir where it built, and typing: > > $ make -C tools/ > make: Entering directory > `/home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools' > make -C /home/rengolin/devel/llvm/sandbox/test-2012-10-26_21-43-48/tools all \ > ORIGINAL_CC="cc" \ > ORIGINAL_CXX="cc" > o timeit-target /home/rengolin/devel/llvm/test-suite/tools/timeit.c -O3 > make: o: Command not found > make: [timeit-target] Error 127 (ignored) > E -o TargetConfig.mk -x c > /home/rengolin/devel/llvm/test-suite/tools/TargetConfig.mk.in > make: E: Command not found > make: [TargetConfig.mk] Error 127 (ignored) > ... > > o? E? Might be environment messup, but I'm a little lost.The command you ran is not expected to work, the Makefiles depend on getting a lot of variables passed in, when run in the way LNT runs them (that is, without piggy backing off of an LLVM installation).> Does this > work out-of-the box to anyone?Yup! :) - Daniel> > -- > cheers, > --renato > > http://systemcall.org/ > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On 27 October 2012 01:17, Daniel Dunbar <daniel at zuster.org> wrote:> Can you include the output of build-tools.log in that directory, please?Ah, yes! Relative path on clang++ binary. I understand why it works to get the version but not here (different paths). Would be good to have some warning (or even an error) if one passes a relative path. Or, possibly, save the current path and pass it to the compiler during the tests. Nothing critical, just for consistency. It's running now, thanks! -- cheers, --renato http://systemcall.org/