This is an archive of the discontinued LLVM Phabricator instance.

[test-suite] Move lit test result codes into llvm/lit
Needs ReviewPublic

Authored by jdoerfert on Apr 12 2020, 5:55 PM.

Details

Summary

In D77986 we moved these result codes into llvm/lit, now we use
those definitions directly.

Depends on: D77986

Event Timeline

jdoerfert created this revision.Apr 12 2020, 5:55 PM
yln added a subscriber: yln.Apr 13 2020, 2:48 PM
yln added inline comments.
litsupport/test.py
38

I think the existing category of UNRESOLVED would be a good semantic fit here.

jdoerfert marked an inline comment as done.Apr 13 2020, 5:23 PM
jdoerfert added inline comments.
litsupport/test.py
38

I mentioned something similar in the other review [0] but FTR:

To me, unresolved doesn't capture the fact that the compile stage of the (lnt-based) process failed to produce an executable. Unresolved is a generic term which could mean a lo of things, e.g., some system dependence were missing, the architecture did not match, the source download failed, ...

[0] https://reviews.llvm.org/D77986#1979402