question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not sure I understand the output when I use -n=12

See original GitHub issue

Why, when I do pytest -n=12 does it look like I have so many workers ? I am I misunderstanding something, I thought it would be 12 worker processes. (I have 8 threads on the CPU, is there something I’m missing?)

pytest -n=12
========================== test session starts ==========================
platform linux -- Python 3.8.8, pytest-6.2.2, py-1.10.0, pluggy-0.13.1
Test order randomisation NOT enabled. Enable with --random-order or --random-order-bucket=<bucket_type>
django: settings: settings.test (from ini)
rootdir: /home/stu/projects/work/dit/tamato, configfile: pyproject.toml
plugins: celery-0.0.0, random-order-1.0.4, xdist-2.3.0, allure-pytest-bdd-2.8.33, Faker-8.10.1, responses-0.5.0, django-4.1.0, forked-1.3.0, bdd-4.0.2
gw0 I / gw1 I / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 I / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 I / gw5 I / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 I / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 I / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 C / gw7 I / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 C / gw7 C / gw8 I / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 C / gw7 C / gw8 C / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 C / gw7 C / gw8 C / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 C / gw7 C / gw8 C / ggw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 gw0 [1814] / gw1 [1814] / gw2 [1814] / gw3 [1814] / gw4 [1814] / gw5 [1814] / gw6 [1814] / gw7 [1814] / gw8 [1814] / gw9 [1814] / gw10 [1814] / gw11 [1814]

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
nicoddemuscommented, Jul 29, 2021

I could make a video of it if that helps ?

I don’t think that’s necessary, but thanks!

0reactions
amyXia1994commented, Aug 24, 2021

Can I also ask in this print out gw0 [21] / gw1 [21] / gw2 [21] / gw3 [21] / gw4 [21] / gw5 [21] / gw6 [21] / gw7 [21] / gw8 [21] / gw9 [21] that I get from running 10 workers, what does [21] mean?

I think the 21 means that each worker has collected 21 tests, and that also means that you have totally 21 test cases

Read more comments on GitHub >

github_iconTop Results From Across the Web

UPDATED: N12 – Terminating a Tenancy for Purchaser's Own ...
N12 Notice for Purchaser's Own Use: Termination Date​​ It's important to note that the notice becomes void if the landlord does not apply...
Read more >
N12 - Terminating a Tenancy for Landlord's Own Use - YouTube
This updated Form N12 - Terminating a Tenancy for Landlord's Own Use Learning Module reflects recently passed amendments to the Residential ...
Read more >
2021 Landlord Education Series: N12 and N13 - YouTube
In the second of four videos for small residential landlords renting in Ontario, the LSHC staff present information on ending a tenancy ...
Read more >
Yamaha n12 weird issue. Can someone help? - Cubase
I tried installing 2 versions of the Yahama Steinberg Driver, 3 versions of windows on 2 computers, both the FW ports on both,...
Read more >
Eviction Via Form N12 Process Requires Good Faith Intention ...
Understanding the Duty of Good Faith Required Within An N12 Eviction For Own ... the own use purposes of the landlord, or certain...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found