-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build only: TestProvisioner has become very flaky #429
Comments
Since updating the gradle version, this has become a frequent problem. We should disable travis caching until we can resolve this. |
Build caching is turned back on. I'm not super confident that it is really fixed, but my box had problems, and those problems are now fixed, so I'm closing this for now. |
It's now failing close to 100% of the time, but only for |
… be flaky and we can close-out #429.
Finally fixed! Huzzah! |
Failure
Since the PR's passed before they failed, it seems to be a flaky sort of failure - the very best kind!!
On my box, I get a different failure:
After I removed the travis cache, the build passed (or at least revealed an easy-to-fix bug in #426). I think it must be that
TestProvisioner
is somehow gunking up gradle's artifact resolution. On my machine, agit clean -d -X -f
did not fix the problem. Neither did nuking~/.gradle/caches
...We've got a man on the inside now ;-) . Hey @JLLeitschuh, we want to turn a list of maven coordinates into files on our harddrive inside of test code. Do you know of a better gradle API to accomplish this?
spotless/testlib/src/main/java/com/diffplug/spotless/TestProvisioner.java
Lines 53 to 68 in babc574
The text was updated successfully, but these errors were encountered: