Skip to content

chore(asm): use byte pointer instead of c_char_p (#10428) #54667

chore(asm): use byte pointer instead of c_char_p (#10428)

chore(asm): use byte pointer instead of c_char_p (#10428) #54667

Triggered via pull request August 29, 2024 08:55
Status Failure
Total duration 13m 48s
Artifacts

lib-injection.yml

on: pull_request
build-and-publish-latest-snapshot-image  /  wait_for_package
build-and-publish-latest-snapshot-image / wait_for_package
build-and-publish-test-image  /  wait_for_package
9s
build-and-publish-test-image / wait_for_package
Matrix: test_unit
Matrix: test_unit_no_instrumentation
build-and-publish-latest-snapshot-image  /  ...  /  build_push
build-and-publish-latest-snapshot-image / build_push / build_push
build-and-publish-test-image  /  ...  /  build_push
13m 9s
build-and-publish-test-image / build_push / build_push
Matrix: test-runner-test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
build-and-publish-test-image / build_push / build_push
buildx failed with: ERROR: failed to solve: failed to push ghcr.io/datadog/dd-trace-py/dd-lib-python-init:e51a32b3359bab81fb13d2fc2b3eda91d7b7ec58: unexpected status from POST request to https://ghcr.io/v2/datadog/dd-trace-py/dd-lib-python-init/blobs/uploads/: 403 Forbidden
build-and-publish-test-image / build_push / build_push
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/