Repository navigation
ci: run only the debug unit tests - #15
Merged
Merged
Conversation
The release variant has no sources or minification of its own, so ./gradlew test ran every unit test twice and took the test job past the two-minute limit.
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
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.
Summary
The
testjob runs./gradlew testDebugUnitTestinstead of./gradlew test.Why
./gradlew testruns the unit tests for both debug and release. The release variant has no source set or minification of its own, so the second run repeats the first. Onmain, the step took 1m55s and the job 2m33s, over the two-minute limit in the rootAGENTS.md.release.ymlstill builds the release variant.Evidence
This PR's CI run gives the new job duration.
Risk & Rollback
Reversibility: Reversible
Blast Radius: CI only. A release-only compile error would now first show up in
release.yml.