Conversation
Convert the skipped "Build application.a (dependency content changes)" integration test from test.serial.skip to test.serial.failing. Its assertions already encode the desired behavior: a dependency content change should invalidate the application's result cache and trigger a rebuild. It currently fails because the custom task reads dependencies via taskUtil.getProject().getReader(), a path not tracked by the caching system's ResourceRequestManager, so dependency changes do not invalidate the cache. Marking it failing (instead of skipping) keeps CI green while turning the gap into a live signal that flips to a hard error once the behavior is fixed.
d3xter666
approved these changes
Sep 18, 2026
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
2 participants
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.
Convert the skipped "Build application.a (dependency content changes)" integration test from test.serial.skip to test.serial.failing. Its assertions already encode the desired behavior: a dependency content change should invalidate the application's result cache and trigger a rebuild.
It currently fails because the custom task reads dependencies via taskUtil.getProject().getReader(), a path not tracked by the caching system's ResourceRequestManager, so dependency changes do not invalidate the cache. Marking it failing (instead of skipping) keeps CI green while turning the gap into a live signal that flips to a hard error once the behavior is fixed.