From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw151521 [PATCH v7 16/16] devtools/cocci: add script to find problematic memset
Date: Sat, 15 Feb 2025 15:25:01 -0500 [thread overview]
Message-ID: <20250215202501.3867241-1-robot@bytheb.org> (raw)
In-Reply-To: <20250215190544.988310-17-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/151521/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13348000041
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
96/104 DPDK:fast-tests / thash_autotest OK 0.36s
97/104 DPDK:fast-tests / threads_autotest OK 0.48s
98/104 DPDK:fast-tests / ticketlock_autotest OK 0.38s
99/104 DPDK:fast-tests / timer_autotest OK 2.86s
100/104 DPDK:fast-tests / trace_autotest OK 0.35s
101/104 DPDK:fast-tests / trace_autotest_with_traces OK 0.35s
102/104 DPDK:fast-tests / vdev_autotest OK 0.34s
103/104 DPDK:fast-tests / version_autotest OK 0.35s
104/104 DPDK:fast-tests / telemetry_all OK 1.12s
Ok: 97
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-02-15 20:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250215190544.988310-17-stephen@networkplumber.org>
2025-02-15 18:47 ` |SUCCESS| pw151506-151521 " qemudev
2025-02-15 18:52 ` qemudev
2025-02-15 19:09 ` |SUCCESS| pw151521 " checkpatch
2025-02-15 19:57 ` |SUCCESS| pw151506-151521 [PATCH] [v7,16/16] devtools/cocci: add scr dpdklab
2025-02-15 19:59 ` dpdklab
2025-02-15 20:00 ` |PENDING| " dpdklab
2025-02-15 20:06 ` dpdklab
2025-02-15 20:09 ` dpdklab
2025-02-15 20:10 ` |SUCCESS| " dpdklab
2025-02-15 20:10 ` |PENDING| " dpdklab
2025-02-15 20:10 ` |SUCCESS| " dpdklab
2025-02-15 20:25 ` 0-day Robot [this message]
2025-02-15 20:33 ` dpdklab
2025-02-15 20:34 ` dpdklab
2025-02-15 21:00 ` dpdklab
2025-02-15 21:12 ` dpdklab
2025-02-15 21:34 ` dpdklab
2025-02-18 21:17 ` dpdklab
2025-02-18 21:31 ` dpdklab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250215202501.3867241-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=stephen@networkplumber.org \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).