spark-master-test-maven-hadoop-3.2 looks like it's been timing out for
~2 weeks, but the others only for a few days.
all of these builds have a 335 minute (5 hours, 35 mins) timeout configured.
honestly, i feel that 5.5 hours is already an insane amount of time
for these builds to run... do we need to increase it? can
someone(s) here figure out what's taking so long and refactor some of
Re: [build system] maven master branch builds timing out en masse...
Moving the conversation here -- yes, why on earth are they taking this
long all of the sudden? we'll have to look again when they come back
online. The last successful build took 6 hours, of which 4:45 were
the unit tests themselves.
Well, at least it seems like we legitimately need these full
integration tests to run that long, and that's just life right now, so
8 hours is better than failing. But yeah, seems like we just test a
whole lot more recently and it's taking a long time. Kudos to recent
efforts to parallelize some of that.