From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: jingjing.wu@intel.com, robot@bytheb.org
Subject: |FAILURE| pw138477 [PATCH] graph: fix head move when graph walk in mcore dispatch
Date: Tue, 19 Mar 2024 03:23:33 -0400 [thread overview]
Message-ID: <20240319072333.1423929-1-robot@bytheb.org> (raw)
In-Reply-To: <20240319141454.3275543-1-jingjing.wu@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/138477/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8338693069
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
"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-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
102/111 DPDK:fast-tests / telemetry_json_autotest OK 0.27 s
103/111 DPDK:fast-tests / thash_autotest OK 0.27 s
104/111 DPDK:fast-tests / threads_autotest OK 0.37 s
105/111 DPDK:fast-tests / ticketlock_autotest OK 0.27 s
106/111 DPDK:fast-tests / timer_autotest OK 2.87 s
107/111 DPDK:fast-tests / trace_autotest OK 0.27 s
108/111 DPDK:fast-tests / trace_autotest_with_traces OK 0.27 s
109/111 DPDK:fast-tests / vdev_autotest OK 0.27 s
110/111 DPDK:fast-tests / version_autotest OK 0.27 s
111/111 DPDK:fast-tests / telemetry_all OK 1.12 s
Ok: 104
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 6
Timeout: 1
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-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
####################################################################################
#### [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: 0
Unexpected Pass: 0
Skipped: 6
Timeout: 1
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-03-19 7:23 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240319141454.3275543-1-jingjing.wu@intel.com>
2024-03-19 5:59 ` |SUCCESS| " qemudev
2024-03-19 6:05 ` |FAILURE| " qemudev
2024-03-19 6:23 ` |SUCCESS| " checkpatch
2024-03-19 7:10 ` |SUCCESS| pw138477 [PATCH] graph: fix head move when graph walk in m dpdklab
2024-03-19 7:10 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:17 ` dpdklab
2024-03-19 7:18 ` dpdklab
2024-03-19 7:19 ` |FAILURE| " dpdklab
2024-03-19 7:20 ` |SUCCESS| " dpdklab
2024-03-19 7:20 ` |FAILURE| " dpdklab
2024-03-19 7:20 ` |SUCCESS| " dpdklab
2024-03-19 7:22 ` dpdklab
2024-03-19 7:22 ` dpdklab
2024-03-19 7:23 ` dpdklab
2024-03-19 7:23 ` |FAILURE| " dpdklab
2024-03-19 7:23 ` 0-day Robot [this message]
2024-03-19 7:24 ` dpdklab
2024-03-19 7:26 ` dpdklab
2024-03-19 7:27 ` dpdklab
2024-03-19 7:29 ` dpdklab
2024-03-19 7:30 ` |SUCCESS| " dpdklab
2024-03-19 7:30 ` dpdklab
2024-03-19 7:32 ` |FAILURE| " dpdklab
2024-03-19 7:32 ` dpdklab
2024-03-19 7:33 ` dpdklab
2024-03-19 7:34 ` |SUCCESS| " dpdklab
2024-03-19 7:41 ` |FAILURE| " dpdklab
2024-03-19 7:41 ` dpdklab
2024-03-19 7:42 ` dpdklab
2024-03-19 7:46 ` dpdklab
2024-03-19 7:47 ` dpdklab
2024-03-19 7:47 ` dpdklab
2024-03-19 7:56 ` dpdklab
2024-03-19 7:57 ` dpdklab
2024-03-19 8:03 ` dpdklab
2024-03-19 8:25 ` |SUCCESS| " dpdklab
2024-03-21 4:18 ` dpdklab
2024-03-21 5:18 ` 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=20240319072333.1423929-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=jingjing.wu@intel.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).