Reenable graph reproducibility test#7694
Conversation
12a57b1 to
571f9c1
Compare
|
Test has passed a couple of times at least. Shall we merge and see how it goes? |
|
When Jarrod just changed the name, I realized that Azure was 32-bit, and new platform is 64-bit. Maybe there's something specific to 32-bit that caused the problem? |
|
Ah - interesting - as far as I can see the Azure images were Windows Server 2022 - and I think that doesn't have a 32-bit version - they are all 64-bit. And the logs have x64 versions of Python. Are you sure about the 32-bit? |
|
No, then probably not; just saw the win32 tag and wondered. |
|
Sorry - where is the win32 tag - is it in the logs somewhere? |
|
In the diff of this PR |
|
Ah no - sorry - So - 64-bit operating system. And: |
…ailure * origin/main: Add zizmor to pre-commit; address GH workflow issues raised (scikit-image#7662) Reenable test marked as flaky on Azure. (scikit-image#7694) Simultaneously resolve all dependencies; add pip caching (scikit-image#7690) Copy keypoints if necessary to preserve contiguity (scikit-image#7692) CI cleanup (scikit-image#7693) Port CI testing from Azure to GitHub (scikit-image#7687) Lower CI build verbosity Use pytest config in pyproject.toml in CI (scikit-image#7555) Improve docstring for rolling_ball function. (scikit-image#7682)
Description
Reenable test marked as flaky; does it still fail (sometimes) on GHA?