github-actions[bot] opened a new pull request, #72256: URL: https://github.com/apache/airflow/pull/72256
* Monitor the workflow run breeze actually dispatched The docs-publish driver looked up the newest run of the workflow right after dispatching it. When the dispatch had not registered yet, that is the previous run - typically already finished - so the driver reported success and moved straight on to the airflow-site refresh and the S3-to-GitHub sync while the docs build it was supposed to gate on was still running. A scheduled run, or a run someone else started, was picked up the same way. Terminal conclusions other than success and failure were also treated as nothing to report, so a cancelled or timed-out run let the rest of the chain proceed as if the docs had been published. * Keep breeze workflow-run monitoring on the dispatched run only Several of the workflows breeze dispatches - apache/airflow-site's build.yml among them - also run on push and pull request. Such a run registering while we poll would be taken for the one we dispatched, so only workflow_dispatch runs are considered now. A transient gh failure during that poll also aborted the whole publishing chain, even though the caller is already retrying. (cherry picked from commit fbea214082de098fb79aabe0803fd97fce367ae2) Co-authored-by: Jarek Potiuk <[email protected]> -- 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]
