Skip to content

Add a special case for how S3 requests should be signed #4864

Add a special case for how S3 requests should be signed

Add a special case for how S3 requests should be signed #4864

Triggered via pull request January 2, 2025 16:34
@BaccataBaccata
synchronize #1605
s3-signing
Status Cancelled
Total duration 8m 44s
Artifacts 1

ci.yml

on: pull_request
Matrix: build
Publish Docs Microsite
0s
Publish Docs Microsite
build-success-checkpoint
0s
build-success-checkpoint
Release
0s
Release
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Test 2_12 (jvm)
Canceling since a higher priority waiting request for 'ci-refs/pull/1605/merge' exists
Test 2_12 (jvm)
The operation was canceled.
Test 3_0 (jvm)
Canceling since a higher priority waiting request for 'ci-refs/pull/1605/merge' exists
Test 3_0 (jvm)
The operation was canceled.
Test 3_0 (native)
Canceling since a higher priority waiting request for 'ci-refs/pull/1605/merge' exists
Test 3_0 (native)
The operation was canceled.
Test 2_13 (jvm)
Canceling since a higher priority waiting request for 'ci-refs/pull/1605/merge' exists
Test 2_13 (jvm)
The operation was canceled.
Test 3_0 (js)
Canceling since a higher priority waiting request for 'ci-refs/pull/1605/merge' exists
Test 3_0 (js)
The operation was canceled.
Test 2_13 (js)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
compilation-2_13_js.zip
21.4 MB