pytest-dev / pytest-dev/pytest-xdist

Progress output gets misaligned with default verbosity

Open
#273 1 comment 1 reaction 1 assignee View on GitHub

@nicoddemus is already working on this.

Since Jan 31, 2018.

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

Description

Just noticed that with pytest-xdist 1.22.0 and pytest 3.4.0 sometimes the progress output is off by 1 or 2 characters.

Test file:

import pytest
@pytest.mark.parametrize('i', range(300))
def test(i): 
    pass

Here are a few runs:

$ pytest -n2
...
scheduling tests via LoadScheduling
................................................................................................................ [ 37%]
................................................................................................................. [ 74%]
...........................................................................                                      [100%]
============================================= 300 passed in 3.64 seconds ==============================================
$ pytest -n8
...
scheduling tests via LoadScheduling
................................................................................................................ [ 36%]
.................................................................................................................... [ 73%]
........................................................................                                         [100%]
============================================= 300 passed in 6.23 seconds ==============================================

This problem happens sometimes only, other times (seems random) the output is correct.

Seems related to pytest 3.4.0, because with pytest 3.3.2 I can't reproduce the issue.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.