[ROCm][CI] Update concurrency setting for docker-cache-rocm.yml#168104
[ROCm][CI] Update concurrency setting for docker-cache-rocm.yml#168104jithunnair-amd wants to merge 1 commit intomainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/168104
Note: Links to docs will display an error until the docs builds have been completed. ❌ 18 New Failures, 2 Cancelled Jobs, 12 Unrelated FailuresAs of commit 47a4e0d with merge base ebb2001 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOBS - The following jobs were cancelled. Please retry:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot merge -f "Lint failures are due to GitHub outage" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
We only want to cache the latest CI docker image for
mainandreleasebranches in cases where multipledocker-buildsworkflow runs get triggered in quick succession. This is because the latest run will anyway overwrite the cached images, since we do not maintain a cached image per-SHA, instead it's only one-per-branch (to minimize cache size and docker load times at runner bringup).Also removing
workflow_dispatchas a trigger since it won't work (needs artifacts fromdocker-buildsrun)cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd