pytest-dev / pytest-dev/pytest-xdist

View output in jenkins

Open
#294 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi,

I'm using xdist in our automation - however, it seems like xdist doesn't throttle the tests correctly in the console.
How can we view the current state (which tests run and when)?

example :

14:47:56
14:47:56 #############################
14:47:56 # Starting to run the tests #
14:47:56 #############################
14:47:56
14:47:56 Tests are running with XDIST - stay tuned
14:47:56 Loading .env environment variables…
14:47:56 ============================= test session starts ==============================
14:47:56 platform linux2 -- Python 2.7.5, pytest-3.5.1, py-1.5.3, pluggy-0.6.0
14:47:56 rootdir: /, inifile:
14:47:56 plugins: xdist-1.22.2, pylint-0.9.0, metadata-1.7.0, html-1.17.0, forked-0.2, cov-2.5.1
14:47:57 gw0 I / gw1 I
14:47:58 gw0 [21] / gw1 [21]
14:47:58
14:47:58 scheduling tests via LoadScheduling

** after the last line - it seems like the job is working but nothing is being exported.

Thanks,
M

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 pytest-xdist run in Jenkins using the shown Python 2.7, pytest 3.5.1, and xdist 1.22.2 output, focusing on what happens after “scheduling tests via LoadScheduling.” Determine which test or console-output entry point controls progress visibility; done means the Jenkins job visibly reports the tests being executed or clearly explains the expected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.