zozo123 commented on PR #74311: URL: https://github.com/apache/airflow/pull/74311#issuecomment-6401497271
I merged `main` and adapted the report to #74889. **Why:** scheduled canaries now run on RunsOn. There the CI image stash goes to RunsOn's S3 cache, and only its digest is a GitHub artifact: the latest canaries, e.g. 40200075185, only have `ci-image-save-v3-linux_amd64-<py>-s3-main`. So every report entry would have been skipped as "CI image missing". **What changed in 35938b59d3:** - The plan also accepts that digest artifact. - The explain job then runs on a RunsOn runner, with the same label template and the 8 CPU / 32 GB size as the `Deps` jobs. - It downloads exactly that tarball by its digest, verifies its sha256, and extracts it into `/mnt`, as `stash-restore` does. On public runners nothing changes. - Tests tie the digest suffix to `stash-save`, the S3 layout to its `sha256/<digest>.tar` objects, and the runner label to breeze's `RUNS_ON_AMD_RUNNER_TEMPLATE`. @shahar1, this touches the RunsOn path; could you take a look? The CI run for this commit is also waiting for a maintainer to approve it. -- 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]
