Rank, 14 days: 14 on the Bun sheet
3 people reported
All time, since Aug 10.
Failing matcher passes silently
“1.4.2: after ~40 s, expect(...).toBeNull() returns without throwing, so the assertion silently passes.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/6001/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Failing matcher passes silently when message exceeds max string length. In bun:test, matchers like toBeNull or toBe on huge values such as happy-dom Elements take ~40 s, then throw nothing.
Is this your bug?
File my report- Where
- bun:test
- Error text
Cannot create a string longer than 2147483647 characters- Versions
- 1.3.14 to 1.4.2
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports3, newest first
- bun:test: failing matcher on a value whose printed form exceeds the max string length passes silently (1.4.2) or takes ~40 s to fail (1.4.4); deep-equality matchers ignore
Bun.inspect.custom#47606 - bun:test reports a failing matcher as passing when its message exceeds the max string length#46005
- expect(<happy-dom Element>).toBeNull() takes ~40s+ on a large tree and then SILENTLY PASSES (throw is lost)#37310