Skip to content

Addressed race conditions and flaky tests in QUIC transport #177

Addressed race conditions and flaky tests in QUIC transport

Addressed race conditions and flaky tests in QUIC transport #177

Triggered via pull request April 21, 2026 14:33
@LaurentRDCLaurentRDC
synchronize #485
quic-race
Status Failure
Total duration 15m 53s
Artifacts

cabal.yml

on: pull_request
Matrix: continuous-integration
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 89 warnings
continuous-integration (9.14.1)
Process completed with exit code 1.
continuous-integration (9.6.7)
Process completed with exit code 1.
continuous-integration (9.4.8)
Process completed with exit code 1.
continuous-integration (9.0.2)
Process completed with exit code 1.
continuous-integration (8.10.7)
Process completed with exit code 1.
continuous-integration (9.14.1)
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/
continuous-integration (9.6.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.6.7)
The import of ‘guard’ from module ‘Control.Monad’ is redundant
continuous-integration (9.6.7)
This binding for ‘err’ shadows the existing binding
continuous-integration (9.6.7)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.6.7)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.6.7)
This binding for ‘sockAddr’ shadows the existing binding
continuous-integration (9.6.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.6.7)
Pattern match(es) are non-exhaustive
continuous-integration (9.6.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.6.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.6.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.4.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.4.8)
The import of ‘guard’ from module ‘Control.Monad’ is redundant
continuous-integration (9.4.8)
Pattern match(es) are non-exhaustive
continuous-integration (9.4.8)
This binding for ‘err’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘sockAddr’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.4.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.2.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.2.8)
Pattern match(es) are non-exhaustive
continuous-integration (9.2.8)
This binding for ‘err’ shadows the existing binding
continuous-integration (9.2.8)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.2.8)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.2.8)
This binding for ‘sockAddr’ shadows the existing binding
continuous-integration (9.2.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.2.8)
• Ignoring unusable UNPACK pragma
continuous-integration (9.2.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.2.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.2.8)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.10.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.10.3)
Pattern match(es) are non-exhaustive
continuous-integration (9.10.3)
In the use of ‘head’
continuous-integration (9.10.3)
In the use of ‘tail’
continuous-integration (9.10.3)
In the use of ‘head’
continuous-integration (9.10.3)
In the use of ‘tail’
continuous-integration (9.10.3)
In the use of ‘head’
continuous-integration (9.10.3)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.10.3)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.10.3)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.10.3)
The import of ‘Data.List’ is redundant
continuous-integration (9.8.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.8.4)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.8.4)
Pattern match(es) are non-exhaustive
continuous-integration (9.8.4)
In the use of ‘head’
continuous-integration (9.8.4)
In the use of ‘tail’
continuous-integration (9.8.4)
In the use of ‘head’
continuous-integration (9.8.4)
In the use of ‘tail’
continuous-integration (9.8.4)
In the use of ‘head’
continuous-integration (9.8.4)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.8.4)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.8.4)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.12.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.12.2)
• Deriving ‘Typeable’ has no effect: all types now auto-derive Typeable
continuous-integration (9.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (9.0.2)
The import of ‘guard’ from module ‘Control.Monad’ is redundant
continuous-integration (9.0.2)
Pattern match(es) are non-exhaustive
continuous-integration (9.0.2)
This binding for ‘err’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘act’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘sockAddr’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘sock’ shadows the existing binding
continuous-integration (9.0.2)
This binding for ‘sock’ shadows the existing binding
continuous-integration (8.10.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
continuous-integration (8.10.7)
• Ignoring unusable UNPACK pragma
continuous-integration (8.10.7)
Pattern match(es) are non-exhaustive
continuous-integration (8.10.7)
This binding for ‘err’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘act’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘act’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘sockAddr’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘sock’ shadows the existing binding
continuous-integration (8.10.7)
This binding for ‘sock’ shadows the existing binding