> I don't get this directory called "lldb-test-traces" in my root build dir
(with a ninja build). My build directory is ~/src/staging/build/ and I just
ran some tests as follows:
Ah ok - the lldb-test-traces directory is really a manifestation of a flag
added to the 'ninja check-lldb' target or the 'make -C tools/lldb/test'
target. If you don't use those, and you don't use another flag to
dotest.py (I think -s off the top of my head), then it will default to a
date/timestamp-based directory. You are looking in the right place for the
way you ran it (although those dirs will add up unless you do a 'rm -rf
2014-*' occasionally).
Glad the error went away after a fresh sync!
On Wed, Jul 23, 2014 at 1:39 AM, Matthew Gardiner <m...@csr.com> wrote:
> Todd Fiala wrote:
>
>>
>> doesn't elsewhere. The test run should have made a directory called
>> "lldb-test-traces". They go in different places depending on ninja vs.
>> make builds. In ninja builds, it will be in your root build dir. In make
>> builds it will be in the {my-build-dir}/tools/lldb/test dir. In that
>> directory, you get a trace log file (*) for every test run that did not
>> succeed - either because it was skipped, it failed (i.e. test assertion
>> failed), it had an error (i.e. it failed but not because of an assert -
>> something happened that was entirely unexpected like an i/o issue, seg
>> fault, etc.), or it unexpectedly passed - marked xfail but succeeded. So -
>> you should have a file called something like "Failed*test_stdcxx_disasm*.log"
>> in that directory. You could look at the contents of that and see what
>> failed.
>>
>
> I don't get this directory called "lldb-test-traces" in my root build dir
> (with a ninja build). My build directory is ~/src/staging/build/ and I just
> ran some tests as follows:
>
>
> ~/src/staging/llvm/tools/lldb/test
> $LD_LIBRARY_PATH=/home/mg11/src/staging/build/lib/
> PYTHONPATH=/home/mg11/src/staging/build/lib/python2.7/site-packages/
> python dotest.py --executable=/home/mg11/src/staging/build/bin/lldb -v
> --compiler=gcc -q .
>
> Instead my log files, it seems, are under here:
>
> ~/src/staging/llvm/tools/lldb/test/2014-07-23-09_19_57
>
> Perhaps the destination of the log-files is effected by certain dotest.py
> arguments and environment variables. I do see some *LOG* environment
> variables inspected in the python, but I've not pursued this in anger.
>
> Matt
>
>
>
>
> Member of the CSR plc group of companies. CSR plc registered in England
> and Wales, registered number 4187346, registered office Churchill House,
> Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
> More information can be found at www.csr.com. Keep up to date with CSR on
> our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people,
> YouTube, www.youtube.com/user/CSRplc, Facebook,
> www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at
> www.twitter.com/CSR_plc.
> New for 2014, you can now access the wide range of products powered by
> aptX at www.aptx.com.
>
--
Todd Fiala | Software Engineer | tfi...@google.com | 650-943-3180
_______________________________________________
lldb-dev mailing list
lldb-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
