Onsi Fakhouri

ok - so you want the system-err to basically act as a temporal log of the spec? let me see what I can do. I already support his for ProgressReports...

Are you hoping to see the entire failure in the GinkgoWriter log? I could imagine a lot of users getting frustrated at the duplication of seeing the failure in the...

I'm going to give the topic some thought today. There are a number of "events" and "streams" that happen over the lifecycle of a spec: - data is written to...

hey @kerthcet it's not out yet - sorry, I've been updating the CHANGELOG as I go but the release should come out in the next couple of days.

Alrighty - one last Gomega change that's related to all this Timeout and Interrupt work. You can now return a `StopTrying("message")` error or simply call `StopTrying("message").Now()` to signal to Gomega...

Lol - sorry i thought i'd pushed to github before i left the coffee shop ;) i'll push it out when i'm back at my computer!

Alright - it's up now. Sorry about that!

Ginkgo 2.3.0 is out now with support for interruptible nodes, as is Gomega 1.22.0 with support for taking a context!

I wanted to call out one more thing to get thoughts/input/feedback before closing this issue and calling this feature done. Currently the `context` provider by Ginkgo is not configured as...

hey @eriknyk - since Ginkgo supports spec [parallelization](https://onsi.github.io/ginkgo/#spec-parallelization) and [randomization](https://onsi.github.io/ginkgo/#spec-randomization) there are no guarantees that specs will run in context-order. Moreover, Ginkgo assumes [specs are independant](https://onsi.github.io/ginkgo/#mental-model-ginkgo-assumes-specs-are-independent). So, while I do...