Repository navigation
Conversation
Coverage (unit tests)Compared against
Line and branch coverage from unit test reports. History is recorded on the |
Contributor
Coverage (instrumentation tests)
|
Collaborator
Author
|
Validation run on this branch (workflow_dispatch, ubuntu-latest with KVM): https://github.com/googlemaps/android-maps-compose/actions/runs/40095704517
The run on this PR itself shows as skipped because the PR is a draft, which is the new draft rule working. |
This branch has not been deployed
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 instrumentation tests are the only workflow in this repo on a billed runner (
macOS-latest-large), and they now account for most of the org's Actions spend. Jobs are currently not even starting because the spending limit was reached.In the last 30 days the workflow ran 136 macOS larger runner jobs, about 2,600 minutes (around 19 minutes each). Part of that was spent on runs that could not catch anything: release-please PRs (225 minutes), Dependabot PRs, docs-only PRs and superseded pushes that kept running.
This PR:
ubuntu-latestwith KVM, the same setupdemo-smoke-test.ymlalready uses successfully (10 to 13 minutes per run). Standard runners are free for public repositories. The emulator stays on API 29google_apis, moving fromx86tox86_64, which is the image Ubuntu runs with acceleration.CODEOWNERS,dependabot.yml, draft PRs (the run starts onready_for_review) and release-please PRs. Workflow changes still run, so a bumped action is exercised before it merges.run-instrumentation-testis not a required check, so skipped runs never block a merge. The post-mergeRecord coverage historyworkflow already handles a missing, cancelled or skipped emulator run by recording unit coverage only; the only change there is a comment that mentioned the macOS runner. Job, workflow file and artifact names are unchanged, so it keeps finding the run.Validation: since this PR is a draft, its own instrumentation run is skipped by design. I triggered the workflow manually on this branch (
workflow_dispatchuses the branch's file) to check the suite on the Ubuntu emulator, and will post the result here before marking it ready.