Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2025

This PR contains the following updates:

Package Change Age Confidence
pytest-xdist (changelog) ==3.7.0 -> ==3.8.0 age confidence

Release Notes

pytest-dev/pytest-xdist (pytest-xdist)

v3.8.0

Compare Source

===============================

Features

  • #&#8203;1083 <https://github.com/pytest-dev/pytest-xdist/issues/1083>_: Add --no-loadscope-reorder and --loadscope-reorder option to control whether to automatically reorder tests in loadscope for tests where relative ordering matters. This only applies when using loadscope.

    For example, [test_file_1, test_file_2, ..., test_file_n] are given as input test files, if --no-loadscope-reorder is used, for either worker, the test_file_a will be executed before test_file_b only if a < b.

    The default behavior is to reorder the tests to maximize the number of tests that can be executed in parallel.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x branch from 6e91080 to e2551f7 Compare August 10, 2025 13:18
@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x branch from e2551f7 to cf18e0c Compare October 21, 2025 10:58
@renovate
Copy link
Contributor Author

renovate bot commented Oct 21, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Pipfile.lock
Command failed: pipenv lock
Creating a virtualenv for this project
Pipfile: /tmp/renovate/repos/github/saucelabs-training/demo-python/Pipfile
Using /usr/local/bin/python33.14.0 to create virtualenv...
created virtual environment CPython3.14.0.final.0-64 in 452ms
  creator 
CPython3Posix(dest=/runner/cache/others/virtualenvs/demo-python-pkXjvlzF, 
clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, via=copy, 
app_data_dir=/tmp/containerbase/cache/.local/share/virtualenv)
    added seed packages: pip==25.3
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator
,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /runner/cache/others/virtualenvs/demo-python-pkXjvlzF
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Ignored the 
following versions that require a different python version: 6.4.0 
Requires-Python <3.12,>=3.8; 6.4.0rc1 Requires-Python <3.12,>=3.8; 6.5.0 
Requires-Python <3.12,>=3.8; 6.5.0rc1 Requires-Python <3.12,>=3.8; 6.6.0 
Requires-Python <=3.12,>=3.8; 6.6.1 Requires-Python <3.13,>=3.8; 6.7.0 
Requires-Python <3.14,>=3.8; 6.7.0rc1 Requires-Python <3.14,>=3.8; 6.7.1 
Requires-Python <3.14,>=3.8
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Could not 
find a version that satisfies the requirement 
robotframework-seleniumlibrary==6.7.1 (from versions: 2.9.2, 3.0.0a2, 3.0.0b1, 
3.0.0b3, 3.0.0rc1, 3.0.0rc2, 3.0.0, 3.0.1, 3.1.0a1, 3.1.0a2, 3.1.0, 3.1.1, 
3.2.0rc1, 3.2.0, 3.3.0, 3.3.1, 4.0.0a1, 4.0.0a2, 4.0.0b1, 4.0.0rc1, 4.0.0, 
4.1.0rc1, 4.1.0, 4.2.0rc1, 4.2.0, 4.3.0rc1, 4.3.0, 4.4.0rc1, 4.4.0rc2, 4.4.0rc3,
4.4.0, 4.5.0rc1, 4.5.0rc2, 4.5.0, 5.0.0a1, 5.0.0a2, 5.0.0a3, 5.0.0b1, 5.0.0, 
5.0.1, 5.1.0, 5.1.1, 5.1.2, 5.1.3, 6.0.0rc1, 6.0.0, 6.1.0rc1, 6.1.0, 6.1.1rc1, 
6.1.1, 6.1.2rc1, 6.1.2, 6.1.3b1, 6.1.3, 6.2.0rc1, 6.2.0, 6.3.0rc1, 6.3.0rc2, 
6.3.0, 6.8.0)
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.14.0/lib/python3.14/site-packages/pi
penv/resolver.py", line 451, in main
[ResolutionFailure]:       _main(
[ResolutionFailure]:       ~~~~~^
[ResolutionFailure]:       parsed.pre,
[ResolutionFailure]:       ^^^^^^^^^^^
[ResolutionFailure]:       ...<7 lines>...
[ResolutionFailure]:       category=parsed.category,
[ResolutionFailure]:       ^^^^^^^^^^^^^^^^^^^^^^^^^
[ResolutionFailure]:       )
[ResolutionFailure]:       ^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.14.0/lib/python3.14/site-packages/pi
penv/resolver.py", line 436, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:       ~~~~~~~~~~~~~~~~^
[ResolutionFailure]:       pre, clear, verbose, system, write, requirements_dir,
packages, category
[ResolutionFailure]:       
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ResolutionFailure]:       )
[ResolutionFailure]:       ^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.14.0/lib/python3.14/site-packages/pi
penv/resolver.py", line 400, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve_deps(
[ResolutionFailure]:       ~~~~~~~~~~~~^
[ResolutionFailure]:       packages,
[ResolutionFailure]:       ^^^^^^^^^
[ResolutionFailure]:       ...<7 lines>...
[ResolutionFailure]:       req_dir=requirements_dir,
[ResolutionFailure]:       ^^^^^^^^^^^^^^^^^^^^^^^^^
[ResolutionFailure]:       )
[ResolutionFailure]:       ^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.14.0/lib/python3.14/site-packages/pi
penv/utils/resolver.py", line 1083, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = 
actually_resolve_deps(
[ResolutionFailure]:       ~~~~~~~~~~~~~~~~~~~~~^
[ResolutionFailure]:       deps,
[ResolutionFailure]:       ^^^^^
[ResolutionFailure]:       ...<7 lines>...
[ResolutionFailure]:       req_dir=req_dir,
[ResolutionFailure]:       ^^^^^^^^^^^^^^^^
[ResolutionFailure]:       )
[ResolutionFailure]:       ^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.14.0/lib/python3.14/site-packages/pi
penv/utils/resolver.py", line 811, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:       ~~~~~~~~~~~~~~~~^^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.14.0/lib/python3.14/site-packages/pi
penv/utils/resolver.py", line 471, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=e)
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: No matching distribution found for robotframework-seleniumlibrary==6.7.1

Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Failed to lock Pipfile.lock!

@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x branch from cf18e0c to 9229887 Compare October 30, 2025 14:44
@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x branch from 9229887 to ec47c5c Compare October 30, 2025 15:08
@renovate renovate bot changed the title Update dependency pytest-xdist to v3.8.0 Update dependency pytest-xdist to v3.8.0 - autoclosed Oct 30, 2025
@renovate renovate bot closed this Oct 30, 2025
@renovate renovate bot deleted the renovate/pytest-xdist-3.x branch October 30, 2025 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants