+ BPF ML On Thu, Sep 12, 2024 at 8:35 AM <bot+bpf-ci@xxxxxxxxxx> wrote: > > Dear patch submitter, > > CI has tested the following submission: > Status: FAILURE > Name: [v14,00/19] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph > Patchwork: https://patchwork.kernel.org/project/netdevbpf/list/?series=889822&state=* > Matrix: https://github.com/kernel-patches/bpf/actions/runs/10833792984 > > Failed jobs: > test_progs-aarch64-gcc: https://github.com/kernel-patches/bpf/actions/runs/10833792984/job/30061791397 > test_progs_no_alu32-aarch64-gcc: https://github.com/kernel-patches/bpf/actions/runs/10833792984/job/30061791836 > test_progs-s390x-gcc: https://github.com/kernel-patches/bpf/actions/runs/10833792984/job/30061757062 > test_progs_no_alu32-s390x-gcc: https://github.com/kernel-patches/bpf/actions/runs/10833792984/job/30061757809 > > First test_progs failure (test_progs-aarch64-gcc): > #132 kprobe_multi_testmod_test > serial_test_kprobe_multi_testmod_test:PASS:load_kallsyms_local 0 nsec > #132/1 kprobe_multi_testmod_test/testmod_attach_api_syms > test_testmod_attach_api:PASS:fentry_raw_skel_load 0 nsec > trigger_module_test_read:PASS:testmod_file_open 0 nsec > test_testmod_attach_api:PASS:trigger_read 0 nsec > kprobe_multi_testmod_check:FAIL:kprobe_test1_result unexpected kprobe_test1_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kprobe_test2_result unexpected kprobe_test2_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kprobe_test3_result unexpected kprobe_test3_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kretprobe_test1_result unexpected kretprobe_test1_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kretprobe_test2_result unexpected kretprobe_test2_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kretprobe_test3_result unexpected kretprobe_test3_result: actual 0 != expected 1 > #132/2 kprobe_multi_testmod_test/testmod_attach_api_addrs > test_testmod_attach_api_addrs:PASS:ksym_get_addr_local 0 nsec > test_testmod_attach_api_addrs:PASS:ksym_get_addr_local 0 nsec > test_testmod_attach_api_addrs:PASS:ksym_get_addr_local 0 nsec > test_testmod_attach_api:PASS:fentry_raw_skel_load 0 nsec > trigger_module_test_read:PASS:testmod_file_open 0 nsec > test_testmod_attach_api:PASS:trigger_read 0 nsec > kprobe_multi_testmod_check:FAIL:kprobe_test1_result unexpected kprobe_test1_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kprobe_test2_result unexpected kprobe_test2_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kprobe_test3_result unexpected kprobe_test3_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kretprobe_test1_result unexpected kretprobe_test1_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kretprobe_test2_result unexpected kretprobe_test2_result: actual 0 != expected 1 > kprobe_multi_testmod_check:FAIL:kretprobe_test3_result unexpected kretprobe_test3_result: actual 0 != expected 1 > Seems like this selftest is still broken. Please let me know if you need help with building and running BPF selftests to reproduce this locally. > > Please note: this email is coming from an unmonitored mailbox. If you have > questions or feedback, please reach out to the Meta Kernel CI team at > kernel-ci@xxxxxxxx.
