Repository navigation
ci: prune merged branch triggers and steady the emulator jobs - #350
Merged
Merged
Conversation
Drops push triggers for eleven feat/native-* branches already merged into main. Gives the private-node recording emulator 3 GB of RAM and 6 GB of disk, since it was dying during the 256 MiB upload cases, and caches the system image and AVD for both emulator jobs to ride out corrupt SDK downloads.
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.
feat/native-*branches already merged into main. The 30 unmerged ones stay.recording-private-node-emulator:ram-size: 3072Manddisk-size: 6000M. Seven of nine recent failures were the emulator vanishing during the 256 MiB upload cases (adb offline, no app crash), mostly ongoogle_apis. The emulator had default RAM, while the other recording jobs already set 2048M.actions/cachestep (v5, SHA-pinned) for the system image and AVD. This rides out theError on ZipFilecorrupt SDK downloads seen in five runs.Check on the first run
${{ env.ANDROID_HOME }}, whichsetup-androidexports earlier in each job.-v1. Bump it if a corrupt image is ever cached.Gate: CI configuration only, so no app or data-flow change.