ci(supabase_flutter): make WASM tests non-blocking

[grdsdev]

Summary

• Make WASM tests non-blocking with continue-on-error: true
• WASM tests have known infrastructure flakiness (12+ minute loading timeouts)
• CI will continue while still running tests for visibility

Context

The flutter test --platform chrome --wasm step has been timing out during the test loading phase (not execution), causing unrelated PRs to fail CI. This is an infrastructure issue with Flutter's WASM testing, not a code issue.

Test plan

• Verify workflow syntax is valid
• CI runs should now pass even if WASM tests timeout

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Enhanced CI/CD pipeline resilience for web platform testing to accommodate infrastructure variations while maintaining visibility into test results.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified the GitHub Actions workflow to add error handling for the WASM web build and test step. The step now continues on failure with added comments documenting known infrastructure flakiness, while still reporting test results for visibility.

Changes

Cohort / File(s)	Summary
CI/CD Configuration .github/workflows/supabase_flutter.yml	Added continue-on-error: true to the "Build and test web (WASM)" step with inline comments explaining infrastructure flakiness and allowing workflow continuation while preserving test visibility

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately describes the main change: making WASM tests non-blocking in the CI workflow by adding continue-on-error: true.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/supabase_flutter.yml (1)

90-97: Avoid masking WASM build failures.

continue-on-error: true applies to the entire step, so a broken flutter build web --wasm will also pass CI. If you only want flaky tests to be non-blocking, split the test and build into separate steps and keep the build blocking.

✅ Suggested split to keep build blocking

-      - name: Build and test web (WASM)
-        # WASM tests have known infrastructure flakiness (12min+ loading timeouts)
-        # Allow CI to continue while still running tests for visibility
-        continue-on-error: true
-        if: ${{ matrix.os == 'ubuntu-latest' && matrix.flutter-version == '3.x'}}
-        run: |
-          flutter test --platform chrome --wasm
-          cd example && flutter build web --wasm
+      - name: Test web (WASM) - non-blocking
+        # WASM tests have known infrastructure flakiness (12min+ loading timeouts)
+        # Allow CI to continue while still running tests for visibility
+        continue-on-error: true
+        if: ${{ matrix.os == 'ubuntu-latest' && matrix.flutter-version == '3.x'}}
+        run: flutter test --platform chrome --wasm
+
+      - name: Build web (WASM)
+        if: ${{ matrix.os == 'ubuntu-latest' && matrix.flutter-version == '3.x'}}
+        run: cd example && flutter build web --wasm