From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: andremue@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw150208 [PATCH v15 3/3] drivers/net: add diagnostics macros to make code portable
Date: Sat, 18 Jan 2025 17:50:06 -0500 [thread overview]
Message-ID: <20250118225006.631508-1-robot@bytheb.org> (raw)
In-Reply-To: <1737237314-9844-4-git-send-email-andremue@linux.microsoft.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/150208/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/12847799610
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.47s
98/104 DPDK:fast-tests / ticketlock_autotest OK 0.38s
99/104 DPDK:fast-tests / timer_autotest OK 2.85s
100/104 DPDK:fast-tests / trace_autotest OK 0.36s
101/104 DPDK:fast-tests / trace_autotest_with_traces OK 0.36s
102/104 DPDK:fast-tests / vdev_autotest OK 0.34s
103/104 DPDK:fast-tests / version_autotest OK 0.34s
104/104 DPDK:fast-tests / telemetry_all OK 1.11s
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-01-18 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1737237314-9844-4-git-send-email-andremue@linux.microsoft.com>
2025-01-18 21:35 ` |SUCCESS| pw150207-150208 " qemudev
2025-01-18 21:40 ` qemudev
2025-01-18 21:55 ` |SUCCESS| pw150208 " checkpatch
2025-01-18 22:36 ` |SUCCESS| pw150207-150208 [PATCH] [v15,3/3] drivers/net: add diagnos dpdklab
2025-01-18 22:37 ` dpdklab
2025-01-18 22:41 ` |PENDING| " dpdklab
2025-01-18 22:43 ` dpdklab
2025-01-18 22:46 ` dpdklab
2025-01-18 22:49 ` |SUCCESS| " dpdklab
2025-01-18 22:50 ` 0-day Robot [this message]
2025-01-18 22:54 ` |PENDING| " dpdklab
2025-01-18 22:54 ` |SUCCESS| " dpdklab
2025-01-18 22:54 ` dpdklab
2025-01-18 22:59 ` |PENDING| " dpdklab
2025-01-18 23:07 ` dpdklab
2025-01-18 23:08 ` |SUCCESS| " dpdklab
2025-01-18 23:33 ` dpdklab
2025-01-18 23:46 ` dpdklab
2025-01-18 23:49 ` dpdklab
2025-01-19 0:05 ` |WARNING| " dpdklab
2025-01-19 3:52 ` |SUCCESS| " 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=20250118225006.631508-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=andremue@linux.microsoft.com \
--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).