10000 CI enable global_dtype fixture on nightly build jobs by jeremiedbb · Pull Request #23110 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

CI enable global_dtype fixture on nightly build jobs #23110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 19, 2022

Conversation

jeremiedbb
Copy link
Member

The globaly_dtype fixture is currently only enabled on a single CI job. It means that the float32 tests are never run on windows or macos for instance. Since enabling the fixture makes the test suite longer we don't want to do it by default, but enabling it for the nighlty build is a good compromise imo.

It would also make me more comfortable with replacing some current [float64, float32] parametrization by the global_dtype fixture.

@jeremiedbb jeremiedbb changed the title CI enable global dtype on nightly build jobs CI enable global_dtype fixture on nightly build jobs Apr 11, 2022
thomasjpfan
thomasjpfan previously approved these changes Apr 11, 2022
Copy link
Member
@thomasjpfan thomasjpfan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Although, this only runs on linux. From the existing [float32, float64] parameterizations that does not use global_dtype, we sometimes get errors on other platforms for different versions of SciPy+NumPy.

Edit: I misremembered how nightly builds work.

@jeremiedbb
Copy link
Member Author

Although, this only runs on linux

why do you say that ? The nightly build run on all platforms

@thomasjpfan
Copy link
Member
thomasjpfan commented Apr 11, 2022

why do you say that ? The nightly build run on all platforms

I was incorrect and misremembered how the nightly builds work.

@ogrisel
Copy link
Member
ogrisel commented Apr 12, 2022

I think the nightly on azure only run on linux with non-standard dependencies.

@jeremiedbb I believe you wanted to run the tests for the nightly wheel builds:

https://github.com/scikit-learn/scikit-learn/blob/main/.github/workflows/wheels.yml

@jeremiedbb
Copy link
Member Author

Oh right... @thomasjpfan you were right, I did misread the config ("ne" instead of "eq") :)

@jeremiedbb jeremiedbb dismissed thomasjpfan’s stale review April 12, 2022 11:57

avoid being merged too quickly

@jeremiedbb
Copy link
Member Author

Would it make sense to run all jobs in the azure config during the scheduled run ?

@thomasjpfan
Copy link
Member

I believe you wanted to run the tests for the nightly wheel builds:

I have a slight preference toward Azure so that wheel building remains simpler. But no strong opinion.

Would it make sense to run all jobs in the azure config during the scheduled run ?

I think it makes sense to do. I opened #23118 to enable this.

@ogrisel
Copy link
Member
ogrisel commented Apr 12, 2022

I am fine with either approach (Azure or the nightly wheels). As you prefer.

@jeremiedbb
Copy link
Member Author
jeremiedbb commented Apr 19, 2022

Since the azure cron job now runs all the jobs, I think this approach is simpler since there's nothing more to do 😄

@ogrisel
Copy link
Member
ogrisel commented Apr 19, 2022

Let's merge if green to give it a try next night.

@ogrisel ogrisel merged commit e358bd7 into scikit-learn:main Apr 19, 2022
jjerphan pushed a commit to jjerphan/scikit-learn that referenced this pull request Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

378D
3 participants
0