Use decision score instead of probability #631
build-deploy-wheels.yml
on: push
Matrix: build_wheels
build_sdist
1m 7s
docs_version
3s
check_tag
0s
list_artifacts
0s
upload_pypi
0s
Annotations
24 errors and 13 warnings
|
build_wheels (macos-latest, cp311)
Process completed with exit code 1.
|
|
build_wheels (macos-latest, cp311)
cibuildwheel: Command ['/usr/bin/arch', '-x86_64', '/bin/sh', '-c', 'python -m pytest /Users/runner/work/wildboar/wildboar/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (macos-latest, cp312)
Process completed with exit code 1.
|
|
build_wheels (macos-latest, cp312)
cibuildwheel: Command ['/usr/bin/arch', '-x86_64', '/bin/sh', '-c', 'python -m pytest /Users/runner/work/wildboar/wildboar/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (macos-latest, cp314)
Process completed with exit code 1.
|
|
build_wheels (macos-latest, cp314)
cibuildwheel: Command ['/usr/bin/arch', '-x86_64', '/bin/sh', '-c', 'python -m pytest /Users/runner/work/wildboar/wildboar/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (windows-latest, cp311)
Process completed with exit code 1.
|
|
build_wheels (windows-latest, cp311)
cibuildwheel: Command python -m pytest D:\a\wildboar\wildboar/tests --benchmark-skip failed with code 1.
|
|
build_wheels (windows-latest, cp313)
Process completed with exit code 1.
|
|
build_wheels (windows-latest, cp313)
cibuildwheel: Command python -m pytest D:\a\wildboar\wildboar/tests --benchmark-skip failed with code 1.
|
|
build_wheels (windows-latest, cp312)
Process completed with exit code 1.
|
|
build_wheels (windows-latest, cp312)
cibuildwheel: Command python -m pytest D:\a\wildboar\wildboar/tests --benchmark-skip failed with code 1.
|
|
build_wheels (ubuntu-latest, cp311)
Process completed with exit code 1.
|
|
build_wheels (ubuntu-latest, cp311)
cibuildwheel: Command ['sh', '-c', 'python -m pytest /project/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (ubuntu-latest, cp312)
Process completed with exit code 1.
|
|
build_wheels (ubuntu-latest, cp312)
cibuildwheel: Command ['sh', '-c', 'python -m pytest /project/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (macos-latest, cp313)
Process completed with exit code 1.
|
|
build_wheels (macos-latest, cp313)
cibuildwheel: Command ['/usr/bin/arch', '-x86_64', '/bin/sh', '-c', 'python -m pytest /Users/runner/work/wildboar/wildboar/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (windows-latest, cp314)
Process completed with exit code 1.
|
|
build_wheels (windows-latest, cp314)
cibuildwheel: Command python -m pytest D:\a\wildboar\wildboar/tests --benchmark-skip failed with code 1.
|
|
build_wheels (ubuntu-latest, cp314)
Process completed with exit code 1.
|
|
build_wheels (ubuntu-latest, cp314)
cibuildwheel: Command ['sh', '-c', 'python -m pytest /project/tests --benchmark-skip'] failed with code 1.
|
|
build_wheels (ubuntu-latest, cp313)
Process completed with exit code 1.
|
|
build_wheels (ubuntu-latest, cp313)
cibuildwheel: Command ['sh', '-c', 'python -m pytest /project/tests --benchmark-skip'] failed with code 1.
|
|
build_sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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_wheels (macos-latest, cp311)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (macos-latest, cp312)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (macos-latest, cp314)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (windows-latest, cp311)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (windows-latest, cp313)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (windows-latest, cp312)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (ubuntu-latest, cp311)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (ubuntu-latest, cp312)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (macos-latest, cp313)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (windows-latest, cp314)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (ubuntu-latest, cp314)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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_wheels (ubuntu-latest, cp313)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
wildboar-sdist
|
3.99 MB |
sha256:5331a83ae635ef52f2132a4801d99f9c49a478ac3a2854ae2fa1794528e37c79
|
|