🔒 🤖 CI Update lock files for scipy-dev CI build(s) 🔒 🤖

[scikit-learn-bot]

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.

[github-actions]

✔️ Linting Passed

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

_{Generated for commit: 7f75a23. Link to the linter CI: here}

[ogrisel]

The 26 failures are probably those reported in #28868. However the run with the updated lock files adds a internal error on top of that:

INTERNALERROR> execnet.gateway_base.RemoteError: concurrent remote_exec would cause deadlock for main_thread_only execmodel

This looks like a consequence of the update to pytest-xdist 3.6.0 (instead of 3.5.0 previously).

[ogrisel]

The regression on pytest-xdist was reported 3 days ago at:

• [REGRESSION][pytest-xdist == 3.6.0] Makes pre-existing pytest configurations crash with execnet.gateway_base.RemoteError: concurrent remote_exec would cause deadlock for main_thread_only execmodel pytest-dev/pytest-xdist#1071

[ogrisel]

Curiously enough this problem did not happen for build_tools/azure/pylatest_pip_openblas_pandas_linux-64_conda.lock updated to pytest-xdist 3.6.0 in #28872 that I recently merged. If we start observing similar failures in PRs, we might want to pin pytest-xdist to 3.5.0 while the problem is investigated upstream.

[ogrisel]

The recently released pytest-xdist 3.6.1 shipped the fix for the race condition triggering the previous CI failure.