Make it possible to flush output via newline in between tests #1347
Comments
|
This is the gist of it. Note that we haven't actually verified that a newline will help, but it seems likely. While you are at it, a mode where not even the |
|
Or make it so that just the |
|
sigh - it only took 3 months but |
|
2.18.0 is out and includes this |
|
woops - didn't mean to close it! |
The most interesting aspect of the new Ginkgo is tweaking the output so that it's easier to follow while a job runs in Prow (onsi/ginkgo#1347). Using this in hack/ginkgo-e2e.sh will follow in a separate commit. Gomega gets bumped to the latest release to keep it up-to-date.
|
This works as expected and does indeed help with watching progress in Prow. Thanks! I think this can be closed. |
The most interesting aspect of the new Ginkgo is tweaking the output so that it's easier to follow while a job runs in Prow (onsi/ginkgo#1347). Using this in hack/ginkgo-e2e.sh will follow in a separate commit. Gomega gets bumped to the latest release to keep it up-to-date.
The most interesting aspect of the new Ginkgo is tweaking the output so that it's easier to follow while a job runs in Prow (onsi/ginkgo#1347). Using this in hack/ginkgo-e2e.sh will follow in a separate commit. Gomega gets bumped to the latest release to keep it up-to-date. The latest pprof added an indirect dependency on github.com/mailru/easyjson when adding a complex integration test. This does not affect Kubernetes and thus can be ignored.
|
wonderful, glad to hear it! |
Some CI systems only flush output when a newline is observed. This makes it hard to see Ginkgo's progress when running without
-v. A new mode that forces Ginkgo to emit a newline between each spec report (even if that report is just "o") would resolve this./cc @pohly
The text was updated successfully, but these errors were encountered: