voonhous opened a new issue, #19895:
URL: https://github.com/apache/hudi/issues/19895

   Part of #19524.
   
   `hudi_trino_ci.yml` still uses a `changes` job that every other job `needs`. 
On the shared ASF runner pool that is a second trip through the queue for every 
run, which #19890 measured at 1 to 3 minutes when the pool is quiet and 20 to 
270 minutes when it is busy. #19890 removed the same pattern from bot.yml by 
moving the skip to a trigger-level `paths` filter.
   
   The comment above the Trino workflow's trigger also now contradicts bot.yml: 
it says a path-filtered workflow leaves an expected run "permanently pending". 
That is only true for required status checks, and `test-hudi-trino-plugin` is 
no longer required (the contexts list was reset in #19523).
   
   Proposed change: move the Trino path list to a trigger-level `paths` filter, 
drop the `changes` job and its `needs`, and soften the comment to say pending 
applies only to required contexts.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to