Skip to content

Conversation

@valeriupredoi
Copy link
Contributor

@valeriupredoi valeriupredoi commented Jan 26, 2022

Description

Second attempt at fixing the issue of missing .pymon-journal file during a pytest monitored session: this time around we moving the output database one dir up


Before you get started

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

@valeriupredoi valeriupredoi requested a review from zklaus January 26, 2022 15:53
@valeriupredoi valeriupredoi changed the title Reloacate pytest-monitor outputted database so .pymon-journal file should not be looked for by pytest Relocaate pytest-monitor outputted database .pymon so .pymon-journal file should not be looked for by pytest Jan 26, 2022
@valeriupredoi valeriupredoi changed the title Relocaate pytest-monitor outputted database .pymon so .pymon-journal file should not be looked for by pytest Relocate pytest-monitor outputted database .pymon so .pymon-journal file should not be looked for by pytest Jan 26, 2022
@valeriupredoi
Copy link
Contributor Author

valeriupredoi commented Jan 26, 2022

OK I ran a full set of monitoring tests - no .pymon-journal crappe (segfault for one OSX test tho); running one more full set now - and huzzah! It looks this did the trick @zklaus - two full sets of tests and no crappe! 💩

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pytest .pymon-journal problem

3 participants