Skip to content
bpf-ci

Introduce GRO support to cpumap codebase #42050

Sign in to view logs

Introduce GRO support to cpumap codebase

Introduce GRO support to cpumap codebase #42050

Triggered via pull request November 29, 2024 23:18
@kernel-patches-daemon-bpfkernel-patches-daemon-bpf[bot]
opened #8149
series/890634=>bpf-next
Status Failure
Total duration 23h 52m 19s
Artifacts 9

test.yml

on: pull_request
set-matrix
1s
set-matrix
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 11 notices
s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
The operation was canceled.
s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
RPC failed; curl 55 Send failure: Broken pipe
s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
4081 bytes of body are still expected
s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
early EOF
s390x-gcc / test (test_verifier, false, 360) / test_verifier on s390x with gcc
fetch-pack: invalid index-pack output
s390x-gcc / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on s390x with gcc
The operation was canceled.
s390x-gcc / test (test_progs, false, 360) / test_progs on s390x with gcc
The self-hosted runner: bpf-ci-runner-s390x-05-worker-00 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
x86_64-gcc / test (test_progs_parallel, true, 30) / test_progs_parallel on x86_64 with gcc
Success: 578/4268, Skipped: 70, Failed: 0
x86_64-gcc / test (test_progs_no_alu32_parallel, true, 30) / test_progs_no_alu32_parallel on x86_64 with gcc
Success: 578/4261, Skipped: 72, Failed: 0
x86_64-llvm-17 / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on x86_64 with llvm-17
Success: 578/4268, Skipped: 64, Failed: 0
x86_64-gcc / test (test_progs, false, 360) / test_progs on x86_64 with gcc
Success: 578/4268, Skipped: 70, Failed: 0
x86_64-gcc / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on x86_64 with gcc
Success: 578/4261, Skipped: 71, Failed: 0
x86_64-llvm-18 / test (test_progs, false, 360) / test_progs on x86_64 with llvm-18
Success: 578/4472, Skipped: 60, Failed: 0
x86_64-llvm-18 / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on x86_64 with llvm-18
Success: 578/4465, Skipped: 62, Failed: 0
x86_64-llvm-17 / test (test_progs, false, 360) / test_progs on x86_64 with llvm-17
Success: 578/4275, Skipped: 63, Failed: 0
x86_64-llvm-18 / test (test_progs_cpuv4, false, 360) / test_progs_cpuv4 on x86_64 with llvm-18
Success: 578/4472, Skipped: 60, Failed: 0
aarch64-gcc / test (test_progs, false, 360) / test_progs on aarch64 with gcc
Success: 575/4129, Skipped: 90, Failed: 0
aarch64-gcc / test (test_progs_no_alu32, false, 360) / test_progs_no_alu32 on aarch64 with gcc
Success: 575/4122, Skipped: 91, Failed: 0

Artifacts

Produced during runtime
Name Size
vmlinux-aarch64-gcc
103 MB
vmlinux-s390x-gcc
85.4 MB
vmlinux-x86_64-gcc
103 MB
vmlinux-x86_64-llvm-17
101 MB
vmlinux-x86_64-llvm-17-release
105 MB
vmlinux-x86_64-llvm-18
136 MB
vmlinux-x86_64-llvm-18-release
141 MB
x86_64-gcc-baseline-veristat-kernel
26.1 KB
x86_64-gcc-baseline-veristat-meta
11.9 KB