Gradle

Before this commit, a force or substitution was not detected by

dependency locking and would allow a user to have a graph result that

differed from the lock state.

With this commit, such differences are now properly reported and will

fail resolution when identified.

Closes #8971

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

Since 24.1, Guava included a change that made ImmutableSet.Builder with unspecified expected size allocate a lot more memory for many items. We haven't bumped into this problem before, because we used the Android variant of Guava that somehow didn't contain the regressing change. With moving to the Java 8 variant we now have to deal with this problem.

See https://github.com/google/guava/issues/3223 for more details.

This reverts commit b3c791db65d344ddbe1878b56db41761db385aa5, reversing

changes made to 29c75bff79d89cfd6f69335a6bd056f1bdf1d160.

This closes https://github.com/gradle/gradle-private/issues/1735

We want to mark the known performance test scenarios in the report even when they pass. This can give us insights of how the scenarios work previously. In this way, we can easily know, "this scenario fails, ah, it's marked as flaky", or, "this scenario is improved, but hold on, it's marked as flaky, let's not rebaseline it".