Skip to content

Reenable graph reproducibility test#7694

Merged
jarrodmillman merged 1 commit intoscikit-image:mainfrom
matthew-brett:test-flaky-repo-test
Feb 3, 2025
Merged

Reenable graph reproducibility test#7694
jarrodmillman merged 1 commit intoscikit-image:mainfrom
matthew-brett:test-flaky-repo-test

Conversation

@matthew-brett
Copy link
Contributor

@matthew-brett matthew-brett commented Feb 3, 2025

Description

Reenable test marked as flaky; does it still fail (sometimes) on GHA?

@matthew-brett matthew-brett marked this pull request as draft February 3, 2025 17:01
@matthew-brett matthew-brett added the 🤖 type: Infrastructure CI, packaging, tools and automation label Feb 3, 2025
@matthew-brett matthew-brett changed the title Draft: Reenable test marked as flaky on Azure. MRG: Reenable test marked as flaky on Azure. Feb 3, 2025
@matthew-brett matthew-brett marked this pull request as ready for review February 3, 2025 19:26
@matthew-brett
Copy link
Contributor Author

Test has passed a couple of times at least. Shall we merge and see how it goes?

@stefanv stefanv changed the title MRG: Reenable test marked as flaky on Azure. Reenable test marked as flaky on Azure. Feb 3, 2025
@jarrodmillman jarrodmillman changed the title Reenable test marked as flaky on Azure. Reenable test on win32 Feb 3, 2025
@jarrodmillman jarrodmillman changed the title Reenable test on win32 Reenable graph reproducibility test on win32 Feb 3, 2025
@jarrodmillman jarrodmillman changed the title Reenable graph reproducibility test on win32 Reenable graph reproducibility test Feb 3, 2025
@jarrodmillman jarrodmillman merged commit 9bb95a7 into scikit-image:main Feb 3, 2025
24 checks passed
@stefanv
Copy link
Member

stefanv commented Feb 3, 2025

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?

@matthew-brett
Copy link
Contributor Author

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?

@stefanv
Copy link
Member

stefanv commented Feb 3, 2025

No, then probably not; just saw the win32 tag and wondered.

@matthew-brett
Copy link
Contributor Author

Sorry - where is the win32 tag - is it in the logs somewhere?

@stefanv
Copy link
Member

stefanv commented Feb 4, 2025

In the diff of this PR

@matthew-brett
Copy link
Contributor Author

Ah no - sorry - win32 there is generic for Windows. On Windows 11, 64-bit - information from systeminfo:

OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22631 N/A Build 22631
System Type:               x64-based PC

So - 64-bit operating system. And:

> python
Python 3.12.1 (tags/v3.12.1:2305ca5, Dec  7 2023, 22:03:25) [MSC v.1937 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys; sys.platform
'win32'
>>> import math
>>> math.log2(sys.maxsize) 
63.0

matthew-brett added a commit to matthew-brett/scikit-image that referenced this pull request Feb 4, 2025
…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)
@stefanv stefanv added this to the 0.25.2 milestone Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🤖 type: Infrastructure CI, packaging, tools and automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants