From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw139725 [RFC] eal: make lcore_init aware of cgroup
Date: Mon, 29 Apr 2024 16:44:07 -0400 [thread overview]
Message-ID: <20240429204407.3113928-1-robot@bytheb.org> (raw)
In-Reply-To: <20240429195342.42711-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/139725/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8884723739
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
####################################################################################
####################################################################################
#### [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
####################################################################################
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-04-29 20:44 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240429195342.42711-1-stephen@networkplumber.org>
2024-04-29 19:27 ` |SUCCESS| " qemudev
2024-04-29 19:31 ` |FAILURE| " qemudev
2024-04-29 20:36 ` |SUCCESS| pw139725 [PATCH] [RFC] eal: make lcore_init aware of cgrou dpdklab
2024-04-29 20:36 ` dpdklab
2024-04-29 20:36 ` |FAILURE| " dpdklab
2024-04-29 20:37 ` |SUCCESS| " dpdklab
2024-04-29 20:38 ` |FAILURE| " dpdklab
2024-04-29 20:38 ` dpdklab
2024-04-29 20:39 ` |SUCCESS| " dpdklab
2024-04-29 20:39 ` dpdklab
2024-04-29 20:40 ` |FAILURE| " dpdklab
2024-04-29 20:40 ` |SUCCESS| " dpdklab
2024-04-29 20:41 ` dpdklab
2024-04-29 20:41 ` |FAILURE| " dpdklab
2024-04-29 20:41 ` dpdklab
2024-04-29 20:42 ` dpdklab
2024-04-29 20:42 ` |SUCCESS| " dpdklab
2024-04-29 20:42 ` dpdklab
2024-04-29 20:42 ` dpdklab
2024-04-29 20:43 ` |FAILURE| " dpdklab
2024-04-29 20:43 ` dpdklab
2024-04-29 20:44 ` 0-day Robot [this message]
2024-04-29 20:44 ` |SUCCESS| " dpdklab
2024-04-29 20:44 ` dpdklab
2024-04-29 20:44 ` dpdklab
2024-04-29 20:44 ` |FAILURE| " dpdklab
2024-04-29 20:45 ` |SUCCESS| " dpdklab
2024-04-29 20:45 ` |FAILURE| " dpdklab
2024-04-29 20:45 ` |SUCCESS| " dpdklab
2024-04-29 20:46 ` dpdklab
2024-04-29 20:46 ` dpdklab
2024-04-29 20:46 ` dpdklab
2024-04-29 20:46 ` dpdklab
2024-04-29 20:47 ` |FAILURE| " dpdklab
2024-04-29 20:47 ` |SUCCESS| " dpdklab
2024-04-29 20:47 ` dpdklab
2024-04-29 20:47 ` |FAILURE| " dpdklab
2024-04-29 20:48 ` |SUCCESS| " dpdklab
2024-04-29 20:48 ` dpdklab
2024-04-29 20:48 ` dpdklab
2024-04-29 20:48 ` |FAILURE| " dpdklab
2024-04-29 20:48 ` dpdklab
2024-04-29 20:49 ` |SUCCESS| " dpdklab
2024-04-29 20:49 ` dpdklab
2024-04-29 20:50 ` |FAILURE| " dpdklab
2024-04-29 20:50 ` |SUCCESS| " dpdklab
2024-04-29 20:50 ` |FAILURE| " dpdklab
2024-04-29 20:50 ` dpdklab
2024-04-29 20:51 ` |SUCCESS| " dpdklab
2024-04-29 20:51 ` dpdklab
2024-04-29 20:51 ` |FAILURE| " dpdklab
2024-04-29 20:51 ` |SUCCESS| " dpdklab
2024-04-29 20:53 ` dpdklab
2024-04-29 20:53 ` dpdklab
2024-04-29 20:53 ` dpdklab
2024-04-29 20:54 ` dpdklab
2024-04-29 20:55 ` |FAILURE| " dpdklab
2024-04-29 20:56 ` |SUCCESS| " dpdklab
2024-04-29 20:58 ` dpdklab
2024-04-29 20:59 ` dpdklab
2024-04-29 20:59 ` |FAILURE| " dpdklab
2024-04-29 20:59 ` |SUCCESS| " dpdklab
2024-04-29 20:59 ` dpdklab
2024-04-29 20:59 ` dpdklab
2024-04-29 21:00 ` dpdklab
2024-04-29 21:00 ` dpdklab
2024-04-29 21:00 ` |FAILURE| " dpdklab
2024-04-29 21:01 ` dpdklab
2024-04-29 21:02 ` dpdklab
2024-04-29 21:02 ` dpdklab
2024-04-29 21:03 ` dpdklab
2024-04-29 21:04 ` |SUCCESS| " dpdklab
2024-04-29 21:05 ` |FAILURE| " dpdklab
2024-04-29 21:05 ` dpdklab
2024-04-29 21:06 ` |SUCCESS| " dpdklab
2024-04-29 21:07 ` |FAILURE| " dpdklab
2024-04-29 21:12 ` |SUCCESS| " dpdklab
2024-04-29 21:16 ` |FAILURE| " dpdklab
2024-04-29 21:20 ` |SUCCESS| " dpdklab
2024-04-29 21:27 ` |FAILURE| " dpdklab
2024-04-29 21:35 ` |SUCCESS| " dpdklab
2024-04-29 21:36 ` dpdklab
2024-04-29 22:07 ` dpdklab
2024-04-29 23:25 ` 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=20240429204407.3113928-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).