George Blue

Hi @magicmoose. That's curious. In order to have something concrete to talk about, I've created this repo: https://github.com/blgm/foo It has "v1" code at the top level and "v2" in a...

Got it! I can reproduce the issue you describe: ``` $ ginkgo ./... [1619723369] Actor Suite - 1/1 specs v1 • SUCCESS! 268.133µs PASS Failed to compile actor: main module...

The advantage of using `go list` is we delegate complexity and maintain *exactly* the same behaviour as `go test`. I wonder how noticeable the effect is of staring another process?

A bit more on the 'files on disk' suggestion: - Initially it could be controlled by an environment variable, e.g. `GINKGO_DEBUG_DIR` - it would be good to specify the directory...

@onsi, I don’t have a strong view on whether it’s a flag or an environment variable. I would lean towards an environment variable if it’s a “pre-release” feature that I...

@onsi, after what must seem like a geological age, here are some very quick thoughts on the `parallel-debug-file` branch: - If you run ginko recursively, then you get a lot...

Perhaps creating them all in the same directory with a name scheme like `ginkgo-node-U-N.log` where `U` is some kind of ID? But it would make it harder to correlate files...

I've merged the file solution via #499. I'll leave this open to remind us to update the docs.

I've used `go:embed` with files (not directories) in Ginkgo and it worked fine. Do you have any more detail on the issues that you're seeing? Can you make it work...

I guess you could do something like: ```go var bailOut bool BeforeEach(func() { if bailOut { Skip("bailing out") } }) AfterEach(func() { if badThingHappened() { bailOut = true } })...