-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Canary] Deno test panicking #22148
Comments
Thanks for catching this. I did a bisect and found that the problematic PR is #22125. We'll need to work on a reproduction for this crash, so we'll probably revert the PR in the meantime. |
bartlomieju
added
bug
Something isn't working correctly
testing
related to deno test and coverage
labels
Jan 27, 2024
I confirmed that reverting that PR fixes the problem. |
The full backtrace:
Panic is raised just before the process exits. |
This is now fixed with #22153 landed. |
This was referenced Jan 29, 2024
mmastrac
added a commit
that referenced
this issue
Feb 5, 2024
Originally in #22125 Reverted in #22153 because of #22148 Fixed in deno_core denoland/deno_core#538 Test plan: 1. Check out: https://github.com/poolifier/poolifier-deno.git 2. `PATH=.../deno/target/release/:$PATH deno task test` 3. `ok | 13 passed (188 steps) | 0 failed (18s)`
littledivy
pushed a commit
that referenced
this issue
Feb 8, 2024
Originally in #22125 Reverted in #22153 because of #22148 Fixed in deno_core denoland/deno_core#538 Test plan: 1. Check out: https://github.com/poolifier/poolifier-deno.git 2. `PATH=.../deno/target/release/:$PATH deno task test` 3. `ok | 13 passed (188 steps) | 0 failed (18s)`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extracted from https://github.com/poolifier/poolifier-deno/actions/runs/7678076145/job/20927551728
I will extract the backtrace when time permits, but in the meantime running
deno task test
after cloning the poolifier-deno repo reliability reproduce the panic.The text was updated successfully, but these errors were encountered: