On Thu, Apr 03, 2025 at 05:57:51PM +0100, Richard Fitzgerald wrote:
On 3/4/25 14:26, Mark Brown wrote:
I've not heard anyone mention hitting the timeouts, though now I run interactively I do see that the Cirrus stuff is a good proportion of the runtime for --alltests. We could potentially add a config option, though it'd need to end up in the config file so it gets turned on and we'd still run into any timeout issues. There's a tension with people expecting --alltests to actually run all the tests as well...
I don't want to get into the situation where nobody outside of Cirrus is running the tests. One of the main points of converting our tests to kunit was the hope that more people would run them on more configurations.
Yes, me either - I do actually run them as part of my automated testing.