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

[TRACING] Add test which would catch the linked panic #131

Open
sarsko opened this issue Dec 11, 2023 · 0 comments
Open

[TRACING] Add test which would catch the linked panic #131

sarsko opened this issue Dec 11, 2023 · 0 comments

Comments

@sarsko
Copy link
Contributor

sarsko commented Dec 11, 2023

See #128 (comment).

Resolving this issue would involve creating a test which panics when run under #9a29bca, but does not panic when run under #c4c6517.

The issue seems to have been:

  1. Task X enters Span A. Context-switch to Task Y.
  2. Task Y enters Span A. Task Y leaves Span A, which closes it. Context switch to Task X.
  3. Task X tries to enter Span A, which does not exist anymore.

May be more details needed, have not looked into this issue much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant