GH-43416: [CI] Upgrade vcpkg version on our CI#46009
GH-43416: [CI] Upgrade vcpkg version on our CI#46009raulcd wants to merge 3 commits intoapache:mainfrom
Conversation
|
@github-actions crossbow submit wheel-manylinux-2014-cp39-cp39-amd64 |
|
Revision: fad35652fad600aded226b6a2ae8ebe3ed427d9b Submitted crossbow builds: ursacomputing/crossbow @ actions-0ded48aaed
|
|
The manylinux job took 2 hours to build before grpc but has been stuck building grpc more than 3 hours (total 5hours+) I am unsure what the problem is but I have experienced the same issue locally that's why I was trying CI. |
|
FYI: (Sorry. This information is not related to the gRPC problem.) Our CI configuration has per package cache. So the next run (I re-ran the job) will start from gRPC build because we can use cache for other packages. |
|
@github-actions crossbow submit wheel-manylinux-2014-cp39-cp39-amd64 |
|
Revision: 10ae8abcccf076605440d0ea6321084d95d5bb2b Submitted crossbow builds: ursacomputing/crossbow @ actions-7718828f6e
|
|
Well, 6 hours (and timing out) only for grpc seems ... excessive :) |
|
I confirm that the compilers' errors reported by #43416 are resolved with man-group/ArcticDB@a5d0cdc which is an adaptation of this PR's revision of |
|
@github-actions crossbow submit wheel-manylinux-2014-cp39-cp39-amd64 |
|
Revision: 2142f6a Submitted crossbow builds: ursacomputing/crossbow @ actions-70c7056daa
|
|
@github-actions crossbow submit wheel-manylinux-2014-cp39-cp39-amd64 |
|
Revision: 2142f6a Submitted crossbow builds: ursacomputing/crossbow @ actions-7bc981d3a9
|
|
This was finally done at: |
3 participants
WIP
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?
This PR includes breaking changes to public APIs. (If there are any breaking changes to public APIs, please explain which changes are breaking. If not, you can remove this.)
This PR contains a "Critical Fix". (If the changes fix either (a) a security vulnerability, (b) a bug that caused incorrect or invalid data to be produced, or (c) a bug that causes a crash (even when the API contract is upheld), please provide explanation. If not, you can remove this.)