The GitHub Actions job "Tests (AMD)" on airflow.git/git-bundle-shallow-fetch has failed. Run started by GitHub user piotrlinski (triggered by piotrlinski).
Head commit for run: 8a0b6f88dff39b109ee5458ce1163d818c0e01fc / piotrlinski <[email protected]> Add opt-in shallow fetch for pinned versions in the Git bundle A Git DAG bundle mirrors the whole repository — full history, every branch and tag — into a bare clone before checking out a version. That amortises well for a long-lived DAG processor or Celery worker that reuses the clone, but a KubernetesExecutor task pod is ephemeral: its bundle cache starts empty every time, so each task re-clones the entire repository just to check out the one commit it was pinned to. With many tasks and large repositories this is a large, repeated waste of network and disk. When running a pinned version, the worker already knows the exact commit SHA, so the bundle can fetch only that commit. A new opt-in ``shallow`` option makes the pinned-version path do ``git fetch --depth 1`` of the SHA straight into the version directory, skipping the bare mirror entirely. It requires the remote to allow fetching an unadvertised commit (which GitHub, GitLab and Bitbucket Cloud do); if the server refuses, the bundle transparently falls back to the existing full clone, so it is safe to enable anywhere. The unpinned branch-tracking path used by the DAG processor is unaffected. Report URL: https://github.com/apache/airflow/actions/runs/32040002141 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
