Bun test code coverage - Not returning exit code 1 when under threshold

Description

[test]
coverage = true
coverageThreshold = { line = 0.9, function = 0.9 }

$ bun test 

....
--------------------------------------------------------|---------|---------|-------------------
File                                                    | % Funcs | % Lines | Uncovered Line #s
--------------------------------------------------------|---------|---------|-------------------
All files                                               |   55.20 |   69.58 |
...
--------------------------------------------------------|---------|---------|-------------------

 138 pass
 0 fail
 486 expect() calls

$ echo $?
0

Contributor guide

Tech stack

javascripttypescriptrust

Domain

testing

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Familiarity with bun testBasic understanding of Rust or JavaScript

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

65

Research direction

Investigate the test runner's coverage logic, likely in the source code under `src/` directory. Look for where the coverage threshold from bunfig.toml is parsed and how the exit code is set after running tests. The bug indicates that when coverage is below threshold, exit code should be 1 but is 0. Track down the condition that checks thresholds and ensure it properly sets the exit code. Check for any recent changes or comments in related issues.