Avoid night torch CI not run because of irrelevant docker image failing to build #40677
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Currently, the workflow
calls
which builds 2 docker images in 2 jobs
However, after #40306,
only calls
model-ci
and no longer calldeepspeed-ci
, seehttps://github.com/huggingface/transformers/pull/40306/files#r2287368451
And we only need to build
latest-with-torch-nightly-docker
image formodel-ci
instead of the 2 docker image.Before this PR, we had
nightly-torch-deepspeed-docker
fails to buildhttps://github.com/huggingface/transformers/actions/runs/17431117913
and prevent the nightly torch CI to be run, which is not good.
This PR avoids this situation by adding
if
conditions in the 2 jobs inbuild-nightly-ci-docker-images.yml