Skip to content
PR

Use NIO scheduleCallback API for connection handler timers #21

Sign in to view logs

Use NIO scheduleCallback API for connection handler timers

Use NIO scheduleCallback API for connection handler timers #21

Triggered via pull request November 12, 2024 08:11
@simonjbeaumontsimonjbeaumont
synchronize #28
simonjbeaumont:sb/update-timers-to-use-scheduled-callbacks
Status Failure
Total duration 7m 8s
Artifacts –

pull_request.yml

on: pull_request
Soundness  /  API breakage check
3m 30s
Soundness / API breakage check
Soundness  /  Documentation check
2m 41s
Soundness / Documentation check
Soundness  /  Unacceptable language check
7s
Soundness / Unacceptable language check
Soundness  /  License headers check
4s
Soundness / License headers check
Soundness  /  Broken symlinks check
4s
Soundness / Broken symlinks check
Soundness  /  Format check
34s
Soundness / Format check
Soundness  /  Shell check
33s
Soundness / Shell check
Soundness  /  YAML lint check
5s
Soundness / YAML lint check
Soundness  /  Python lint check
4s
Soundness / Python lint check
Soundness  /  Swift license headers check
8s
Soundness / Swift license headers check
Matrix: Cxx Interop / Cxx interop / linux
Matrix: Cxx Interop / Cxx interop / windows-nightly
Matrix: Cxx Interop / Cxx interop / windows
Matrix: Integration Tests / linux
Matrix: Integration Tests / windows-nightly
Matrix: Integration Tests / windows
Matrix: Unit Tests / Unit tests / linux
Matrix: Unit Tests / Unit tests / windows-nightly
Matrix: Unit Tests / Unit tests / windows
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Cxx Interop / Cxx interop / Linux (nightly-main)
Process completed with exit code 1.
Integration Tests / Linux (nightly-main)
Process completed with exit code 1.
Unit Tests / Unit tests / Linux (nightly-main)
Process completed with exit code 1.