Skip to content

Environment is not populated when using pytest-xdist #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
davehunt opened this issue Sep 3, 2015 · 2 comments
Closed

Environment is not populated when using pytest-xdist #18

davehunt opened this issue Sep 3, 2015 · 2 comments

Comments

@davehunt
Copy link
Collaborator

davehunt commented Sep 3, 2015

The environment section in the HTML report is missing when we run tests in parallel using pytest-xdist. I'm hoping that @RonnyPfannschmidt can take a look and suggest how we can fix it. 😄

@RonnyPfannschmidt
Copy link
Member

its impossible to share the information as is

the current implementation basically relies on "global variables"

pytest-xdist has the concept of a slaveoutput, which i a dictionary

you can pass normal strings/numbers with ease using that

the objects you should interact with on the slave are
config.slaveinput and config.slaveoutput

to finish the reporting there is a hook called pytest_testnodedown(node, error)
the node will have a slaveoutput attribute matching the dictionary of the slave

so you can just set config.slaveoutput['environment'] = environment and access it on the master in the testnodedown hook and add each nodes environment to a list for use in reporting

to handle configuration there is the pytest_configure_node(node) hook, the node will have a slaveinput attribute where you can add extra inputs

@davehunt
Copy link
Collaborator Author

davehunt commented Sep 8, 2015

Thanks @RonnyPfannschmidt, I've been able to fix this in pull #19. Would you be able to take a look and let me know if there's anything concerning in my changes?

drRedflint pushed a commit to drRedflint/pytest-html that referenced this issue Aug 10, 2022
* Move outcome handling to backend
BeyondEvil added a commit that referenced this issue Mar 5, 2023
* fix main.js conflicts

* fix js test

* fix resource (main.js) test

* revert change to report extra

* filters style

* css and dom brush up

* Buildable app

* always store data in html

* Always store data blob in file

* json dump test data

* read data from dom element

* manually initialize state

* minimalistic dataset

* simplify included files

* Handle report extras

* Handle python report hooks

* imgviewer

* present name in image viewer and open img on click

* setup linter for project

* conform to styles

* show video in imageviewer (#14)

* show video in imageviewer

* Chore: Pluralize extra (#15)

* Add extras.HTML

* Move outcome handling to backend (#18)

* Move outcome handling to backend

* Pass in text version of longrepr if present

* make collapse/expand all functional (#20)

* make collapse/expand all functional

* only create links for text, url and json (#22)

* make filter search case insensitive (#21)

* make filter search case insensitive

* use sessionStorage to prevent preferences to be reapplied on new reports

* avoid multiple event bindings + fix filter bug

* Collapse individual row

Co-authored-by: Jim Brännlund <[email protected]>

* add no log output captured string

* Query params (#25)

* Add query params

* adjust tests (#26)

* Duration format (#27)

* adjust tests

* build format handler

* remove dependency

---------

Co-authored-by: Jim Brännlund <[email protected]>

* Beyondevil/cleanup (#28)

* chore: Cleanup branch before merge

* chore: Fix duration and CI

* Fix pre-commit issues

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Viktor Gustafsson <[email protected]>
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

No branches or pull requests

2 participants