From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: npratte@iol.unh.edu, robot@bytheb.org
Subject: |FAILURE| pw140911 [PATCH v1] dts: Testbed And Node Configuration Split
Date: Mon, 10 Jun 2024 16:24:08 -0400 [thread overview]
Message-ID: <20240610202408.2488443-1-robot@bytheb.org> (raw)
In-Reply-To: <20240610193410.17968-2-npratte@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/140911/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9454617768
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
####################################################################################
88/97 DPDK:fast-tests / telemetry_json_autotest OK 0.37 s
89/97 DPDK:fast-tests / thash_autotest OK 0.37 s
90/97 DPDK:fast-tests / threads_autotest OK 0.47 s
91/97 DPDK:fast-tests / ticketlock_autotest OK 0.42 s
92/97 DPDK:fast-tests / timer_autotest OK 2.87 s
93/97 DPDK:fast-tests / trace_autotest OK 0.37 s
94/97 DPDK:fast-tests / trace_autotest_with_traces OK 0.37 s
95/97 DPDK:fast-tests / vdev_autotest OK 0.37 s
96/97 DPDK:fast-tests / version_autotest OK 0.37 s
97/97 DPDK:fast-tests / telemetry_all OK 1.12 s
Ok: 90
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:[~2024-06-10 20:24 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240610193410.17968-2-npratte@iol.unh.edu>
2024-06-10 19:07 ` |SUCCESS| " qemudev
2024-06-10 19:11 ` qemudev
2024-06-10 19:35 ` checkpatch
2024-06-10 20:24 ` 0-day Robot [this message]
2024-06-10 23:38 ` |SUCCESS| pw140911 [PATCH] [v1] dts: Testbed And Node Configuration dpdklab
2024-06-10 23:39 ` dpdklab
2024-06-10 23:54 ` dpdklab
2024-06-11 0:02 ` dpdklab
2024-06-11 0:16 ` dpdklab
2024-06-11 1:16 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:17 ` dpdklab
2024-06-12 23:17 ` dpdklab
2024-06-12 23:17 ` dpdklab
2024-06-12 23:18 ` dpdklab
2024-06-12 23:19 ` dpdklab
2024-06-12 23:19 ` dpdklab
2024-06-12 23:19 ` dpdklab
2024-06-12 23:20 ` dpdklab
2024-06-12 23:21 ` dpdklab
2024-06-12 23:22 ` dpdklab
2024-06-12 23:24 ` dpdklab
2024-06-12 23:26 ` dpdklab
2024-06-12 23:26 ` dpdklab
2024-06-12 23:27 ` dpdklab
2024-06-12 23:28 ` dpdklab
2024-06-12 23:29 ` dpdklab
2024-06-12 23:29 ` dpdklab
2024-06-12 23:30 ` dpdklab
2024-06-12 23:31 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:34 ` dpdklab
2024-06-12 23:34 ` dpdklab
2024-06-12 23:35 ` dpdklab
2024-06-12 23:37 ` 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=20240610202408.2488443-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=npratte@iol.unh.edu \
--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).