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.

Sign up for GitHub

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

Jump to bottom

Handle "metadata" durring test setup #85

Open

prusse-martin opened this issue Feb 5, 2025 · 0 comments

Member

prusse-martin commented Feb 5, 2025 •

edited

Loading

As a follow up to #78 the intent is to tackle the limitation stated there "... when a core dump happens before the data is written...".

A possible approach could be something in the lines of:

{"nodeid": "test_1.py::test_bar", "start": 3.0}
{"nodeid": "test_1.py::test_bar", "start": 3.0, "metadata": {"a": "asd"}}
{"nodeid": "test_1.py::test_bar", "start": 3.0, "metadata": {"a": "asd", "b": 7}}
{"nodeid": "test_1.py::test_bar", "start": 3.0, "metadata": {"a": "asd", "b": 7}, "finish": 4.0, "outcome": "passed"}

There we see the metadata evolving.

And probably could help pinpoint the crash source if the output is just:

{"nodeid": "test_1.py::test_bar", "start": 3.0}
{"nodeid": "test_1.py::test_bar", "start": 3.0, "metadata": {"a": "asd"}}

(a crash cause some lines to not be present)

from: #82 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment