mentioned in #1037 (comment)
Let’s see how this affects CI time
mentioned in #1037 (comment)
Let’s see how this affects CI time
Let’s see how this affects CI time
Less than I expected:
master: https://cirrus-ci.com/build/6730654054875136 this PR: https://cirrus-ci.com/build/4723750860488704
What do you think? Is this useful? If yes, should we just keep it as is or reduce the test iterations?
I think we can leave it as-is. I think only the duration of the longest-running CI job really matters, and that seems barely affected.
Indeed. Ready for review then.
-DVERIFY
for tests
if coverage is enabled, maybe just disable tests
(and leave noverify_tests
)?
Instead of disabling
-DVERIFY
fortests
if coverage is enabled, maybe just disabletests
(and leavenoverify_tests
)?
done