Repository navigation
ci: stop main runs cancelling each other and drop the fake metrics - #140
Merged
Merged
Conversation
Four commits on main went unverified on 2026-09-22 because cancel-in-progress is keyed on workflow and ref, so each merge killed the run of the one before it. Cancelling stays on for branches. The dependency graph was being submitted twice. dependency-submission.yml already does it with contents: write; the copy here has no such permission and logged "Resource not accessible by integration" on every run. Capture Build Metrics printed fixed strings - "Unit tests: 34/34 passing", "Detekt: 0/0 issues", "Parallel Execution: 4+ threads" - none of them measured. Removed rather than faked. The APK guard warned above 8 MB against a 20.1 MB debug APK, so it fired every build. Raised to 24 MB, which is roughly 20% headroom.
Merged
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
1 participant
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.
Four things in
build.ymlthat either lie or fight the build.Main runs cancelled each other.
cancel-in-progressis keyed on workflow and ref, so each merge killed the run of the one before it. Four commits onmainwent unverified this way on 2026-09-22. Cancelling stays on for branches, off formain.The dependency graph was submitted twice.
dependency-submission.ymlalready does it, onmainpushes, withcontents: write. The copy passed to setup-gradle here has no such permission and loggedResource not accessible by integrationon every run since it was added.Capture Build Metricsprinted fixed strings.Unit tests: 34/34 passing,Detekt: 0/0 issues,Spotless: 100% formatted,Parallel Execution: 4+ threads. Nothing measured any of them, and the test count is already wrong. Removed rather than faked; the build scan and the JUnit report carry the real numbers.The APK guard warned on every build. Threshold 8 MB against a 20.1 MB debug APK. Raised to 24 MB, roughly 20% headroom over today's size. Worth tuning, or pointing at the release APK instead, which is the size that actually ships.