You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had some reports of binary store exceptions in our internal spring distribution when trying snapshot/milestone dependencies.
This project has ~30 submodules and reproduce all the issues might be difficult because I'm seeing a few of the modules having binary store exceptions. What is interesting is that only happens in testCompileClasspath or testRuntimeClasspath, related to org.hamcrest:hamcrest-core:2.. It appears to be related to a platform rule per exception details:
Caused by: java.lang.IllegalStateException: Corrupt serialized resolution result. Cannot find selected module (149) for constraint platform-runtime -> org.hamcrest:hamcrest-core:2.2
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.DefaultResolutionResultBuilder.visitOutgoingEdges(DefaultResolutionResultBuilder.java:82)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:237)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:130)
... 199 more
If you clone the repo and execute ./gradlew :my-submodule:dependencies --configuration integTestRuntimeClasspath you should be able to see:
* What went wrong:
Execution failed for task ':my-submodule:dependencies'.
> Failed to notify dependency resolution listener.
> Could not resolve all dependencies for configuration ':my-submodule:integTestRuntimeClasspathCopy'.
> Problems reading data from Binary store in /private/var/folders/hb/c0ghc68d7vn26h4ny84kzv0r0000gn/T/gradle1676642303220288846.bin offset 12425 exists? true
> Could not resolve all dependencies for configuration ':my-submodule:integTestRuntimeClasspathCopy'.
> Problems reading data from Binary store in /private/var/folders/hb/c0ghc68d7vn26h4ny84kzv0r0000gn/T/gradle1676642303220288846.bin offset 12425 exists? true
Prior to this fix the same dependency state could lead to duplicate
outgoing edges which would cause an issue when the node targeted was
removed because it was deselected.
The code now uses a datastructure that will perform the de duplication
and it no longer registers entries in some code paths.
Fixes#13551
Current Behavior
We had some reports of binary store exceptions in our internal spring distribution when trying snapshot/milestone dependencies.
This project has ~30 submodules and reproduce all the issues might be difficult because I'm seeing a few of the modules having binary store exceptions. What is interesting is that only happens in
testCompileClasspath
ortestRuntimeClasspath
, related toorg.hamcrest:hamcrest-core:2.
. It appears to be related to a platform rule per exception details:I was able to isolate one of them in https://github.com/nebula-plugins/gradle-nebula-integration/tree/master/binary-store-issue-05142020.
If you clone the repo and execute
./gradlew :my-submodule:dependencies --configuration integTestRuntimeClasspath
you should be able to see:Your Environment
Gradle 6.6-20200617074346+0000
Build scan URL: https://scans.gradle.com/s/7cxwbvnedtp6u
The text was updated successfully, but these errors were encountered: