ci: run unit test suites as parallel jobs and fix pub caching

.github/actions/flutter_base/action.yaml

@@ -18,9 +18,69 @@ runs:
       uses: subosito/flutter-action@v2
       with:
         cache: true
+        # `cache: true` with no explicit `pub-cache` input ALSO silently
+        # enables flutter-action's OWN internal pub-cache step (its
+        # action.yaml: `if: (inputs.pub-cache == '' && inputs.cache ==
+        # 'true') || ...`), whose key unconditionally appends
+        # `${{ hashFiles('**/pubspec.lock') }}` -- an UNSCOPED glob from the
+        # repo root, not the narrower `packages/**/pubspec.yaml` below.
+        # Confirmed live: a run on this exact composite action (reached by
+        # every tests.yaml job via integration_test_base -> flutter_base)
+        # hit "hashFiles('**/pubspec.lock') couldn't finish within 120
+        # seconds" on a macOS leg, and the GH Actions cache listing
+        # (`gh api repos/Bdaya-Dev/oidc/actions/caches`) shows a
+        # `flutter-linux-...-<hash>-` key with an EMPTY trailing segment --
+        # the same hashFiles call degrading to "" on Linux too, just not
+        # fatally there. Explicitly disabling it here (we run our own
+        # narrowly-scoped pub cache below instead) removes that failure
+        # mode for every job that goes through this action, including
+        # ios/macos/android/web/linux/windows via integration_test_base --
+        # without changing anything those jobs own.
+        pub-cache: "false"
         channel: ${{ inputs.channel }}
         flutter-version: ${{ inputs.flutter-version }}
 
+    # Replaces the internal pub-cache step disabled above. subosito/
+    # flutter-action's own `cache: true` only caches the downloaded
+    # Flutter/Dart SDK (keyed by version), not the hosted-package pub cache
+    # that `melos bootstrap` below populates via `pub get` across every
+    # workspace package, nor the pub-global packages activated later by
+    # the coverage-formatting steps (coverage/combine_coverage/
+    # remove_from_coverage). Missing previously (every job paid a cold
+    # `pub get` + cold global-package resolve/compile on every run). Now
+    # that unit_tests is split into many parallel jobs (see tests.yaml),
+    # this matters more, not less: every one of those jobs runs its own
+    # `melos bootstrap` independently, so a warm cache is shared across all
+    # of them (and across sdk channels via the key).
+    # Keyed on the channel (stable/beta resolve different dependency sets)
+    # and a hash of every pubspec, scoped under packages/ (cheap: at this
+    # point in the job nothing has generated android/Pods/build dirs yet,
+    # so the glob only walks source files) instead of an unscoped `**` from
+    # the repo root -- a dependency change invalidates it; restore-keys
+    # fall back to the most recent cache for the same channel so a partial
+    # hit still saves most of the network/compile cost. Concurrent jobs
+    # racing to save the same key is harmless: actions/cache only lets the
+    # first writer persist it, and the pub cache's own content is derived
+    # purely from pubspec.yaml/pubspec.lock, so two independent
+    # populations of the same key are equivalent.
+    - name: Cache pub dependencies
+      uses: actions/cache@v6
+      with:
+        # Two paths, not one: this action also runs on windows-latest (the
+        # `windows` job, via integration_test_base) where the global pub
+        # cache lives under %LOCALAPPDATA%\Pub\Cache
+        # (~/AppData/Local/Pub/Cache under this workflow's bash shell), not
+        # ~/.pub-cache -- see the windows job's own PATH export in
+        # tests.yaml, which adds both for the same reason. A path that
+        # doesn't exist on a given OS is simply skipped by actions/cache,
+        # so listing both is harmless on Linux/macOS.
+        path: |
+          ~/.pub-cache
+          ~/AppData/Local/Pub/Cache
+        key: pub-${{ runner.os }}-${{ inputs.channel }}-${{ hashFiles('pubspec.yaml', 'pubspec.lock', 'packages/**/pubspec.yaml') }}
+        restore-keys: |
+          pub-${{ runner.os }}-${{ inputs.channel }}-
+
     # see https://github.com/invertase/melos/issues/796
     - uses: bluefireteam/melos-action@main
       continue-on-error: true

.github/workflows/dart_package.yaml

@@ -79,7 +79,21 @@ jobs:
           flutter-version: ${{inputs.flutter_version}}
           channel: ${{inputs.flutter_channel}}
           cache: true
-          cache-key: flutter-:os:-:channel:-:version:-:arch:-:hash:-${{ hashFiles('**/pubspec.lock') }}
+          # Dropped the trailing `-${{ hashFiles('**/pubspec.lock') }}`: the
+          # SDK binary's cache content never varies with this repo's
+          # lockfile, so tying its key to it only added needless
+          # invalidation on every dependency bump, PLUS an unscoped
+          # repo-root `**` glob that has been observed to fail outright
+          # ("hashFiles('**/pubspec.lock') couldn't finish within 120
+          # seconds") on a macOS runner elsewhere in this repo's CI. Also
+          # disables flutter-action's own internal pub-cache step (default
+          # ON whenever `cache: true` and `pub-cache` is unset), which
+          # independently appends that same unscoped hashFiles call to ITS
+          # key -- this reusable workflow isn't currently invoked by
+          # anything in this repo, so there's no replacement pub-cache
+          # step here, just removal of the failure mode.
+          pub-cache: "false"
+          cache-key: "flutter-:os:-:channel:-:version:-:arch:-:hash:"
 
       - uses: bluefireteam/melos-action@v3
 

.github/workflows/deploy_firebase.yaml

@@ -55,7 +55,18 @@ jobs:
         with:
           channel: stable
           cache: true
-          cache-key: flutter-:os:-:channel:-:arch:-:hash:-${{ hashFiles('**/pubspec.lock') }}
+          # See .github/actions/flutter_base's comment for the full story:
+          # the SDK cache doesn't need to vary with the lockfile, and the
+          # unscoped `hashFiles('**/pubspec.lock')` glob this key used to
+          # require has been observed to fail ("couldn't finish within 120
+          # seconds") on a macOS runner elsewhere in this repo's CI; the
+          # dead `flutter-linux-stable-x64-<hash>-` cache entries (trailing
+          # dash, empty hash segment) in this repo's cache list are that
+          # same failure degrading silently on Linux. pub-cache: "false"
+          # disables flutter-action's own internal pub-cache step, which
+          # independently used the same unscoped hashFiles call.
+          pub-cache: "false"
+          cache-key: "flutter-:os:-:channel:-:arch:-:hash:"
 
       - name: Build Example (Flutter web + wasm)
         shell: bash

.github/workflows/firebase_preview.yaml

@@ -49,7 +49,14 @@ jobs:
         with:
           channel: stable
           cache: true
-          cache-key: flutter-:os:-:channel:-:arch:-:hash:-${{ hashFiles('**/pubspec.lock') }}
+          # See deploy_firebase.yaml's identical fix / .github/actions/
+          # flutter_base's comment for the full story: unscoped
+          # `hashFiles('**/pubspec.lock')` observed failing on a macOS
+          # runner elsewhere in this repo's CI, and the dead
+          # `flutter-linux-stable-x64-<hash>-` cache entries are that same
+          # failure degrading silently on Linux.
+          pub-cache: "false"
+          cache-key: "flutter-:os:-:channel:-:arch:-:hash:"
 
       - name: Setup Python
         if: steps.filter.outputs.docs == 'true'

.github/workflows/flutter_package.yaml

@@ -75,7 +75,15 @@ jobs:
           flutter-version: ${{inputs.flutter_version}}
           channel: ${{inputs.flutter_channel}}
           cache: true
-          cache-key: flutter-:os:-:channel:-:version:-:arch:-:hash:-${{ hashFiles('**/pubspec.lock') }}
+          # See dart_package.yaml's identical fix: the SDK cache doesn't
+          # need to vary with the lockfile, and the unscoped
+          # `hashFiles('**/pubspec.lock')` glob it required has been
+          # observed to fail ("couldn't finish within 120 seconds") on a
+          # macOS runner elsewhere in this repo's CI. pub-cache: "false"
+          # disables flutter-action's own internal pub-cache step, which
+          # independently used the same unscoped hashFiles call.
+          pub-cache: "false"
+          cache-key: "flutter-:os:-:channel:-:version:-:arch:-:hash:"
       - name: 📦 Install Dependencies
         run: |
           flutter pub global activate very_good_cli          

.github/workflows/pana.yaml

@@ -37,6 +37,13 @@ jobs:
         with:
           channel: stable
           cache: true
+          # See .github/actions/flutter_base's comment: `cache: true` alone
+          # also enables flutter-action's internal pub-cache step, whose
+          # key unconditionally appends an unscoped
+          # `hashFiles('**/pubspec.lock')` that has been observed to fail
+          # ("couldn't finish within 120 seconds") on a macOS runner
+          # elsewhere in this repo's CI.
+          pub-cache: "false"
       # see https://github.com/invertase/melos/issues/796
       - uses: bluefireteam/melos-action@main
         continue-on-error: true