-
Notifications
You must be signed in to change notification settings - Fork 175
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
[Util] Check checkpoint file exists when running state extraction #6459
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6459 +/- ##
==========================================
- Coverage 41.65% 41.45% -0.21%
==========================================
Files 1974 2026 +52
Lines 139202 144611 +5409
==========================================
+ Hits 57985 59944 +1959
- Misses 75189 78468 +3279
- Partials 6028 6199 +171
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Thank you!
a677314
to
24d820d
Compare
|
||
err := ensureCheckpointFileExist(flagExecutionStateDir) | ||
if err != nil { | ||
log.Error().Err(err).Msgf("cannot ensure checkpoint file exist in folder %v", flagExecutionStateDir) |
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.
Some test cases wants the checkpoint folder to be empty. Changed it from Fatal to Error for now.
When running state extraction with a wrong
--execution-state-dir
flag, the error message is misleading.This PR adds check to ensure checkpoint file can be found in the specified
--execution-state-dir
and improved error message when a wrong or empty folder is used.