Logged https://issues.apache.org/jira/browse/CALCITE-7751 for the issue.
I have an idea of how we can avoid this in the future by splitting the jobs requiring labels in a separate file. Feel free to take a loot on the proposed PR. Best, Stamatis On Wed, Aug 26, 2026 at 7:15 PM Mihai Budiu <[email protected]> wrote: > > I think the sequence was: > > - actions were not run for a first-time contributor > - I approved the PR > - I set the label LGTM > - I enabled the actions to run > - only a couple of actions were run > > So the bug was that some actions were NEVER run. > > Mihai > > ________________________________ > From: Stamatis Zampetakis <[email protected]> > Sent: Wednesday, August 26, 2026 6:02 AM > To: [email protected] <[email protected]> > Subject: Re: Skipped CI jobs > > I am under the impression that CI works as expected but if you think there > is a bug then we should log a JIRA ticket and follow-up. > > CI actions are triggered on the following events [1]: [opened, synchronize, > reopened, labeled] > Every time someone adds/removes a label (e.g., "LGTM will merge soon") all > actions are triggered. However, we don't want to run all actions every time > someones changes a label so the majority of actions are skipped based on > the following conditional: > if: github.event.action != 'labeled' > > In fact, the only action that should run when the labels change is the one > for the slow tests [2] and only if the actual label is "slow-tests-needed". > > All in all, when you add "LGTM will merge soon" label no action should run. > The actions run normally for every other event (i.e., opened, synchronize, > reopened) so there is no reason to run it again just because a label > changed. > > Best, > Stamatis > > [1] > > https://github.com/apache/calcite/blob/f511791d1b49437635a960f07032f7c2f9a137f7/.github/workflows/main.yml#L31 > [2] > > https://github.com/apache/calcite/blob/f511791d1b49437635a960f07032f7c2f9a137f7/.github/workflows/main.yml#L403 > > > On Wed, Aug 26, 2026 at 2:10 PM Yu Xu <[email protected]> wrote: > > > That’s certainly true; once the "LGTM will merge soon" label is applied, > > the number of tests run usually drops significantly. So, after applying > the > > label but before merging, I typically perform a rebase—at the very least, > > that triggers the full suite of tests. > > > > On 2026/08/25 16:48:32 Mihai Budiu wrote: > > > I wonder why CI skips so many jobs. Some of them seem unjustified: > > > https://github.com/apache/calcite/pull/5219 > > > > > > > > > > > >
