[v3-0-test] Fix generate-constraints run on different python than base (#52464) #52466
+3
−1
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.
It turns out that when we are installing Breeze we were using
the "Image" python version and not the 'default" python version
to install breeze, and Python 3.12 and 3.11 are not installed by
default when generate-constraints runs.
This change fixes this problem, also it changes the name of the
generate-constraints job to only show the python version used.
(cherry picked from commit 33afdf9)
Co-authored-by: Jarek Potiuk [email protected]