Onsi Fakhouri

yes that `go test` behavior is what i was telling you about - it doesn't support profiling with multiple packages. if you want you can start playing with v2 now....

The V2 beta was just released. [Here are some instructions for trying it out.](https://github.com/onsi/ginkgo/issues/809)!

hey @KevinJCross some thoughts on this. The use case makes sense to me. I can imagine a few ways of approaching this once 2.0 is out (I'd like to get...

hey @KevinJCross - ok sounds like the api design makes sense to you. I'm close to pushing out a commit to the `ver2` branch that formally bumps the major version...

hey @KevinJCross thanks for exploring options here. I've thought about it a bit more and I find my opinion shifting. Rather than build out a new instrumentation abstraction (and deal...

hey sorry for the delay. I was offline for 🦃 -day. Yes I'm suggesting Ginkgo creates its own proof file using its own instrumentation rather than sampling. `pprof` is "just"...

hey there @JiaYongfei - correct `CapturedStdOutErr` is only populated if the tests are run in parallel. in series Ginkgo does not intercept stdout/stderr and so it cannot populate the resulting...

hey there - Ginkgo is using `go test`'s support for code coverage. By default this only tracks coverage for the package under test (i.e. the package in which the test...

I'd recommend reading the golang blog post on how coverage works: https://go.dev/blog/cover basically only packages that are compiled into the test binary can be tracked for test coverage. If you...

hey @runkecheng `ginkgo -skip="case1"` should indeed work. `-skipPackage` will not work as it only refers to the package that is being compiled - not any imported dependencies. I do recommend...