perf: speed up shorebird_tests with template project and Gradle cache#108
Merged
eseidel merged 2 commits intoshorebird/devfrom Feb 3, 2026
Merged
perf: speed up shorebird_tests with template project and Gradle cache#108eseidel merged 2 commits intoshorebird/devfrom
eseidel merged 2 commits intoshorebird/devfrom
Conversation
- Create a template Flutter project once in setUpAll and copy it per test, avoiding repeated `flutter create` calls - Run a warm-up `flutter build apk` in setUpAll (outside per-test timeout) to prime the Gradle cache - Add actions/cache for ~/.gradle so subsequent CI runs start warm - Add VERBOSE env var and failure output logging from #107
Author
|
We should immediately see this in faster CI times... (with less flake) if we don't then something didn't work. |
When the GHA Gradle cache is restored, skip the throwaway APK build since the cache is already warm. This saves ~4 minutes on cache-hit runs.
bdero
approved these changes
Feb 3, 2026
bdero
left a comment
bdero
left a comment
There was a problem hiding this comment.
Minor concern, but not blocking.
PR mentions adding a VERBOSE env var, but I don't see it in the diff?
bdero
pushed a commit
that referenced
this pull request
Feb 3, 2026
…#108) - Create a template Flutter project once in setUpAll and copy it per test, avoiding repeated `flutter create` calls - Run a warm-up `flutter build apk` in setUpAll (outside per-test timeout) to prime the Gradle cache - Add actions/cache for ~/.gradle so subsequent CI runs start warm - Add VERBOSE env var and failure output logging from #107
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.
Summary
setUpAlland copy it per test, avoiding repeatedflutter createcallsflutter build apkinsetUpAll(outside per-test timeout) to prime the Gradle cacheactions/cachefor~/.gradleso subsequent CI runs start warmThis should fix the flaky 6-minute timeout failures on macOS by moving the expensive first-build overhead outside the per-test timeout.
Test plan