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 does not respect repeats or retry properties in test options #16051

Open
goldenstein64 opened this issue Dec 30, 2024 · 0 comments · May be fixed by #16060
Open

bun test does not respect repeats or retry properties in test options #16051

goldenstein64 opened this issue Dec 30, 2024 · 0 comments · May be fixed by #16060
Labels
bug Something isn't working needs triage

Comments

@goldenstein64
Copy link

What version of Bun is running?

1.1.42+50eec0025

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What steps can reproduce the bug?

Run these tests. Do not expect it to complete in a reasonable amount of time.

import { it, expect } from "bun:test";

it("fails", () => {
  expect.unreachable();
}, { retry: 1e9 });

it("passes", () => {}, { repeats: 1e9 });

What is the expected behavior?

Both tests should hang because they have a massive amount of retries or repeats.

What do you see instead?

Both tests complete immediately.

Additional information

I'm not sure what the output should be in these cases, which is why the repro is about making the tests hang instead of observing the output.

@goldenstein64 goldenstein64 added bug Something isn't working needs triage labels Dec 30, 2024
@goldenstein64 goldenstein64 changed the title bun test does not respect repeats or retry property in test options bun test does not respect repeats or retry properties in test options Dec 30, 2024
@Devanand-Sharma Devanand-Sharma linked a pull request Dec 30, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant