chore(kv-store): disable browser tests on v4-next to unblock staging CI#22805
Merged
nchamo merged 1 commit intobackport-to-v4-next-stagingfrom Apr 27, 2026
Conversation
AztecBot
added
ci-draft
nchamo
approved these changes
Apr 27, 2026
nchamo
deleted the
claudebox/backport-22693-disable-kv-store-browser-tests
branch
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
3 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.
What
Cherry-picks the last commit of #22693 (
f0f0c6977b95114aeb2b7204414941adfff86efe, "disable kv-store browser tests to unblock CI") ontov4-next.Drops
&& yarn test:browserfrom the kv-storetestscript so CI runs node tests only.Why
The staging backport PR #22763 is failing
cion the kv-store browser-test step. The failure is the well-known sqlite-opfs hang originally fixed in #22693: the run consistently dies aftersqlite-opfs/multi_map.test.ts > AztecMultiMap > multiple keys are independent, withtimeout 600skillingbash10 minutes later.v4-nextdoes not yet have #22693, so the staging branch reproduces the hang.Per Martin's call in Slack, only this last commit (the simple
testscript change) is needed onv4-next— the other commits in #22693 (worker.ts pool-skip + vitest gate) aren't required just to unblock CI.Once this lands on
v4-next, re-running CI on #22763 should pass.ClaudeBox log: https://claudebox.work/s/c257cb057ea53390?run=3