Skip to content

Assert guard execution in non-upload evidence regressions - #16

Closed
perNyfelt wants to merge 1 commit into
mainfrom
feature/assert-non-upload-guard-execution
Closed

perNyfelt wants to merge 1 commit into
mainfrom
feature/assert-non-upload-guard-execution

Conversation

@perNyfelt

Copy link
Copy Markdown
Member

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.

@perNyfelt

Copy link
Copy Markdown
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.

@perNyfelt perNyfelt closed this Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant