Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bun test exits with code 0 when the entrypoint fails to resolve (ModuleNotFound) #15208

Open
NReilingh opened this issue Nov 18, 2024 · 1 comment · May be fixed by #15300 or #15212
Open

bun test exits with code 0 when the entrypoint fails to resolve (ModuleNotFound) #15208

NReilingh opened this issue Nov 18, 2024 · 1 comment · May be fixed by #15300 or #15212
Labels
bug Something isn't working confirmed bug We can reproduce this issue

Comments

@NReilingh
Copy link
Contributor

What version of Bun is running?

1.1.34+5e5e7c60f

What platform is your computer?

Darwin 24.1.0 arm64 arm

What steps can reproduce the bug?

  1. bun test ./doesNotExist.ts
  2. echo $?

What is the expected behavior?

Exit code should be a value other than 0.

What do you see instead?

Exit code is 0.

Additional information

This is kind of a meta-test failure, but should still be considered an error state -- otherwise, CI tools that are expecting an exit 0 when tests pass may pass code that hasn't been tested (but that the programmer is expecting to have been tested).

@NReilingh NReilingh added bug Something isn't working needs triage labels Nov 18, 2024
@Jarred-Sumner
Copy link
Collaborator

Yes definitely a bug.

@Jarred-Sumner Jarred-Sumner added confirmed bug We can reproduce this issue and removed needs triage labels Nov 18, 2024
@Jarred-Sumner Jarred-Sumner linked a pull request Nov 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed bug We can reproduce this issue
Projects
None yet
2 participants