> On Feb 8, 2021, at 5:00 PM, Jarek Potiuk <ja...@potiuk.com> wrote:
>
>> I'm not convinced this is true. I have yet to see any of my PRs for
> "non-big" projects getting queued while Spark, Airflow, others are. Thus
> why I think there are only a handful of projects that are getting upset
> about this but the rest of us are like "meh whatever."
>
> Do you have any data on that? Or is it just anecdotal evidence?
Totally anecdotal. Like when I literally ran a Yetus PR during the
builds meeting as you were complaining about Airflow having an X deep queue. My
PR ran fine, no pause.
> You can see some analysis and actually even charts here:
> https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status
Yes, and I don't even see Yetus showing up. I wonder how many other
projects are getting dropped from the dataset....
> Maybe you have a very tiny "PR traffic" and it is mostly in the time zone
> that is not affected?
True, it has very tiny PR traffic right now. (Sep/Oct/Nov was
different though) But if it was one big FIFO queue, our PR jobs would also get
queued. They aren't even when I go look at one of the other projects that does
have queued jobs.
When you see Airflow backed up, maybe you should try submitting a PR to
another project yourself to see what happens.
All I'm saying is: right now, that document feels like it is _greatly_
overstating the problem and now that you point it out, clearly dropping data.
It is problem, to be sure, but not all GitHub Actions projects are suffering.
(I wouldn't be surprised if smaller projects are actually fast tracked through
the build queue in order to avoid a tyranny of the majority/resource starvation
problem... which would be ironic given how much of an issue that is at the ASF.)
