-
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
ci: bump docker and docker-dind to 20.10.20 for gitlab #5045
Conversation
why? |
Required for #5044, see ac1f853's comment
Current version of Docker (19.03.5) won't work as Jammy compatibility was added in 20.10.13 (changelog) and alongside "improperly passed syscalls" (at least, based on this answer). Currently, with the bug, builds are failing (for example, this GitLab CI job) and the solution (per my testing) was to update to GCC 10 and while I can do that for all cross compilation targets, I cannot do that for Windows cross compilation (see package), the same way I can for ARM64 cross compilation (see package) |
I don't think this makes senes. Looks like 9.5.0 of gcc has the bug fix also. I really don't think we should upgrade to ubuntu 22.04 at this point. |
I am currently not aware of any way to force "non-native" targets (read, mingw-w64) to deviate from the base distribution's standard library, the "base" for focal is 9.4.0-1ubuntu1~20.04.1 as of now, which is still affected by the bug. To the best of my knowledge, the least inelegant way of upgrading the base libraries is by upgrading the distro entirely. |
What commit introduces the buggy code? |
It's not our code that's buggy, rather it's our code that trips the bug. But regardless, that would be 711f929, specifically portions unchanged by the commit that are affected by it, that are Dash-specific, like Line 1219 in 711f929
With Ubuntu 22.04, these types of constructions build just fine with tests passing (tested locally within WSL2) |
Are there alternative fixes? maybe by changing how we initialize these requests? How did bitcoin-core avoid this buggy compiler code? |
Yes, but that workaround (using the assignment operator) doesn't work for us for some reason, it gives a different error instead. |
The bug in question has been sidestepped with #5055, this PR has been modified to only bump the underlying version of Docker, which adds Jammy support but our containers will still remain on Focal. |
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.
utACK, let's try it and see if it works. Manager node might need upgrading.
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.
blocking this with a "request changes" review to make sure it's not merged prior to #5068 (or any alternative PR) which fixes CI failures introduced by these changes
This pull request has conflicts, please rebase. |
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.
👍
CI is currently failing... Rebasing to see if that helps for some reason https://gitlab.com/dashpay/dash/-/jobs/3256133934 |
af2814b
to
4ad79ac
Compare
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.
utACK
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.
utACK for squash merge
Issue being fixed or feature implemented
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:
For repository code-owners and collaborators only