Conversation
b6742bc to
6537ad9
Compare
9065e41 to
a70ab2e
Compare
|
@cbodley Can you take a look at this? GCC marks an error at https://github.com/adamemerson/ceph/blob/wip-boost-1.87/src/librbd/migration/HttpClient.cc#L969 and I'm not quite sure where it's going wrong. Asio is failing to move-construct a Beast stream, it appears. |
|
seastar should be ok with: #61735 I get multiple warnings of: Did you have these as well? |
fix a bunch of stuff that boost 1.87 broke around boost::asio, largely involving deprecated function overloads being removed. I did this independently of the upstream, but I realized belatedly that I should have just looked in the PR lists first, as 90% of the fixes already existed, unmerged. References: ceph/ceph#61084
Yes. I think some of the less maintained parts of boost use deprecated constructs. It is very annoying. Spirit and MPI seem to be the worst offenders. Short term I was thinking of suppressing the warnings around includes of things we don't control. Long term I'd like us to replace our uses of Boost.Spirit and similar pre-Modern Boost libraries that have been accumulating more flakiness as we upgrade. But we don't have to worry about that for now. |
a70ab2e to
7bdd877
Compare
|
@petrutlucian94 Do you know what might be up with the windows failure here? It looks like Boost is expecting a header that isn't there? |
|
@ljflores Could we get this tested against core, please? |
|
@adamemerson I see that it was fixed here: boostorg/stacktrace@d6499f2 It wasn't released yet so we'll need to apply the fix ourselves through |
|
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
7bdd877 to
a773800
Compare
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
Because Boost including its own deprecated headers is not our problem. Signed-off-by: Adam Emerson <aemerson@redhat.com>
4670e6f to
f9a687a
Compare
|
#62242 - fixed the error in running it again |
|
jenkins test make check |
|
jenkins test make check arm64 |
2 similar comments
|
jenkins test make check arm64 |
|
jenkins test make check arm64 |
|
@cbodley Between https://pulpito.ceph.com/aemerson-2025-03-13_06:04:34-rgw-wip-boost-1.87-distro-default-smithi/ and https://pulpito.ceph.com/aemerson-2025-03-13_15:10:21-rgw-wip-boost-1.87-distro-default-smithi/ and the lone failure being a known fault, can we count this as QAd successfully for RGW? |
👍 |
ceph#61084 bumped up the version used to 1.87. The warning should be for 1.88, same as it was 1.86 when we used 1.85. Fixes: https://tracker.ceph.com/issues/70725 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
For reasons of Python and Asio valgrinding.
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e