Skip to content

feat: add verbose mode and failure logging to shorebird_tests#107

Merged
eseidel merged 1 commit into
shorebird/devfrom
es/log_shorebird_tests
Apr 23, 2026
Merged

feat: add verbose mode and failure logging to shorebird_tests#107
eseidel merged 1 commit into
shorebird/devfrom
es/log_shorebird_tests

Conversation

@eseidel

@eseidel eseidel commented Feb 3, 2026

Copy link
Copy Markdown

Summary

  • Gate line-by-line streaming output behind VERBOSE env var
  • Dump stdout/stderr on command failure (when not already streaming)
  • Set VERBOSE=1 in CI workflow for shorebird tests

Follow-up to #106.

Test plan

  • Verify CI logs show streaming output for each flutter command
  • Verify failure output is dumped when a command fails

eseidel added a commit that referenced this pull request Feb 3, 2026
- 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
eseidel added 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
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
bdero pushed a commit that referenced this pull request Feb 11, 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
@bdero bdero force-pushed the shorebird/dev branch 2 times, most recently from 54cd693 to 2706fb5 Compare February 13, 2026 23:33
bdero pushed a commit that referenced this pull request Feb 13, 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
bdero pushed a commit that referenced this pull request Feb 21, 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
bdero pushed a commit that referenced this pull request Mar 2, 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
bdero pushed a commit that referenced this pull request Mar 5, 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
bdero pushed a commit that referenced this pull request Mar 10, 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
bdero pushed a commit that referenced this pull request Mar 24, 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
bdero pushed a commit that referenced this pull request Mar 27, 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
bdero pushed a commit that referenced this pull request Apr 20, 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
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
@eseidel eseidel force-pushed the es/log_shorebird_tests branch from 6c462e7 to 2f00918 Compare April 21, 2026 17:32
@eseidel eseidel enabled auto-merge (squash) April 21, 2026 17:35
@eseidel eseidel requested a review from bdero April 21, 2026 17:35
@eseidel

eseidel commented Apr 21, 2026

Copy link
Copy Markdown
Author

The shorebird ci failure is just that shorebird ci doesn't know how to run flutter repo tests which are themselves standard since they have a flutter version of 0.0.0.

Comment thread packages/shorebird_tests/test/shorebird_tests.dart
@eseidel eseidel merged commit 86c9362 into shorebird/dev Apr 23, 2026
7 of 9 checks passed
@eseidel eseidel deleted the es/log_shorebird_tests branch April 23, 2026 03:34
bdero pushed a commit that referenced this pull request Apr 27, 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
bdero pushed a commit that referenced this pull request Apr 27, 2026
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
bdero pushed a commit that referenced this pull request Apr 30, 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
bdero pushed a commit that referenced this pull request Apr 30, 2026
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
bdero pushed a commit that referenced this pull request Jun 1, 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
bdero pushed a commit that referenced this pull request Jun 1, 2026
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
mrnpro pushed a commit to Flutter-Code-Push/flutter that referenced this pull request Jun 16, 2026
…shorebirdtech#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 shorebirdtech#107
mrnpro pushed a commit to Flutter-Code-Push/flutter that referenced this pull request Jun 16, 2026
…irdtech#107)

Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
bdero pushed a commit that referenced this pull request Jun 22, 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
bdero pushed a commit that referenced this pull request Jun 22, 2026
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
bdero pushed a commit that referenced this pull request Jun 25, 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
bdero pushed a commit that referenced this pull request Jun 25, 2026
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
bdero pushed a commit that referenced this pull request Jul 7, 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
bdero pushed a commit that referenced this pull request Jul 7, 2026
Stream subprocess output in real time when VERBOSE is set, and dump
stdout/stderr on failure. This helps diagnose flaky timeout failures
in CI where buffered output is lost when the test times out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants