🤖 ci: remove BUN_JSC_useWasmIPInt=0 workaround after Bun >= 1.3.10 upgrade
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, github-actions, typescript
- Domain
- build-system, ci-cd, testing
Research direction
Start with the Bun upgrade PR, then inspect the Test / Unit job environment in .github/workflows/pr.yml and the test-unit, test-unit-ci, and test-integration targets in the Makefile. Remove both BUN_JSC_useWasmIPInt=0 settings after Bun reaches 1.3.10 or later, then run the listed QuickJS suites with bun test --max-concurrency=1 --rerun-each=5 and confirm they stay green.
Written by the indexing model from the issue text.
Description
PR #4697 sets BUN_JSC_useWasmIPInt=0 for unit tests (.github/workflows/pr.yml Test / Unit job env and the Makefile test-unit, test-unit-ci and test-integration targets). It works around a Bun 1.3.5 JSC Wasm IPInt crash in the QuickJS suites (oven-sh/bun#17841, see #4406). The setting makes the QuickJS suites about 1.3–1.7x slower.
Follow-up: when the pinned Bun is upgraded to 1.3.10 or later (which has the WebKit fix, oven-sh/bun#26922), remove both settings and confirm the QuickJS suites stay green without them (for example bun test --max-concurrency=1 --rerun-each=5 over quickjsRuntime, code_execution, sandboxHostService and WorkflowRunner.evaluate tests).
- Owner: whoever upgrades the pinned Bun version.
- Trigger: the Bun upgrade PR.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 139
- Avg merge
- 6h 58m
- Merged PRs (30d)
- 774
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/xum
-
🤖 tests: localStorage budget worst-case test runs near the 5 s timeout and flakes in the merge queueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
backlog
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
backlog
Difficulty 5/5 Over a week Newbie friendliness 38/100
Maintainers usually reply within 1 day
Similar issues
-
needs:triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
ai-discovered
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jessepollak/home#1627 ·
Maintainers usually reply within 1 day
-
agent-canvas bug llm priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenHands/OpenHands#17806 · 3 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
radius-project/ai-extensions#923 ·
Maintainers usually reply within 1 day