Skip to content
Container

Feat: ban IPs not sending a valid connection ID #1504

Sign in to view logs

Feat: ban IPs not sending a valid connection ID

Feat: ban IPs not sending a valid connection ID #1504

Triggered via pull request December 10, 2024 10:15
@josecelanojosecelano
synchronize #1124
josecelano:1096-ban-socket-addresses-not-sending-a-valid-connection-id
Status Failure
Total duration 9m 14s
Artifacts 1

container.yaml

on: pull_request
Matrix: Test (Docker)
Context
0s
Context
Publish (Development)
0s
Publish (Development)
Publish (Release)
0s
Publish (Release)
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Test (Docker) (debug)
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cargo nextest run --workspace-remap /test/src/ --target-dir-remap /test/src/target/ --cargo-metadata /test/src/target/nextest/cargo-metadata.json --binaries-metadata /test/src/target/nextest/binaries-metadata.json" did not complete successfully: exit code: 100
Test (Docker) (release)
The job was canceled because "debug" failed.
Test (Docker) (release)
The operation was canceled.
Test (Docker) (debug)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
torrust~torrust-tracker~LH5BLC.dockerbuild
73.4 KB