Repository navigation
Conversation
Member
Author
|
Superseded by #17, which covers the same follow-up with the log scoped to builds that schedule the guard and have digests set. |
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.
The non-upload evidence regressions now assert that releaseAllGuard succeeds on both the initial run and configuration-cache reuse, while releaseAll remains absent and no upload occurs. The parameterized cases cover bundleAll, releaseAllSigningCheck, and releaseAllGuard; the standalone :core:check case is removed.
Adds an informational message when releaseAll is not scheduled and a comment documenting the task-input timing assumption during graph configuration.
Validation:
./gradlew test --tests '*ModuleReleaseTest.nonUploadGraphsIgnoreExportedUploadEvidence'passed. Full-suite verification was not rerun for this commit; the earlier full build encountered Gradle test-results EOFException.