Another option would be to increase the resources dedicated to each agent
container and run less in parallel. Or, best yet, do both (up timeouts and
lower parallelization / up resources).
As far as I can tell the failures on Jenkins aren't value-add compared to what
we're seeing on circleci and are just generating busywork.
There's a reasonable discussion to be had about "what's the smallest footprint
of hardware we consider C* supported on" and targeting ASF CI to validate that.
I believe the noisy env + low resources on ASF CI currently are lower than
whatever floor we'd reasonably agree on.
On Tue, Jul 5, 2022, at 12:47 AM, Berenguer Blasi wrote:
> Hi All,
>
> bringing https://issues.apache.org/jira/browse/CASSANDRA-17729 to the ML
> for visibility as this has been a discussion point with some of you.
>
> I noticed tests timeout much more on jenkins that circle. I was
> wondering if legit bugs were hiding behind those timeouts and it might
> be the case. Feel free to jump in the ticket :-)
>
> Regards
>
>
