Sunbelt Computer Software

PL/B Language Development and Support

Use subprocess timeout · gitpython-developers/GitPython@1c08f40 · GitHub

Python package

Use subprocess timeout #2352

Sign in to view logs

Triggered via pull request April 22, 2026 21:23

ngie-eign

synchronize #2127

ngie-eign:use-subprocess-timeout

Status Failure

Total duration 8m 39s

Artifacts –

pythonpackage.yml

on: pull_request

Matrix: test

Annotations

19 errors and 6 warnings

test (ubuntu, 3.13)

Process completed with exit code 1.

test (macos, 3.14)

Process completed with exit code 1.

test (ubuntu, 3.12)

Process completed with exit code 1.

test (ubuntu, 3.10)

Process completed with exit code 1.

test (ubuntu, 3.11)

Process completed with exit code 1.

test (ubuntu, 3.14)

Process completed with exit code 1.

test (ubuntu, 3.9)

Process completed with exit code 1.

test (macos, 3.12)

Process completed with exit code 1.

test (macos, 3.13)

Process completed with exit code 1.

test (ubuntu, 3.14t)

Process completed with exit code 1.

test (macos, 3.9)

Process completed with exit code 1.

test (macos, 3.11)

Process completed with exit code 1.

test (windows, 3.10)

Process completed with exit code 1.

test (macos, 3.10)

Process completed with exit code 1.

test (ubuntu, 3.13t)

Process completed with exit code 1.

test (windows, 3.12)

Process completed with exit code 1.

test (windows, 3.11)

Process completed with exit code 1.

test (macos, 3.8)

[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip

test (windows, 3.9)

Process completed with exit code 1.

test (windows, 3.10)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6.0.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/

test (windows, 3.12)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6.0.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/

test (windows, 3.11)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6.0.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/

test (windows, 3.9)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6.0.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/

test (windows, 3.7)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6.0.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/

test (windows, 3.8)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Vampire/setup-wsl@v6.0.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/