From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143110 [PATCH v2 3/3] test/bbdev: update for queue stats
Date: Mon, 12 Aug 2024 20:42:38 -0400 [thread overview]
Message-ID: <20240813004238.2291499-1-robot@bytheb.org> (raw)
In-Reply-To: <20240812234201.2196633-4-nicolas.chautru@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143110/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10361220408
next prev parent reply other threads:[~2024-08-13 0:42 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240812234201.2196633-4-nicolas.chautru@intel.com>
2024-08-12 23:13 ` |SUCCESS| pw143109-143110 " qemudev
2024-08-12 23:17 ` qemudev
2024-08-12 23:41 ` |SUCCESS| pw143110 " checkpatch
2024-08-13 0:42 ` 0-day Robot [this message]
2024-08-13 16:16 ` |SUCCESS| pw143109-143110 [PATCH] [v2,3/3] test/bbdev: update for qu dpdklab
2024-08-13 16:16 ` dpdklab
2024-08-13 16:18 ` |PENDING| " dpdklab
2024-08-13 16:20 ` |SUCCESS| " dpdklab
2024-08-13 16:22 ` dpdklab
2024-08-13 16:24 ` dpdklab
2024-08-13 16:24 ` dpdklab
2024-08-13 16:26 ` |PENDING| " dpdklab
2024-08-13 16:27 ` |SUCCESS| " dpdklab
2024-08-13 16:28 ` |PENDING| " dpdklab
2024-08-13 16:30 ` dpdklab
2024-08-13 16:31 ` dpdklab
2024-08-13 16:32 ` dpdklab
2024-08-13 16:34 ` |SUCCESS| " dpdklab
2024-08-13 16:34 ` |PENDING| " dpdklab
2024-08-13 16:35 ` dpdklab
2024-08-13 16:36 ` dpdklab
2024-08-13 16:36 ` dpdklab
2024-08-13 16:37 ` |SUCCESS| " dpdklab
2024-08-13 16:38 ` |PENDING| " dpdklab
2024-08-13 16:38 ` dpdklab
2024-08-13 16:39 ` dpdklab
2024-08-13 16:39 ` |SUCCESS| " dpdklab
2024-08-13 16:39 ` |PENDING| " dpdklab
2024-08-13 16:40 ` dpdklab
2024-08-13 16:41 ` dpdklab
2024-08-13 16:41 ` |SUCCESS| " dpdklab
2024-08-13 16:41 ` |PENDING| " dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:43 ` dpdklab
2024-08-13 16:43 ` dpdklab
2024-08-13 16:44 ` dpdklab
2024-08-13 16:44 ` dpdklab
2024-08-13 16:45 ` dpdklab
2024-08-13 16:47 ` dpdklab
2024-08-13 16:47 ` dpdklab
2024-08-13 16:49 ` dpdklab
2024-08-13 16:51 ` |SUCCESS| " dpdklab
2024-08-13 16:51 ` |PENDING| " dpdklab
2024-08-13 16:52 ` dpdklab
2024-08-13 16:52 ` dpdklab
2024-08-13 16:53 ` dpdklab
2024-08-13 16:53 ` dpdklab
2024-08-13 16:54 ` dpdklab
2024-08-13 16:54 ` dpdklab
2024-08-13 16:55 ` dpdklab
2024-08-13 16:56 ` dpdklab
2024-08-13 16:56 ` dpdklab
2024-08-13 16:57 ` dpdklab
2024-08-13 16:58 ` dpdklab
2024-08-13 16:59 ` dpdklab
2024-08-13 17:00 ` |SUCCESS| " dpdklab
2024-08-13 17:01 ` dpdklab
2024-08-13 17:01 ` |PENDING| " dpdklab
2024-08-13 17:02 ` dpdklab
2024-08-13 17:03 ` |SUCCESS| " dpdklab
2024-08-13 17:03 ` |PENDING| " dpdklab
2024-08-13 17:03 ` dpdklab
2024-08-13 17:04 ` dpdklab
2024-08-13 17:04 ` dpdklab
2024-08-13 17:04 ` dpdklab
2024-08-13 17:06 ` dpdklab
2024-08-13 17:06 ` dpdklab
2024-08-13 17:07 ` dpdklab
2024-08-13 17:07 ` dpdklab
2024-08-13 17:07 ` dpdklab
2024-08-13 17:08 ` dpdklab
2024-08-13 17:08 ` dpdklab
2024-08-13 17:10 ` dpdklab
2024-08-13 17:10 ` dpdklab
2024-08-13 17:10 ` dpdklab
2024-08-13 17:11 ` dpdklab
2024-08-13 17:11 ` |SUCCESS| " dpdklab
2024-08-13 17:12 ` |PENDING| " dpdklab
2024-08-13 17:12 ` dpdklab
2024-08-13 17:12 ` |SUCCESS| " dpdklab
2024-08-13 17:13 ` |PENDING| " dpdklab
2024-08-13 17:14 ` dpdklab
2024-08-13 17:15 ` |SUCCESS| " dpdklab
2024-08-13 17:16 ` |PENDING| " dpdklab
2024-08-13 17:18 ` dpdklab
2024-08-13 17:18 ` dpdklab
2024-08-13 17:21 ` |SUCCESS| " dpdklab
2024-08-13 17:32 ` dpdklab
2024-08-13 17:36 ` |PENDING| " dpdklab
2024-08-13 18:12 ` dpdklab
2024-08-13 18:26 ` |SUCCESS| " dpdklab
2024-08-13 19:36 ` 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=20240813004238.2291499-1-robot@bytheb.org \
--to=robot@bytheb.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).