Onsi Fakhouri

This is now resolved in V2. Ginkgo now manages its own timeout and triggers a test-wide interrupt that gracefully unwinds any running tests and calls reporters appropriately. V2 is in...

that's great to hear, thanks!

iirc i turned this off intentionally. your usecase makes sense to me though so let me dig into why i'd done that and circle back.

Makes sense - but I think I agree that the intent behind `--dry-run` is to report on how the suite will run which should include running the reporting nodes. Will...

it'll be in the next release - not sure yet when I'll cut a release, though. hopefully in the next few days/week.

hey @anshuljayn thanks for using the 2.0 beta/rc! As it's a new feature, I'd love to learn more in general about how you're using report entries. I can add these...

hey @anshuljayn thanks for sharing how you're using the new feature. When you say you want the flexibility to avoid including CodeLocation and Time do you mean in the JUnit...

hey sorry for the delay on my end. thanks for the additional detail. imo the junit and json report formats should have as much information as possible and formatting/visibility should...

hey there - i'd love to add support for this someday but it's currently unsupported. two main motivations behind the current behavior were: - giving users clean non-interleaved and immediate...

makes sense. i'd love to be able to get to this someday soon!