-
Notifications
You must be signed in to change notification settings - Fork 67
Copy all packages and catch those that couldn't be copied (infra) #2017
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
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2017 +/- ##
==========================================
+ Coverage 51.03% 51.04% +0.01%
==========================================
Files 385 385
Lines 41507 41524 +17
Branches 7712 7716 +4
==========================================
+ Hits 21184 21197 +13
- Misses 19563 19564 +1
- Partials 760 763 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
I guessed there could be a race condition, though I didn't guess the exact reason, XD.
I like this approach better. There is just one small comment. Since now we are copying all the packages (not only the checkbox ones), there could be a chance that we remove a package from the source PPA, and it will remain in the destination PPA, forever.
I don't think this is a big issue, but it would be great to include a comparison of the packages in the source PPA and the destination PPA for debugging purposes, as we have the output of the packages we have successfully copied.
816c69f
to
e7671e1
Compare
I've updated the code to also check if version are outdate and remove them from the desired list. AFAIK you can't remove packages from a PPA, so I'm not sure your comment applies. Still, we've never done something like that, I don't think it applies here |
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.
LGTM+1!
ngl, I'm unsure about what that button does and how to get to it regularly (when copies didn't fail). |
Description
The strategy of trying to infer what packages are to be copied has two disadvantages:
This leads to partial beta releases, like the one we just had. This fixes the issue by simply skipping the copy actions that fails with the error that the target build is outdated.
Resolved issues
Fixes: https://warthogs.atlassian.net/browse/CHECKBOX-1977
Documentation
N/A
Tests
Updated the tests and fixed the current release with this fix