-
Notifications
You must be signed in to change notification settings - Fork 349
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
ci: try to fix podman tests by building proto once #9267
Conversation
✅ Deploy Preview for determined-ui canceled.
|
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9267 +/- ##
==========================================
- Coverage 44.59% 44.58% -0.02%
==========================================
Files 1273 1273
Lines 155832 155832
Branches 2439 2438 -1
==========================================
- Hits 69501 69472 -29
- Misses 86092 86121 +29
Partials 239 239
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
There have been some other questionable things recently where workspace data seems to be different in later steps after rebuilds, and rebuilding things repeatedly is part of why our tests are so dang slow to begin with. Thanks for this; hopefully it helps. :)
Ticket
Description
Fix failing podman tests
https://app.circleci.com/pipelines/github/determined-ai/determined/54910/workflows/19816278-7088-4c7e-910e-5a6c50699a96/jobs/2515396
Don't build proto again. We probably shouldn't be building proto more than once per CI. We also likely don't even need to build
proto
at all. My best guess of what is going on is somehow thestore_artifacts
is interacting weirdly with us building proto again so try making sure we always run after build proto is done.Test Plan
Tests pass on main after landing
Checklist
docs/release-notes/
.See Release Note for details.