Downgrading mlflow to avoid protobuf issues on nightly builds.#3784
Merged
Conversation
vfdev-5
reviewed
Jun 9, 2026
vfdev-5
reviewed
Jun 9, 2026
Co-authored-by: vfdev <vfdev.5@gmail.com>
Collaborator
Author
|
@vfdev-5 done |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Nightly CI/CD builds for pytorch/ignite were failing due to a protobuf compatibility issue introduced by a newer version of mlflow. This PR fixes the broken nightly test pipeline by downgrading mlflow to the last known working version, which resolves the protobuf conflict without requiring changes to the core library code.
Changes made:
Root cause:
A newer mlflow release pulled in a protobuf version that conflicted with the nightly build environment, causing CI failures unrelated to any code changes in ignite itself.
Error message: