Skip to content

Fix httpclient-5.x plugin injecting sw8 headers into ClickHouse HTTP requests #1101

Fix httpclient-5.x plugin injecting sw8 headers into ClickHouse HTTP requests

Fix httpclient-5.x plugin injecting sw8 headers into ClickHouse HTTP requests #1101

Re-run triggered March 11, 2026 14:25
Status Cancelled
Total duration 28m 15s
Artifacts 2

plugins-jdk17-test.1.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 1 warning
resteasy-6.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
caffeine-3.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
c3p0-0.9.0.x-0.9.1.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
c3p0-0.9.2.x-0.10.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
spring-6.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
gateway-4.1.2.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
gateway-4.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
Test
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
activemq-artemis-2.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
httpexchange-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
spring-scheduled-6.x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
lettuce-webflux-6x-scenario-jdk17
Canceling since a higher priority waiting request for plugins-jdk17-1-797 exists
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
skywalking-agent
44.3 MB
sha256:d3970672b44ae3c7d0d9cb7b8f2fb0c43b64fe1eac0211ab3f95c8c1ec360db2
test-tools
527 MB
sha256:852f257b64d27d4da979fed9d005736bc3473343faddbad134e27b9ec0467363