-
Notifications
You must be signed in to change notification settings - Fork 49
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
Plans for supporting t.Parallel #4
Comments
Thanks! So right now, A potential solution I've had in mind is to have a variant of Another idea uses a sort-of context-aware, gross, package global stack-marker, but I don't think that'll pan out the way I'd like. |
Thanks! :-) |
Can track support for this in #16 Not entirely sure of this solution yet though |
You guys might be interested in the recently implemented golang/go#22289. ("proposal: runtime: support tracking goroutine ancestor tracebacks"). Unfortunately I don't see a way of turning it on at runtime without spawning another process to set the environment variable to turn it on, hmm. |
Looking forward for this to be done. Can I help anyhow? Any update? (: |
I haven't worked on this in a long time @bwplotka, you're more than welcome to pick it up! What I did two years ago was start allowing this via just add a For the last year now, the codebase I work on at $dayjob uses ginkgo, which has a parallel test runner that segments tests into independent binaries during parallel execution, which makes leaktest work as normal (but we don't have a real use case for it). A solution based on what @pwaller noted last year would probably be the best way forward, feel free to give it a shot! You can message me on gophers slack (same username) if you want to chat about it |
Awesome, will let know here if I will find time to work on this (: Thanks for tips! 👍 |
Hello!
Thanks for this library, it'll definitely come in handy. Would you be able to document the reasons why t.Parallel isn't supported and what ideas you have for addressing the problem?
Thanks
The text was updated successfully, but these errors were encountered: