pytest-dev / pytest-dev/pytest-xdist

Suppress header output

Open
#958 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.9k
Forks
287
Avg merge
9h 30m
Merged PRs (30d)
2

Description

Is there any way to suppress this output at the start of pytest -n auto? -q has no output.

[gw0] darwin Python 3.9.17 cwd: /some/path
[gw1] darwin Python 3.9.17 cwd: /some/path
[gw2] darwin Python 3.9.17 cwd: /some/path
[gw3] darwin Python 3.9.17 cwd: /some/path
[gw4] darwin Python 3.9.17 cwd: /some/path
[gw5] darwin Python 3.9.17 cwd: /some/path
[gw6] darwin Python 3.9.17 cwd: /some/path
[gw7] darwin Python 3.9.17 cwd: /some/path
[gw8] darwin Python 3.9.17 cwd: /some/path
[gw9] darwin Python 3.9.17 cwd: /some/path
[gw0] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw1] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw2] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw3] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw4] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw6] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw5] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw7] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
[gw8] Python 3.9.17 (main, Jun 12 2023, 14:44:48)  -- [Clang 14.0.3 (clang-1403.0.22.14.1)]
gw0 [2] / gw1 [2] / gw2 [2] / gw3 ok / gw4 ok / gw5 ok / gw6 ok / gw7 ok / gw8 ok / gw9 gw0 [2] / gw1 [2] / gw2 [2] / gw3 [2] / gw4 ok / gw5 ok / gw6 ok / gw7 ok / gw8 ok / gw9

This is a large log spew that is irrelevant to the user running the test.

I tried searching through the issues here and docs, but couldn't find a way that would suppress this output.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported output with pytest -n auto, then trace the xdist entry point that emits the worker headers and status lines. Done means users can suppress this irrelevant startup output while normal test results remain available; the payload names no source files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, distributed-systems, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.