-
Notifications
You must be signed in to change notification settings - Fork 356
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: handle failed checkpoints correctly [DET-3853] #1083
Conversation
@@ -485,6 +485,16 @@ def test_fail_on_first_validation() -> None: | |||
) | |||
|
|||
|
|||
@pytest.mark.e2e_cpu # type: ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make this into a unit test rather than an e2e test? We already have some infrastructure in trial_workload_sequencer_test.go
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about both? In theory, this covers more than just the trial workload sequencer. This covers making sure this class of failures is handled by the entire system.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, done
Description
This change fixes a bug in the trial workload sequencer were it is assumes that checkpoints won't fail. In the event of a failure checkpoint, a nil pointer is de-referenced when trying to access checkpoint metrics that don't exist in a failure.
Test Plan
Commentary (optional)