-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
exp: Unify dvc exp list and show output #9808
exp: Unify dvc exp list and show output #9808
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #9808 +/- ##
=======================================
Coverage 90.40% 90.41%
=======================================
Files 484 484
Lines 36919 36916 -3
Branches 5334 5332 -2
=======================================
- Hits 33377 33376 -1
+ Misses 2930 2929 -1
+ Partials 612 611 -1
☔ 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.
Thanks for the PR! It's the right idea, I left some comments on how we could make the internal APIs a little bit cleaner.
@pmrowla I made the changes that you suggested and I think it all works well now and However, some of the tests are written to check things in The tests in question were all written by @dberenbaum , so maybe we can have a look at that together (seeing as we are closer timezone-wise) |
@tibor-mach the tests for |
Ok, I will have a look at how the tests are done and if I need any help, I will ask @dberenbaum |
@pmrowla the tests should all work as intended now. I am not sure why Also, shouldn't we have a test that checks the desired order of head-tag-branch on the UI level for both exp show and exp list? Or maybe it would be enough to test the newly public Also please have a look at how I handled the typing in the UI. Perhaps that is what is making it fail benchmarks? Thanks! |
I'm a bit confused about this error on Windows. It only seems to happen with Python 3.9 and it doesn't really seem to be related to anything I changed... @pmrowla any ideas? |
It's a known flaky test, you can disregard that failure since it's not related to your changes |
Ok then @pmrowla do you think we need some extra tests for the |
Solves #9794