Marton, This is super helpful, and thanks for linking the data. On Sun, Apr 18, 2021, 2:06 AM Elek, Marton <e...@apache.org> wrote:
> > There are 13 project which uses Github Actions above this possible limit: > > > project build hours average hours per job max hours per job > nuttx 14138.818889 3.441777 17.845833 > pulsar 10785.601944 0.478743 2.011667 > airflow 8305.211111 1.247216 20.768056 > skywalking 6852.736667 0.959095 7.520278 > arrow 6290.633889 0.503573 24.359444 > ozone 5484.444722 4.440846 17.473333 > camel 4241.184722 0.754525 18.681389 > iotdb 4007.576667 1.224061 36.676944 > shardingsphere 2858.329444 0.503937 21.633056 > beam 2782.366111 0.688364 46.451667 > nifi 2380.907500 4.641145 11.313056 > apisix 2342.009722 0.209183 24.139167 > dubbo 1815.491389 1.537249 11.023889 > The Apache NuttX project has implemented some aggressive cancellation of workflows in the last few weeks so I would expect our numbers to go way down. We also are looking and a larger overhaul of our build system but that is a further out effort. The run times still seem a little high compared to what I usually see, so I will look at what is causing that. It's possible something is hanging occasionally. This is where that repo is super nice! We have some bigger plans in the works including adding physical hardware racks to our testing (this is an embedded RTOS project) which will require us to run our own runners. As part of that we have also been considering adding our own larger runners to the mix that we would pay for, but how is still a very open question with the security issues that have been mentioned before. Thanks, Brennan
