Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
test/e2e: fix custom timing reporting
This never worked when ginkgo runs with more than one thread, we use 3 in CI. The problem is that the SynchronizedAfterSuite() function accepts two functions. The first one is run for each ginkgo node while the second one is only run once for the whole suite. Because the timings are stored as slice thus in memory we loose all timings from the other nodes as they were only reported on node 1. Moving the printing in the first function solves this but causes the problem that the result is now no longer sorted. To fix this we let each node write the result to a tmp file and only then let the final after suite function collect the timings from all these files, then sort them and print the output like we did before. Signed-off-by: Paul Holzinger <[email protected]>
- Loading branch information