Support tracing RAG retrieval in Spring AI 1.x plugin #2141
peachisaiplugins-jdk17-test.0.yaml
on: pull_request
Build
6m 51s
Matrix: test
Annotations
22 errors and 15 warnings
|
spring-ai-1.x-scenario-jdk17
Process completed with exit code 1.
|
|
jdk17-with-gson-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
undertow-2.3.x-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
undertow-2.3.x-scenario-jdk17
The operation was canceled.
|
|
jetty-thread-pool-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
jetty-thread-pool-scenario-jdk17
The operation was canceled.
|
|
jetty-10.x-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
jetty-10.x-scenario-jdk17
The operation was canceled.
|
|
jetty-11.x-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
jetty-11.x-scenario-jdk17
The operation was canceled.
|
|
grizzly-2.3.x-4.x-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
grizzly-2.3.x-4.x-scenario-jdk17
The operation was canceled.
|
|
grizzly-2.3.x-4.x-workthreadpool-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
grizzly-2.3.x-4.x-workthreadpool-scenario-jdk17
The operation was canceled.
|
|
spring-rabbitmq-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
spring-rabbitmq-scenario-jdk17
The operation was canceled.
|
|
jersey-3.x-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
jersey-3.x-scenario-jdk17
The operation was canceled.
|
|
graphql-20plus-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
graphql-20plus-scenario-jdk17
The operation was canceled.
|
|
spring-kafka-3.x-scenario-jdk17
The strategy configuration was canceled because "test.spring-ai-1_x-scenario" failed
|
|
spring-kafka-3.x-scenario-jdk17
The operation was canceled.
|
|
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 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
resttemplate-6.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
jetty-11.x-thread-pool-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
spring-ai-1.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
jdk17-with-gson-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
undertow-2.3.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
jetty-thread-pool-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
jetty-10.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
jetty-11.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
grizzly-2.3.x-4.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
grizzly-2.3.x-4.x-workthreadpool-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
spring-rabbitmq-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
jersey-3.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
graphql-20plus-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
spring-kafka-3.x-scenario-jdk17
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/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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.4 MB |
sha256:fd45c3186622b1e6a3f35b958866ead7fcf1c507c2d731ee21fd682372ce4837
|
|
|
test-plugin-workspace-graphql-20plus-scenario
|
84.7 MB |
sha256:1349708eca90320594ccc3542f64e2d4ee74044250e1ff9261947081c7ca4a4b
|
|
|
test-plugin-workspace-grizzly-2.3.x-4.x-scenario
|
13.1 MB |
sha256:ec1e471f9b0600b8823b9c987dfbcee3d69d7fd54b123f8c989628c52d451667
|
|
|
test-plugin-workspace-grizzly-2.3.x-4.x-workthreadpool-scenario
|
9.86 MB |
sha256:1be4bc12e99bbfd38dee965757ed1bd88a2cb2ba1e97786a0fa288a3e0d886a3
|
|
|
test-plugin-workspace-jdk17-with-gson-scenario
|
79.3 MB |
sha256:74699d8edba0c9b6d5f1db23c419b461aac9afa87c1af97702121364b16485ce
|
|
|
test-plugin-workspace-jersey-3.x-scenario
|
20.4 MB |
sha256:1164e3505fb2a21f5f22be6da2c8b633b2b853781285196c7ffe68c39075b0e1
|
|
|
test-plugin-workspace-jetty-10.x-scenario
|
14.3 MB |
sha256:133b4dcf983872ef215ff31446a62be63ea833827382a0cfe6522ae558eac920
|
|
|
test-plugin-workspace-jetty-11.x-scenario
|
10.4 MB |
sha256:9b3a961f10922f15c6d8f9506dd2c6fb02c4826149255363e6d50954ec5dd9da
|
|
|
test-plugin-workspace-jetty-11.x-thread-pool-scenario
|
4.8 MB |
sha256:d636fc51866a8945d005f74b44a9bcb27ebc0ff5a17a2a31daee25c6ce3d00f2
|
|
|
test-plugin-workspace-jetty-thread-pool-scenario
|
7.31 MB |
sha256:6961251527272990ea9c332670f9a88bcd565024708f640ac87c0c9ce908f5a4
|
|
|
test-plugin-workspace-resttemplate-6.x-scenario
|
33.6 MB |
sha256:e66d0e8e9b559b192fe3c044b9380e0e53a44c0dceff51f83a972ab1969bfe53
|
|
|
test-plugin-workspace-spring-ai-1.x-scenario
|
60.8 MB |
sha256:d6b13d050619c73ed6fd6f5d1149379ce43cc84f194f82e4e7b163e28c8a3cd3
|
|
|
test-plugin-workspace-spring-kafka-3.x-scenario
|
129 MB |
sha256:9b36a648e5535ebd9846d189297b4c84c8768df65adcdb5da665160623d4fcef
|
|
|
test-plugin-workspace-spring-rabbitmq-scenario
|
82.2 MB |
sha256:fd5fd380c9cca757bb2eb2a5512da00fe6ea1fe3a730b536748bf78d514cbc3e
|
|
|
test-plugin-workspace-undertow-2.3.x-scenario
|
8.45 MB |
sha256:6835857de5c9b725ffd68b9c00703e3679c5cf5434d2b8224dd1e0dc201589ce
|
|
|
test-tools
|
643 MB |
sha256:0d17770b1e47b9bd645a3d7dc0e557eaf3fbd5351f116d61b3895802aade5940
|
|