potiuk opened a new issue #11294:
URL: https://github.com/apache/airflow/issues/11294


   **Description**
   
   Github Actions is great for us (much better than Travis used to be) but they 
change so fast that some of the features are not perfect and some of them are 
missing. This issue is an "umbrella issue" storing references to Github Suppor 
requests/ticket filed to GitHub Team and links to future changes planned by 
GitHub Actions that solve our pain points.
   
   
   - [ ]  Merge button becomes "green" when pending checks have not yet started
   This issue is filed by @potiuk  as ticket 
https://support.github.com/ticket/personal/0/857608. It's been acknowledged and 
files as a bug to GitHub Engineering
   
   - [ ]  No links between "workflow_run" and the originating workflow 
   The issue is filed by @potiuk as ticket 
'https://support.github.com/ticket/personal/0/859741. Waiting for feedback from 
GitHub suppport.
   
   - [ ] Jobs being often cancelled with 137 error. This seems to happen often 
. 
   The issue is filed by @potiuk as 
https://support.github.com/ticket/personal/0/857606 . GitHub support advised us 
to enable verbose debugging for the project. The JIRA issue is created 
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20945  to enable the 
debugging. IN progress.
   
   - [ ] No native cancelling of the workflows. @potiuk implemented custom 
"Cancel Workflow Runs" action that implements that feature 
https://github.com/marketplace/actions/cancel-workflow-runs and we are using 
it, but it has some limitations when the queue of jobs get really busy (the 
cancel step has to be executed in order to perform cancel but there might be 
not enough slotsl in the queue). @potiuk opened a ticket for that: 
https://support.github.com/ticket/personal/0/859753. Waiting for answer from 
GitHub support.
   
   


----------------------------------------------------------------
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.

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


Reply via email to