| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
I spend some time trying to get the LIT test suite passing. Here are the changes that I needed to make on my machine.
I made the following changes for the following reasons.
1. google-test.py: The Google test format now checks for "[ PASSED ] 1 test." to check if a test passes.
2. discovery.py: The output appears in a different order on my machine than it did in the test.
3. unittest-adaptor.py: The output appears in a different order on my machine than it did in the test.
4. The classname is now formed differently in `getJUnitXML(...)`.
I'm not sure what is causing the output order to differ in discovery.py and unittest-adaptor.py. Does anybody have any thoughts?
Reviewers: ddunbar, danalbert, jroelofs
Reviewed By: jroelofs
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D9864
llvm-svn: 239663
|
|
|
|
| |
llvm-svn: 190738
|
|
|
|
|
|
|
|
|
| |
- This is a work-in-progress and all details are subject to change, but I am
trying to build up support for allowing lit to be used as a driver for
performance tests (or other tests which might want to record information
beyond simple PASS/FAIL).
llvm-svn: 190535
|
|
|
|
|
|
|
| |
- This aligns with how existing test suites end up wanting to use the local
config files, conceptually it makes sense to consider them to be inherited.
llvm-svn: 189885
|
|
|
|
| |
llvm-svn: 189561
|
|
|
|
| |
llvm-svn: 188417
|
|
|
|
|
|
| |
- This cleans up the text output of failing tests when run under PY3.
llvm-svn: 188416
|
|
|
|
| |
llvm-svn: 188107
|
|
|
|
|
|
| |
the source test root.
llvm-svn: 179402
|
|
|
|
| |
llvm-svn: 179401
|
|
|
|
| |
llvm-svn: 179243
|
|
|
|
| |
llvm-svn: 174102
|
|
|
|
| |
llvm-svn: 174072
|
|
|
|
|
|
| |
- Also, add a test for it.
llvm-svn: 174019
|
|
llvm-svn: 174001
|