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
Building the python interpreter twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches.
For more background on the cause(s) of this problem, see #120858 and further resources linked there.
Notably, the remaining known upstream issue (python/cpython#81777) has been fixed in Python 3.11, so we should verify the problem remains after bumping the default python version to 3.11.
Anecdotally, on nixpkgs 6512b21nix-build --check '<nixpkgs>' -A python311 indeed succeeded for me, which is promising.
The text was updated successfully, but these errors were encountered:
Building the python interpreter twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches.
For more background on the cause(s) of this problem, see #120858 and further resources linked there.
Notably, the remaining known upstream issue (python/cpython#81777) has been fixed in Python 3.11, so we should verify the problem remains after bumping the default python version to 3.11.
Anecdotally, on nixpkgs 6512b21
nix-build --check '<nixpkgs>' -A python311
indeed succeeded for me, which is promising.The text was updated successfully, but these errors were encountered: