Fix test bugs introduced in b22024802.
Review Request #2483 - Created July 14, 2015 and submitted
|gmalmquist, stuhood, zundel|
That change turned on artifact caching globally in tests.
The outcome was that many tests were actually not doing anything.
Instead, they were reading from the real artifact cache.
So, for example, the antlr gen test wasn't running antlr - it was
finding the expected outputs in the cache...
This commit removes the code that turned universal caching on,
and then re-enables caching just for tool bootstrapping, for test
This fixed the weird issue with antlr gen, so that large comment
is gone too.
Incidentally, this commit also changes the way we register the
source root in the antlr gen test. Instead of eval'ing it in a
BUILD file it just registers it directly, as other tests do.
CI passes: https://travis-ci.org/pantsbuild/pants/builds/71004749
You should probably add Garrett as a reviewer, he had to do this: https://github.com/pantsbuild/pants/blob/master/tests/python/pants_test/backend/codegen/tasks/test_simple_codegen_task.py#L28 Looks like that comment + code can go now too.
Revision 2 (+36 -67)
Pushing based on the CI passing and John's earlier shipit (prior to a small followup commit), because right now many of our tests aren't doing anything.
Status: Closed (submitted)
Submitted as deae13386b7dac5d05a310c45034d70718c38020.
At first I was concerned that this would turn on caching for all of the test parts in tests like test_bundle_create.py test_binary_create.py, etc that subclass JvmToolTaskTestBase, but I see you you are just turning it on for the jvm bootstrap part of the task, so LGTM
nit: We don't need clean=True here, its already a freshly made temporary dir