[PATCH] D20252: surface build error content through test event system

[Todd Fiala via llvm-commits]

tfiala added a comment.

As an example of output, here's what the textual output for a (force, contrived) build error looks like now:

  Configuration: arch=x86_64 compiler=clang
  ----------------------------------------------------------------------
  Collected 2 tests
  
  ======================================================================
  ERROR: test_typedef_dsym (Testtypedef.TypedefTestCase)
     Test 'image lookup -t a' and check for correct display at different scopes.
  ----------------------------------------------------------------------
  Error when building test subject.
  
  Test Directory:
  /Volumes/Data/src/lldb-llvm.org/lldb/packages/Python/lldbsuite/test/lang/c/typedef
  
  Build Command:
  make MAKE_DSYM=YES ARCH=x86_64 CC="clang"
  
  Build Output:
  main.c:10:10: fatal error: 'idontexist.h' file not found
  #include <idontexist.h>
           ^
  1 error generated.
  make: *** [main.o] Error 1
  
  ======================================================================
  ERROR: test_typedef_dwarf (Testtypedef.TypedefTestCase)
     Test 'image lookup -t a' and check for correct display at different scopes.
  ----------------------------------------------------------------------
  Error when building test subject.
  
  Test Directory:
  /Volumes/Data/src/lldb-llvm.org/lldb/packages/Python/lldbsuite/test/lang/c/typedef
  
  Build Command:
  make MAKE_DSYM=NO ARCH=x86_64 CC="clang"
  
  Build Output:
  main.c:10:10: fatal error: 'idontexist.h' file not found
  #include <idontexist.h>
           ^
  1 error generated.
  make: *** [main.o] Error 1
  
  ----------------------------------------------------------------------
  Ran 2 tests in 0.754s
  
  RESULT: FAILED (0 passes, 0 failures, 2 errors, 0 skipped, 0 expected failures, 0 unexpected successes)
  Session logs for test failures/errors/unexpected successes can be found in directory '2016-05-13-11_42_40'

That's much more informative as to what went wrong.  Previously we'd just get a Python backtrace that said one of the build routines failed, with no output as to what build failure occurred.


http://reviews.llvm.org/D20252