Onsi Fakhouri

hey @lanwen good catch on `ginkgo unfocus` not catching `Focus`. I'll fix that ahead of the RC for v2. Ginkgo's current behavior is that it emits a non-zero exit code...

I'm closing this as I've implemented it on master and [this](https://github.com/onsi/ginkgo/pull/996/commits/7d02b23591498389b790fa21a4b6be7e94435b59) commit seemed unrelated to the issue at hand.

I was imagining you might want to get visibility into the test without it hanging, but could explore some of these options.

Actually - I've received an alternative solution suggestion that would be easier to implement and reason about. Instead, what if: `ginkgo -p -debug` (for example) caused each node to stream...

I think I lean towards a flag over an env-var as it is `ginkgo`'s primary interaction model. Can you share why environment variables might be preferred?

I've pushed a file-based approach to `parallel-debug-file`. Would love folks to take a look and send feedback. @williammartin might need your help vendoring a couple of dependencies that needed to...

thanks for taking a look @blgm I'd love to find an interface that works well. I think the file approach has merit and agree that ending up with lots of...

Good point @nodo We should update the docs here: https://onsi.github.io/ginkgo/#ginkgo-and-continuous-integration To recommend that folks add the debug flag in CI environments

go for it!

hey @MariusSchmidt - glad you're enjoying Ginkgo :) `ginkgo build` is simply using `go test -c` under the hood. Can you do me a favor and check wether or not...