[lldb-dev] RFC: Making unit tests run by default on ninja check-lldb

Ying Chen via lldb-dev lldb-dev at lists.llvm.org
Tue Oct 20 16:51:52 PDT 2015


Hi Zachary,

The big unknown here is how to make the buildbots understand unit test
> failures and trigger a failure when ninja check-lldb-unit fails.
>

There're two conditions buildbot will identity a test step as failure.
One is that the command has non-zero return code.
The other is that there're failing codes in stdout message. (Refer to
LitTestCommand::evaluateCommand in this file
<https://github.com/llvm-mirror/zorg/blob/master/zorg/buildbot/commands/LitTestCommand.py>
.)
Failing codes are defined as:
    failingCodes = set(['FAIL', 'XPASS', 'KPASS', 'UNRESOLVED', 'TIMEOUT'])

So if the failures are print out as '^FAIL: (.*) \(.*\)', buildbot will
understand it's failing even if ninja check-lldb-unit returns 0.
Or we could add some logic to the above file to handle the output of unit
test.

Thanks,
Ying
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20151020/40a9bbe7/attachment-0001.html>


More information about the lldb-dev mailing list