From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: wanry@yunsilicon.com, robot@bytheb.org
Subject: |FAILURE| pw144181 [PATCH v3 19/19] net/xsc: add dev basic stats ops
Date: Wed, 18 Sep 2024 03:04:31 -0400 [thread overview]
Message-ID: <20240918070431.3439767-1-robot@bytheb.org> (raw)
In-Reply-To: <20240918060936.1231758-20-wanry@yunsilicon.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/144181/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10916735368
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 FAIL 0.67 s (exit status 1)
90/98 DPDK:fast-tests / thash_autotest FAIL 0.67 s (exit status 1)
91/98 DPDK:fast-tests / threads_autotest FAIL 0.67 s (exit status 1)
92/98 DPDK:fast-tests / ticketlock_autotest FAIL 0.67 s (exit status 1)
93/98 DPDK:fast-tests / timer_autotest FAIL 0.67 s (exit status 1)
94/98 DPDK:fast-tests / trace_autotest FAIL 0.67 s (exit status 1)
95/98 DPDK:fast-tests / trace_autotest_with_traces FAIL 0.67 s (exit status 1)
96/98 DPDK:fast-tests / vdev_autotest FAIL 0.67 s (exit status 1)
97/98 DPDK:fast-tests / version_autotest FAIL 0.67 s (exit status 1)
98/98 DPDK:fast-tests / telemetry_all OK 1.22 s
Ok: 1
Expected Fail: 0
Fail: 97
Unexpected Pass: 0
Skipped: 0
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-----------------------------
prev parent reply other threads:[~2024-09-18 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240918060936.1231758-20-wanry@yunsilicon.com>
2024-09-18 5:45 ` |SUCCESS| pw144165-144181 " qemudev
2024-09-18 5:50 ` qemudev
2024-09-18 6:13 ` |WARNING| pw144181 " checkpatch
2024-09-18 7:04 ` 0-day Robot [this message]
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=20240918070431.3439767-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=wanry@yunsilicon.com \
/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).