add regression tests for GIL ordering bug (v2) #209
Annotations
32 errors and 9 warnings
|
Build (1.24.x, ubuntu-latest)
Process completed with exit code 2.
|
|
Build (1.24.x, ubuntu-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.24.x, ubuntu-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.25.x, ubuntu-latest)
Process completed with exit code 2.
|
|
Build (1.25.x, ubuntu-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.25.x, ubuntu-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.22.x, ubuntu-latest)
Process completed with exit code 2.
|
|
Build (1.22.x, ubuntu-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.22.x, ubuntu-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.21.x, ubuntu-latest)
Process completed with exit code 2.
|
|
Build (1.21.x, ubuntu-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.21.x, ubuntu-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.25.x, windows-latest)
Process completed with exit code 1.
|
|
Build (1.25.x, windows-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.25.x, windows-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.22.x, windows-latest)
Process completed with exit code 1.
|
|
Build (1.22.x, windows-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.22.x, windows-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.21.x, windows-latest)
Process completed with exit code 1.
|
|
Build (1.21.x, windows-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.21.x, windows-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.24.x, windows-latest)
Process completed with exit code 1.
|
|
Build (1.24.x, windows-latest):
main_test.go#L770
undefined: runtime
|
|
Build (1.24.x, windows-latest):
main_test.go#L770
t.SkipIf undefined (type *testing.T has no field or method SkipIf)
|
|
Build (1.22.x, macos-13-xlarge)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.24.x, macos-13)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.24.x, macos-13-xlarge)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.25.x, macos-13-xlarge)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.25.x, macos-13)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.21.x, macos-13)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.22.x, macos-13)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.21.x, macos-13-xlarge)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build (1.24.x, ubuntu-latest)
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-go@v5, actions/setup-python@v5. 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 (1.25.x, ubuntu-latest)
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-go@v5, actions/setup-python@v5. 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 (1.22.x, ubuntu-latest)
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-go@v5, actions/setup-python@v5. 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 (1.21.x, ubuntu-latest)
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-go@v5, actions/setup-python@v5. 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 (1.21.x, ubuntu-latest)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
Build (1.25.x, windows-latest)
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-go@v5, actions/setup-python@v5. 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 (1.22.x, windows-latest)
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-go@v5, actions/setup-python@v5. 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 (1.21.x, windows-latest)
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-go@v5, actions/setup-python@v5. 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 (1.24.x, windows-latest)
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-go@v5, actions/setup-python@v5. 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/
|