(replying on list in case others are interested, Renato sent me the
log offline).
Okay, I found problem, the MultiSource/Applications/Burg test is
breaking the running of the test suite because it can't find yacc. Can
you file a bugzilla for this? We should just add a configure check or
something to make sure that doesn't cause the test suite to fall over.
You should be able to work around it by installing yacc.
- Daniel
On Sun, Oct 28, 2012 at 11:27 AM, Daniel Dunbar <daniel.dunbar at
gmail.com> wrote:> On Oct 28, 2012, at 11:19, Renato Golin <rengolin at systemcall.org>
wrote:
>
>> On 28 October 2012 17:32, Daniel Dunbar <daniel.dunbar at
gmail.com> wrote:
>>> Exactly how are you running the tests? Via LNT or directly?
>>
>> Via LNT, like this:
>>
>> ./sandbox/bin/python sandbox/bin/lnt runtest nt \
>> --sandbox sandbox \
>> --test-suite ~/devel/llvm/test-suite \
>> --cc ~/devel/llvm/debug/bin/clang++
>
> You probably make --cc be clang not clang++, but I wouldn't expect
> that to fatally break the running of the tests.
>
> The test suite makefiles can be pretty fragile. If you send me the
> test.log file I will take a look. If you want to try running on a
> smaller subset you can ad something like "--only-test
> SingleSource/UnitTests".
>
> - Daniel
>
>>> If via LNT, make sure you test suite repository is clean (no in
tree
>>> configure or make results).
>>
>> $ git status
>> # On branch master
>> nothing to commit (working directory clean)
>>
>> cheers,
>> --renato