Skip to content

fix: Introduce _get_current_streamed_span() to keep types backwards compatible #7902

fix: Introduce _get_current_streamed_span() to keep types backwards compatible

fix: Introduce _get_current_streamed_span() to keep types backwards compatible #7902

Triggered via pull request April 30, 2026 11:35
Status Failure
Total duration 2m 5s
Artifacts

test-integrations-flags.yml

on: pull_request
Matrix: Flags
All Flags tests passed
2s
All Flags tests passed
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 42 warnings
Flags (3.10, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.10, ubuntu-22.04)
Process completed with exit code 4.
Flags (3.8, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.8, ubuntu-22.04)
Process completed with exit code 4.
Flags (3.12, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.12, ubuntu-22.04)
Process completed with exit code 4.
Flags (3.14, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.14, ubuntu-22.04)
Process completed with exit code 4.
Flags (3.13, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.13, ubuntu-22.04)
Process completed with exit code 255.
Flags (3.7, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.7, ubuntu-22.04)
Process completed with exit code 255.
Flags (3.14t, ubuntu-22.04)
Process completed with exit code 1.
Flags (3.14t, ubuntu-22.04)
Process completed with exit code 4.
All Flags tests passed
Process completed with exit code 1.
Flags (3.10, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.10, ubuntu-22.04)
No valid coverage files found
Flags (3.10, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.10, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.10, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.10, ubuntu-22.04)
No files found matching pattern: .junitxml
Flags (3.8, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.8, ubuntu-22.04)
No valid coverage files found
Flags (3.8, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.8, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.8, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.8, ubuntu-22.04)
No files found matching pattern: .junitxml
Flags (3.12, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.12, ubuntu-22.04)
No valid coverage files found
Flags (3.12, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.12, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.12, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.12, ubuntu-22.04)
No files found matching pattern: .junitxml
Flags (3.14, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.14, ubuntu-22.04)
No valid coverage files found
Flags (3.14, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.14, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.14, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.14, ubuntu-22.04)
No files found matching pattern: .junitxml
Flags (3.13, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.13, ubuntu-22.04)
No valid coverage files found
Flags (3.13, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.13, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.13, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.13, ubuntu-22.04)
No files found matching pattern: .junitxml
Flags (3.7, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.7, ubuntu-22.04)
No valid coverage files found
Flags (3.7, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.7, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.7, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.7, ubuntu-22.04)
No files found matching pattern: .junitxml
Flags (3.14t, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: getsentry/codecov-action@fda17cfc37e16a0cc23f61685813390bfee7daf3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Flags (3.14t, ubuntu-22.04)
No valid coverage files found
Flags (3.14t, ubuntu-22.04)
File not readable or does not exist: coverage.xml
Flags (3.14t, ubuntu-22.04)
Please ensure your test framework is generating JUnit XML output.
Flags (3.14t, ubuntu-22.04)
No JUnit XML files found matching pattern: .junitxml
Flags (3.14t, ubuntu-22.04)
No files found matching pattern: .junitxml