This is an archive of the discontinued LLVM Phabricator instance.

[LIT] Fix failing LIT tests
ClosedPublic

Authored by EricWF on May 19 2015, 2:27 PM.

Details

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?

Diff Detail

Event Timeline

EricWF updated this revision to Diff 26093.May 19 2015, 2:27 PM
EricWF retitled this revision from to [LIT] Fix failing LIT tests.
EricWF updated this object.
EricWF edited the test plan for this revision. (Show Details)
EricWF added reviewers: ddunbar, jroelofs, danalbert.
EricWF set the repository for this revision to rL LLVM.
EricWF added a subscriber: Unknown Object (MLST).
jroelofs accepted this revision.May 27 2015, 8:41 AM
jroelofs edited edge metadata.

LGTM

utils/lit/tests/unittest-adaptor.py
7

I don't know what controls the order, but I'm not sure we care? Maybe should make these CHECK-DAGs...

This revision is now accepted and ready to land.May 27 2015, 8:41 AM

One more note: why didn't the buildbots catch this?

One more note: why didn't the buildbots catch this?

I don't see anything that creates a check-lit rule in CMake or something similar for autoconf. My guess is that they never get run.

ping: @EricWF, you should commit this....

EricWF updated this revision to Diff 27632.Jun 12 2015, 11:54 PM
EricWF updated this object.
EricWF edited edge metadata.
  • fix tests
EricWF closed this revision.Jun 12 2015, 11:59 PM