-
Notifications
You must be signed in to change notification settings - Fork 50
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
Handle trials with corrupted status #372
Handle trials with corrupted status #372
Conversation
Why: The helper functions were in different modules which was confusing. Moving them to storage/base and storage/legacy makes it more coherent.
Why: The method fetch many trials, not only one, hence the name is confusing.
Why: Database corruption occurs when there is Timeouts in PickledDB. The objective is saved but status is not set to completed. How: We catch non-completed trials with objective and log a warning with a pointer to documentation to manually fix corrupted trials.
f529bf8
to
e28a934
Compare
Closing and reopening to trigger build on travis-ci.com (migrated from travis-ci.org few minutes ago). |
Codecov Report
@@ Coverage Diff @@
## develop #372 +/- ##
===========================================
- Coverage 45.45% 45.22% -0.24%
===========================================
Files 67 67
Lines 12245 12388 +143
Branches 306 306
===========================================
+ Hits 5566 5602 +36
- Misses 6654 6761 +107
Partials 25 25
Continue to review full report at Codecov.
|
Why:
Database corruption occurs when there is Timeouts in PickledDB. The objective is saved but status is not set to completed.
How:
We catch non-completed trials with objective and log a warning with a pointer to documentation to manually fix corrupted trials.
Note:
Also add substantial documentation on storage which was required to document what the user can do to fix the database corruption.