runtests: report single test time + total duration #4027
Conversation
... after each successful test.
|
Interesting results. Should valgrind be running on most variants? It would appear to add ~10 minutes to the test time. |
|
The problem with Valgrind is: Valgrind + OpenSSL + Xenial makes Valgrind crash because of an assertion failure. |
|
@MarcelRaad I actually meant the negative; should valgrind be disabled on all but a "maximal" build, so that CI finishes more quickly in general? |
|
The challange is with all the various build combinations and making sure they all have at least one build that runs with valgrind enabled. Ie there cannot be just one "maximal" build since there are so many alternative options and mutually exclusive ones. But yes, switching off valgrind for the builds that make sense will certainly make them run faster! |
|
I like the new timing information output like this! I'll let the PR sit here a while to collect input from others if someone has objections, but if nobody does I'll merge it later. |
|
On Fri, Jun 14, 2019 at 05:08:54AM -0700, Daniel Stenberg wrote:
The challange is with all the various build combinations and making sure they
all have at least one build that runs with valgrind enabled.
ASAN, MSAN and UBSAN catch a lot of the same things that Valgrind do with much
less overhead. Enabling those in more builds might be a workable alternative.
|
... after each successful test.