Skip to content

Conversation

marcphilipp
Copy link
Member

Prior to this commit the default seeds were generated separately but the
configuration parameter that allows using a fixed seed only allowed to
set both to the same value making it impossible to reproduce a failure
for different default seeds. Since the default seed is now identical,
this scenario is avoided.

Fixes #3817.

Prior to this commit the default seeds were generated separately but the
configuration parameter that allows using a fixed seed only allowed to
set both to the same value making it impossible to reproduce a failure
for different default seeds. Since the default seed is now identical,
this scenario is avoided.

Fixes #3817.
@marcphilipp marcphilipp merged commit a422c5a into main May 17, 2024
@marcphilipp marcphilipp deleted the marc/3817-align-random-ordering-default-seeds branch May 17, 2024 13:09
marcphilipp added a commit that referenced this pull request Jun 17, 2024
Prior to this commit the default seeds were generated separately but the
configuration parameter that allows using a fixed seed only allowed to
set both to the same value making it impossible to reproduce a failure
for different default seeds. Since the default seed is now identical,
this scenario is avoided.

Fixes #3817.

(cherry picked from commit a422c5a)
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.

ClassOrderer.Random and MethodOrderer.Random do not use same default seed
2 participants