Skip to content

fix: Exit with ProtocolViolation if a packet has no frames #2169

fix: Exit with ProtocolViolation if a packet has no frames

fix: Exit with ProtocolViolation if a packet has no frames #2169

Triggered via pull request April 2, 2024 06:48
@larseggertlarseggert
synchronize #1779
fix-1476
Status Failure
Total duration 21m 55s
Artifacts

check.yml

on: pull_request
Matrix: Build & test
Benchmark  /  Benchmark
Benchmark / Benchmark
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Build & test (macos-14, nightly, debug)
Process completed with exit code 1.
Build & test (macos-14, stable, debug)
Process completed with exit code 1.
Build & test (macos-14, 1.74.0, debug)
Process completed with exit code 1.
Build & test (ubuntu-latest, stable, debug)
Process completed with exit code 1.
Build & test (ubuntu-latest, nightly, debug)
Process completed with exit code 1.
Build & test (ubuntu-latest, 1.74.0, debug)
Process completed with exit code 1.
Build & test (ubuntu-latest, stable, release)
Process completed with exit code 1.
Build & test (windows-latest, nightly, debug)
Process completed with exit code 1.
Build & test (windows-latest, stable, debug)
Process completed with exit code 1.
Build & test (windows-latest, 1.74.0, debug)
Process completed with exit code 1.