-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Display more information on negative avoidance message #186
Comments
Thanks for bringing this up @NikolayMetchev . The way the time difference is measured is different between the Gradle Doctor and Gradle Enterprise. Neither value is 100% accurate. Nor is it possible for either calculation to account for potential differences in the environment between the build pulling form the build cache and the build that populated the build cache. If you are seeing a lot of false positives, you can adjust the value for The value that Gradle Doctor uses to estimate this value is the Build Cache entry's |
Hi Nelson, As it is now I am just ignoring those messages as noise. If I were to have more info easily accessible perhaps I can make a more informed decision about adjusting the gradle doctor settings or the task configuration. |
@runningcode Do you know how Gradle Enterprise compute this? I am also seeing warnings from this plugin that don't seem to hold true compared to what I see in the Gradle enterprise UI. |
It appears that it should be possible to add the delta here, as well as the original build ID?
Would you accept a PR for this if this is possible? |
Something I have noticed is that probably Gradle enterprise ignore the fingerprinting inputs` duration, whereas Gradle doctor considers it? |
It would be good when gradle doctor prints out which tasks took longer to be loaded from cache then a re-run would have taken for it to also print the time it thinks a re-run would have taken and how long loading from cache took.
I looked in the build scan and for the tasks that gradle doctor is pointing out gradle enterprise does not agree that loading from cache took longer.
The text was updated successfully, but these errors were encountered: