-
Notifications
You must be signed in to change notification settings - Fork 135
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
checkImplicitDependenciesTest flake #1285
Comments
I've opened #1287 to fix the confusing suggested configuration. |
schlosna
added a commit
to palantir/tritium
that referenced
this issue
Apr 15, 2020
Papering over problem in `checkImplicitDependencies` that needs to be fixed, see palantir/gradle-baseline#1285
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Appears there was a flake in
checkImplicitDependenciesTest
for https://app.circleci.com/jobs/github/palantir/tritium/7611 with the error below. I triggered a rerun https://app.circleci.com/jobs/github/palantir/tritium/7653 that succeeded without any changes.Slightly tangential and probably a separate FR is that the fix suggestions for any of the
checkImplicitDependenciesTest
tasks should suggesttestImplementation
and notimplementation
What did you want to happen?
Ideally the dependency checks should be consistent and idempotent
The text was updated successfully, but these errors were encountered: