[PATCH v8] fix issues reported by GCC address sanitizer #3050
FanHong674ci-pipeline-arm64.yml
on: pull_request
Build_out-of-tree
2m 6s
Run_sched_config
11m 0s
Run_stash_config
11m 5s
Run_scheduler_sp
11m 53s
Run_scheduler_scalable
11m 13s
Run_process_mode
10m 27s
Run_inline_timer
6m 25s
Run_packet_align
3m 35s
Run_dpdk-19_11
11m 21s
Run_dpdk-20_11
11m 42s
Run_dpdk-21_11
11m 9s
Matrix: Build
Matrix: Build_gcc_u22
Matrix: Build_OS
Matrix: Build_static_u22
Matrix: Build_XDP
Matrix: Run
Matrix: Run_CFLAGS
Matrix: Run_distcheck
Matrix: Run_OS
Annotations
6 errors
|
Build (gcc, --enable-lto --enable-abi-compat)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Build (gcc, --enable-lto --enable-abi-compat)
The operation was canceled.
|
|
Build_static_u22 (11, --enable-lto)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Build_static_u22 (11, --enable-lto)
The operation was canceled.
|
|
Run (clang, --with-crypto=ipsecmb)
The self-hosted runner: i-071ab16724e1576ac 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.
|
|
Run (clang, --without-openssl --without-pcap)
The self-hosted runner: i-058d804fcfa3fcb0f 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.
|