From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw142516 [PATCH 4/4] test: run timer secondary tests as part of fast suite
Date: Thu, 18 Jul 2024 16:03:52 -0400 [thread overview]
Message-ID: <20240718200352.2342308-1-robot@bytheb.org> (raw)
In-Reply-To: <20240718191049.84865-5-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/142516/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9997472876
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
####################################################################################
106/115 DPDK:fast-tests / thash_autotest OK 0.27 s
107/115 DPDK:fast-tests / threads_autotest OK 0.37 s
108/115 DPDK:fast-tests / ticketlock_autotest OK 0.27 s
109/115 DPDK:fast-tests / timer_autotest OK 2.82 s
110/115 DPDK:fast-tests / timer_secondary_autotest TIMEOUT 30.01 s
111/115 DPDK:fast-tests / trace_autotest OK 0.27 s
112/115 DPDK:fast-tests / trace_autotest_with_traces OK 0.27 s
113/115 DPDK:fast-tests / vdev_autotest OK 0.27 s
114/115 DPDK:fast-tests / version_autotest OK 0.27 s
115/115 DPDK:fast-tests / telemetry_all OK 1.07 s
Ok: 108
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
####################################################################################
92/101 DPDK:fast-tests / thash_autotest OK 0.37 s
93/101 DPDK:fast-tests / threads_autotest OK 0.52 s
94/101 DPDK:fast-tests / ticketlock_autotest OK 0.42 s
95/101 DPDK:fast-tests / timer_autotest OK 2.87 s
96/101 DPDK:fast-tests / timer_secondary_autotest TIMEOUT 30.04 s
97/101 DPDK:fast-tests / trace_autotest OK 0.37 s
98/101 DPDK:fast-tests / trace_autotest_with_traces OK 0.37 s
99/101 DPDK:fast-tests / vdev_autotest OK 0.37 s
100/101 DPDK:fast-tests / version_autotest OK 0.37 s
101/101 DPDK:fast-tests / telemetry_all OK 1.12 s
Ok: 94
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-07-18 20:03 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240718191049.84865-5-stephen@networkplumber.org>
2024-07-18 19:01 ` |SUCCESS| pw142513-142516 " qemudev
2024-07-18 19:06 ` qemudev
2024-07-18 19:12 ` |SUCCESS| pw142516 " checkpatch
2024-07-18 20:03 ` 0-day Robot [this message]
2024-07-19 8:55 ` |PENDING| pw142513-142516 [PATCH] [4/4] test: run timer secondary te dpdklab
2024-07-19 9:03 ` |SUCCESS| " dpdklab
2024-07-19 9:04 ` dpdklab
2024-07-19 9:06 ` dpdklab
2024-07-19 9:17 ` dpdklab
2024-07-19 9:18 ` dpdklab
2024-07-19 9:20 ` dpdklab
2024-07-19 9:20 ` dpdklab
2024-07-19 9:38 ` dpdklab
2024-07-19 10:39 ` |PENDING| " dpdklab
2024-07-19 10:47 ` |SUCCESS| " dpdklab
2024-07-19 10:56 ` |PENDING| " dpdklab
2024-07-19 10:58 ` dpdklab
2024-07-19 11:04 ` dpdklab
2024-07-19 11:06 ` dpdklab
2024-07-19 11:11 ` dpdklab
2024-07-19 11:13 ` dpdklab
2024-07-19 11:16 ` dpdklab
2024-07-19 11:18 ` dpdklab
2024-07-19 11:20 ` dpdklab
2024-07-19 11:20 ` dpdklab
2024-07-19 11:23 ` |SUCCESS| " dpdklab
2024-07-19 11:25 ` |PENDING| " dpdklab
2024-07-19 11:25 ` dpdklab
2024-07-19 11:26 ` dpdklab
2024-07-19 11:26 ` |SUCCESS| " dpdklab
2024-07-19 11:26 ` |PENDING| " dpdklab
2024-07-19 11:27 ` dpdklab
2024-07-19 11:30 ` dpdklab
2024-07-19 11:32 ` dpdklab
2024-07-19 11:32 ` dpdklab
2024-07-19 11:32 ` dpdklab
2024-07-19 11:33 ` dpdklab
2024-07-19 11:34 ` |FAILURE| " dpdklab
2024-07-19 11:35 ` dpdklab
2024-07-19 11:35 ` |PENDING| " dpdklab
2024-07-19 11:37 ` dpdklab
2024-07-19 11:38 ` dpdklab
2024-07-19 11:38 ` dpdklab
2024-07-19 11:42 ` dpdklab
2024-07-19 11:43 ` dpdklab
2024-07-19 11:44 ` dpdklab
2024-07-19 11:44 ` dpdklab
2024-07-19 11:46 ` dpdklab
2024-07-19 11:53 ` dpdklab
2024-07-19 11:57 ` |SUCCESS| " dpdklab
2024-07-19 12:00 ` |PENDING| " dpdklab
2024-07-19 12:00 ` dpdklab
2024-07-19 12:02 ` dpdklab
2024-07-19 12:02 ` dpdklab
2024-07-19 12:03 ` dpdklab
2024-07-19 12:04 ` dpdklab
2024-07-19 12:08 ` dpdklab
2024-07-19 12:09 ` dpdklab
2024-07-19 12:09 ` dpdklab
2024-07-19 12:09 ` dpdklab
2024-07-19 12:10 ` dpdklab
2024-07-19 12:10 ` dpdklab
2024-07-19 12:12 ` |FAILURE| " dpdklab
2024-07-19 12:12 ` |PENDING| " dpdklab
2024-07-19 12:13 ` dpdklab
2024-07-19 12:13 ` dpdklab
2024-07-19 12:13 ` dpdklab
2024-07-19 12:15 ` |SUCCESS| " dpdklab
2024-07-19 12:15 ` |PENDING| " dpdklab
2024-07-19 12:16 ` |FAILURE| " dpdklab
2024-07-19 12:18 ` |SUCCESS| " dpdklab
2024-07-19 12:21 ` |FAILURE| " dpdklab
2024-07-19 12:22 ` dpdklab
2024-07-19 12:23 ` |SUCCESS| " dpdklab
2024-07-19 12:24 ` |FAILURE| " dpdklab
2024-07-19 12:27 ` dpdklab
2024-07-19 12:28 ` dpdklab
2024-07-19 12:28 ` |PENDING| " dpdklab
2024-07-19 12:28 ` |SUCCESS| " dpdklab
2024-07-19 12:28 ` |FAILURE| " dpdklab
2024-07-19 12:33 ` dpdklab
2024-07-19 12:33 ` |SUCCESS| " dpdklab
2024-07-19 12:34 ` |FAILURE| " dpdklab
2024-07-19 12:37 ` dpdklab
2024-07-19 12:38 ` dpdklab
2024-07-19 12:40 ` dpdklab
2024-07-19 12:40 ` dpdklab
2024-07-19 12:41 ` dpdklab
2024-07-19 12:43 ` dpdklab
2024-07-19 12:50 ` |PENDING| " dpdklab
2024-07-19 12:52 ` |SUCCESS| " dpdklab
2024-07-19 12:55 ` |PENDING| " dpdklab
2024-07-19 12:56 ` dpdklab
2024-07-19 12:57 ` dpdklab
2024-07-19 12:59 ` dpdklab
2024-07-19 13:00 ` dpdklab
2024-07-19 13:00 ` dpdklab
2024-07-19 13:00 ` dpdklab
2024-07-19 13:03 ` dpdklab
2024-07-19 13:05 ` dpdklab
2024-07-19 13:06 ` dpdklab
2024-07-19 13:08 ` dpdklab
2024-07-19 13:08 ` dpdklab
2024-07-19 13:08 ` dpdklab
2024-07-19 13:11 ` dpdklab
2024-07-19 13:12 ` dpdklab
2024-07-19 13:12 ` dpdklab
2024-07-19 13:15 ` dpdklab
2024-07-19 13:15 ` dpdklab
2024-07-19 13:19 ` |SUCCESS| " dpdklab
2024-07-19 13:22 ` |PENDING| " dpdklab
2024-07-19 13:30 ` dpdklab
2024-07-19 13:31 ` |FAILURE| " dpdklab
2024-07-19 13:48 ` |SUCCESS| " dpdklab
2024-07-19 20:24 ` 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=20240718200352.2342308-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=stephen@networkplumber.org \
--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).