From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: luca.vizzarro@arm.com, robot@bytheb.org
Subject: |FAILURE| pw143814 [PATCH v3 5/5] dts: add testpmd set ports queues
Date: Mon, 9 Sep 2024 08:05:10 -0400 [thread overview]
Message-ID: <20240909120510.1721218-1-robot@bytheb.org> (raw)
In-Reply-To: <20240909110158.1009592-6-luca.vizzarro@arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/143814/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10772236001
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
####################################################################################
89/98 DPDK:fast-tests / telemetry_json_autotest OK 0.37 s
90/98 DPDK:fast-tests / thash_autotest OK 0.37 s
91/98 DPDK:fast-tests / threads_autotest OK 0.47 s
92/98 DPDK:fast-tests / ticketlock_autotest OK 0.42 s
93/98 DPDK:fast-tests / timer_autotest OK 2.87 s
94/98 DPDK:fast-tests / trace_autotest OK 0.37 s
95/98 DPDK:fast-tests / trace_autotest_with_traces OK 0.37 s
96/98 DPDK:fast-tests / vdev_autotest OK 0.37 s
97/98 DPDK:fast-tests / version_autotest OK 0.37 s
98/98 DPDK:fast-tests / telemetry_all OK 1.12 s
Ok: 91
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-09-09 12:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240909110158.1009592-6-luca.vizzarro@arm.com>
2024-09-09 10:49 ` |SUCCESS| pw143810-143814 " qemudev
2024-09-09 10:53 ` qemudev
2024-09-09 11:05 ` |SUCCESS| pw143814 " checkpatch
2024-09-09 12:05 ` 0-day Robot [this message]
2024-09-09 16:27 ` |SUCCESS| pw143810-143814 [PATCH] [v3,5/5] dts: add testpmd set port dpdklab
2024-09-09 16:30 ` dpdklab
2024-09-09 16:41 ` dpdklab
2024-09-09 16:43 ` |PENDING| " dpdklab
2024-09-09 16:55 ` |SUCCESS| " dpdklab
2024-09-09 17:05 ` |PENDING| " dpdklab
2024-09-09 17:05 ` |SUCCESS| " dpdklab
2024-09-09 17:09 ` dpdklab
2024-09-09 17:17 ` |PENDING| " dpdklab
2024-09-09 17:39 ` dpdklab
2024-09-09 19:07 ` |SUCCESS| " dpdklab
2024-09-09 19:22 ` dpdklab
2024-09-09 19:23 ` dpdklab
2024-09-09 19:36 ` dpdklab
2024-09-09 19:42 ` dpdklab
2024-09-09 20:51 ` dpdklab
2024-09-09 20:56 ` dpdklab
2024-09-09 21:00 ` dpdklab
2024-09-09 21:04 ` dpdklab
2024-09-09 21:21 ` dpdklab
2024-09-09 21:25 ` dpdklab
2024-09-09 23:29 ` dpdklab
2024-09-16 9:52 ` dpdklab
2024-09-16 18:44 ` 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=20240909120510.1721218-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=luca.vizzarro@arm.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).