This repository was archived by the owner on Sep 9, 2020. It is now read-only.
PRED-2940: Clear up errors and warnings from previous runs. #166
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 similar comment
|
Label Needs Review: Predictions was removed because @davidalien is part of Predictions domain. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the problem, when errors from previous runs show up in the script output for subsequent runs.
The root cause is that we store errors and warnings to the local DB and display them in the end.
This PR suggests always cleaning up error/warnings not only for
NewContextbut forOldContextas well.JIRA: https://datarobot.atlassian.net/browse/PRED-2940
Testing
Tested locally