Skip to content

FEAT: extend profiling to child processes #1256

FEAT: extend profiling to child processes

FEAT: extend profiling to child processes #1256

Triggered via pull request April 15, 2026 03:48
Status Failure
Total duration 5m 17s
Artifacts

tests.yml

on: pull_request
Matrix: build_binpy_wheels
Matrix: test_binpy_wheels
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 7 warnings
lint_job
Process completed with exit code 1.
Build sdist
Process completed with exit code 1.
Build sdist
forced failure
Build sdist
forced failure
windows-latest, arch=auto
Process completed with exit code 1.
windows-latest, arch=auto
cibuildwheel: Command python D:\a\line_profiler\line_profiler/run_tests.py failed with code 1.
windows-latest, arch=auto
called process failed
windows-latest, arch=auto
called process failed
windows-latest, arch=auto
called process failed
macOS-latest, arch=auto
Process completed with exit code 1.
macOS-latest, arch=auto
cibuildwheel: Command ['/usr/bin/arch', '-x86_64', '/bin/sh', '-c', 'python /Users/runner/work/line_profiler/line_profiler/run_tests.py'] failed with code 1.
macOS-latest, arch=auto
forced failure
ubuntu-24.04-arm, arch=auto
Process completed with exit code 1.
ubuntu-24.04-arm, arch=auto
cibuildwheel: Command ['sh', '-c', 'python /project/run_tests.py'] failed with code 1.
ubuntu-24.04-arm, arch=auto
forced failure
ubuntu-24.04-arm, arch=auto
forced failure
ubuntu-latest, arch=auto
Process completed with exit code 1.
ubuntu-latest, arch=auto
cibuildwheel: Command ['sh', '-c', 'python /project/run_tests.py'] failed with code 1.
ubuntu-latest, arch=auto
forced failure
ubuntu-latest, arch=auto
forced failure
Workflow syntax warning: .github/workflows/tests.yml#L143
.github/workflows/tests.yml (Line: 143, Col: 11): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
lint_job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.6.0. 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/
Build sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.6.0. 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/
windows-latest, arch=auto
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
macOS-latest, arch=auto
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
ubuntu-24.04-arm, arch=auto
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
ubuntu-latest, arch=auto
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/