Onsi Fakhouri

hey, sorry I was never able to better engage with this. if it's still an open issue let me know. for now I'm going to close this as I try...

Ima gonna go ahead and close this but please feel free to reopen if need be

well... over two years later :( it looks like this race is happening while Gomega is trying to format the failure message. It's traversing the `err` returned by `ts.Token()` to...

I'm going to close this issue for now. If there's interest in submitting a PR let me know and we can reopen it.

As of ginkgo 2.5 you can run `ginkgo -v -show-node-events` to see exactly which node is running. I think that can help cases like this. am going to close this...

+1 - I can dig into how this is affecting parallel specs in Ginkgo but the details aren't super important or really "playwright's fault", it's a subtle issue around how...

hey, sorry for the delay here - looks like I won't be able to squeeze this in any time soon - so didn't want to leave folks hanging.

Yes!! Thanks so much @Dannyb48 - this will ship with the next release.

sorry for never getting back to this. yes you do need to send the signal to the process and its children yourself. I don't think I can forward it as...

hey @fiunchinho it sounds like your current structure is: ``` /suite-A |__ scenario_a_test.go /suite-B |__ scenario_b_test.go /suite-C |__ scenario_c_test.go ... ``` where each `scenario_*_test.go` file looks like: ```go var _...