fix: test cases mlflow registry #415
Merged
Conversation
This file contains 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
Signed-off-by: Leila <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #415 +/- ##
==========================================
- Coverage 92.18% 92.16% -0.02%
==========================================
Files 97 97
Lines 4775 4776 +1
Branches 429 429
==========================================
Hits 4402 4402
Misses 276 276
- Partials 97 98 +1 ☔ View full report in Codecov by Sentry. |
s0nicboOm
requested review from
ab93,
qhuai,
nkoppisetty and
s0nicboOm
as code owners
ab93
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There existed errors in test logs while test cases still passed. One example is the ConnectionError due to not mocking mlflow function calls properly.
Fixed through modifying a few syntax for patch mock calls. The test cases should pass with no logging errors now.