Conversation
…auncherTest The ALL_SOURCE classpath assertion failed once in CI (INRIA#6890) with an empty classpath and passed on rerun. An empty classpath means a spoon.classpath*.tmp file existed but was empty; since cached files younger than 1h are reused without invoking Maven, a stale empty file (copied from the working directory along with the project) is the prime suspect. On failure, report path, size, mtime and content of the cached classpath files in both the copied project and the working directory. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
`MavenLauncherTest.spoonMavenLauncherTest` failed once in #6890 (`expected: not equal but was: <0>` on the ALL_SOURCE classpath) and passed on rerun.
An empty classpath means a `spoon.classpath*.tmp` file existed but was empty (a missing file throws instead). Cached files younger than 1h are reused without invoking Maven, and the test copies the whole working directory, including its cached files, into `spooned/`. A stale empty file is the prime suspect: planting an empty `spoon.classpath.tmp` at the repo root reproduces the exact failure locally.
This PR only adds a failure message listing path, size, mtime and content of the cached classpath files in both the copied project and the working directory, so the next occurrence tells us where the empty file came from.
🤖 Generated with Claude Code