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

fix(torture): move snapshot check #713

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

gabriele-0201
Copy link
Contributor

Previously, the check was made immediately after respawning the child,
which implied a check of the snapshot over a non-up-to-date
state.last_snapshot(), leading to incorrect checks.

@rphmeier rphmeier force-pushed the gm_torture_random_sample_entire_state branch 2 times, most recently from 9d61919 to 599b9b8 Compare January 23, 2025 19:23
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_random_sample_entire_state branch from 599b9b8 to 49224a2 Compare January 24, 2025 10:01
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_move_shanpshot_check branch from 13263ae to 0d9d2be Compare January 24, 2025 10:01
Base automatically changed from gm_torture_random_sample_entire_state to master January 24, 2025 11:47
Previously, the check was made immediately after respawning the child,
which implied a check of the snapshot over a non-up-to-date
`state.last_snapshot()`, leading to incorrect checks.
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_move_shanpshot_check branch from 0d9d2be to 5435408 Compare January 24, 2025 11:48
@gabriele-0201 gabriele-0201 merged commit 50daa3d into master Jan 24, 2025
8 checks passed
@gabriele-0201 gabriele-0201 deleted the gm_torture_move_shanpshot_check branch January 24, 2025 12:35
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