Skip to content

🔒 🤖 CI Update lock files for array-api CI build(s) 🔒 🤖 #29198

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

Conversation

scikit-learn-bot
Copy link
Contributor

Update lock files.

Note

If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.

Copy link

github-actions bot commented Jun 6, 2024

✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

Generated for commit: 9473012. Link to the linter CI: here

@glemaitre glemaitre merged commit 4efe900 into scikit-learn:main Jun 6, 2024
33 checks passed
@lesteve
Copy link
Member

lesteve commented Jun 6, 2024

So we were wondering with @glemaitre why this was triggered, since lock-file update is supposed to be triggered weekly on Monday.

The answer is that this has been triggered manually (workflow_update) by @thomasjpfan and @betatim
https://github.com/scikit-learn/scikit-learn/actions/workflows/update-lock-files.yml
image

So I guess if you wanted to test triggering the GPU CI on this PR, well this has been merged too quickly 😅 ...

Note that this trigger all the lock-file updates for example the Cirrus arm lock-file was updated in #29197. In an ideal world you would be able to pass additional arguments to the workflow_update that get passed to the build_tools/update_environment_and_lock_files.py script but this is not very high priority.

@jeremiedbb jeremiedbb mentioned this pull request Jul 2, 2024
11 tasks
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.

4 participants