Skip to content
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

DM-41846: Use the test ID as the unique component of the test run collection #119

Merged
merged 1 commit into from
Nov 27, 2023

Conversation

timj
Copy link
Member

@timj timj commented Nov 22, 2023

This is a reasonable thing to do in general, but is important when using pytest-randomly because when using that plugin without the --randomly-dont-reset-seed flag, the seed is forced to the global value before every test is run. This leads to makeTestCollection returning the same random integer for every test and the runs clash in the shared repo.


  • Passes Jenkins CI.
  • Documentation is up-to-date.

Preview the docs at: https://pipelines.lsst.io/v/DM-FIXME

This is a reasonable thing to do in general, but is important when
using pytest-randomly because when using that plugin without the
--randomly-dont-reset-seed flag, the seed is forced to the global
value before every test is run. This leads to makeTestCollection
returning the same random integer for every test and the runs
clash in the shared repo.
@timj timj merged commit 617add9 into main Nov 27, 2023
2 checks passed
@timj timj deleted the tickets/DM-41846 branch November 27, 2023 18:49
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

Successfully merging this pull request may close these issues.

2 participants