Thanks all.
Just to add a bit of note,
> * Create a wiki page collecting all the practices to reduce the hours
> (using the pr cancel workflow discussed earlier + timeouts + ...?)
We should probably also mention that Apache Spark managed to distribute the
workflow runs to forked repositories in
I really love what Hyukjin has done. I did not have the capacity to
participate in this actively, but this is exactly the way to go, I think
(with a caveat). Following the motorway metaphor - everyone (every
contributor/committer, not every project) has their own lane and they do
not interfere with
Also some comments for the stats. This is good stuff Marton.
> Apparently, what's named "jobhours" in your statistics is actually the
> runtime for an entire workflow (the sum of all job runtimes for that
> workflow). That's at least what I conclude if I look at this workflow,
> which your table
On 4/19/21 1:07 PM, Jarek Potiuk wrote:
Also some comments for the stats. This is good stuff Marton.
Apparently, what's named "jobhours" in your statistics is actually the
runtime for an entire workflow (the sum of all job runtimes for that
workflow). That's at least what I conclude if I l
