You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was identified due to the build beginning to crash on 3/11. These test failures were not caused by any code merge, but instead a release of cibuildwheel.
We can tell that the version of cibuildwheel changed by comparing last known succeeding vs failed builds.
However. That's just addressing the problem. The real question is why this occurred.
In this experiment build, we forced a pip freeze from the same python executable invoking cibuildwheel, and the freeze version is reporting 2.16.5, but the running version is reporting 2.17.0.
THIS is the source of the mystery. Why are we getting cibuildwheel==2.17.0 when everything we're seeing during install is 2.16.6?
This was identified due to the build beginning to crash on 3/11. These test failures were not caused by any code merge, but instead a release of
cibuildwheel
.We can tell that the version of
cibuildwheel
changed by comparing last known succeeding vs failed builds.Before
After
The cause of the error is that
cibuildwheel
no longer assumes thatwheel
is NECESSARY to build your package. We can simply address it by adding:However. That's just addressing the problem. The real question is why this occurred.
In this experiment build, we forced a
pip freeze
from the same python executable invokingcibuildwheel
, and thefreeze
version is reporting2.16.5
, but the running version is reporting2.17.0
.THIS is the source of the mystery. Why are we getting
cibuildwheel==2.17.0
when everything we're seeing during install is2.16.6
?Code:
In Build:
This issue tracks understanding this question.
CC @jalauzon-msft
The text was updated successfully, but these errors were encountered: