Skip to content

Conversation

@mverzilli
Copy link
Contributor

No description provided.

@mverzilli mverzilli added the ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure label Jan 2, 2026
@AztecBot
Copy link
Collaborator

AztecBot commented Jan 2, 2026

Flakey Tests

🤖 says: This CI run detected 2 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (\0338;;http://ci.aztec-labs.com/733b066874bb22a3�733b066874bb22a38;;�\033): BOX=react BROWSER=chromium run_compose_test react-chromium box boxes (144s) (code: 1) (\033mverzilli\033: fix for IndexedDB serialization)
\033FLAKED\033 (\0338;;http://ci.aztec-labs.com/4ce941ee321b8970�4ce941ee321b89708;;�\033): BOX=vite BROWSER=chromium run_compose_test vite-chromium box boxes (425s) (code: 1) (\033mverzilli\033: fix for IndexedDB serialization)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants