From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138767 [PATCH] graph: avoid accessing graph list when getting stats
Date: Mon, 25 Mar 2024 12:44:31 -0400 [thread overview]
Message-ID: <20240325164431.876216-1-robot@bytheb.org> (raw)
In-Reply-To: <20240325155303.770468-2-rjarry@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138767/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8423192469
next prev parent reply other threads:[~2024-03-25 16:44 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240325155303.770468-2-rjarry@redhat.com>
2024-03-25 15:39 ` qemudev
2024-03-25 15:43 ` qemudev
2024-03-25 15:55 ` checkpatch
2024-03-25 16:44 ` 0-day Robot [this message]
2024-03-25 17:12 ` |SUCCESS| pw138767 [PATCH] graph: avoid accessing graph list when ge dpdklab
2024-03-25 17:21 ` dpdklab
2024-03-25 17:21 ` dpdklab
2024-03-25 17:21 ` dpdklab
2024-03-25 17:22 ` dpdklab
2024-03-25 17:23 ` dpdklab
2024-03-25 17:24 ` dpdklab
2024-03-25 17:24 ` dpdklab
2024-03-25 17:24 ` dpdklab
2024-03-25 17:24 ` dpdklab
2024-03-25 17:25 ` dpdklab
2024-03-25 17:25 ` dpdklab
2024-03-25 17:25 ` dpdklab
2024-03-25 17:25 ` dpdklab
2024-03-25 17:26 ` dpdklab
2024-03-25 17:26 ` dpdklab
2024-03-25 17:26 ` dpdklab
2024-03-25 17:26 ` dpdklab
2024-03-25 17:29 ` dpdklab
2024-03-25 17:29 ` dpdklab
2024-03-25 17:30 ` dpdklab
2024-03-25 17:30 ` dpdklab
2024-03-25 17:31 ` dpdklab
2024-03-25 17:31 ` dpdklab
2024-03-25 17:31 ` dpdklab
2024-03-25 17:32 ` dpdklab
2024-03-25 17:32 ` dpdklab
2024-03-25 17:32 ` dpdklab
2024-03-25 17:32 ` dpdklab
2024-03-25 17:32 ` dpdklab
2024-03-25 17:33 ` dpdklab
2024-03-25 17:33 ` dpdklab
2024-03-25 17:33 ` dpdklab
2024-03-25 17:33 ` dpdklab
2024-03-25 17:35 ` dpdklab
2024-03-25 17:35 ` dpdklab
2024-03-25 17:36 ` dpdklab
2024-03-25 17:36 ` dpdklab
2024-03-25 17:36 ` dpdklab
2024-03-25 17:36 ` dpdklab
2024-03-25 17:37 ` dpdklab
2024-03-25 17:37 ` dpdklab
2024-03-25 17:37 ` dpdklab
2024-03-25 17:39 ` dpdklab
2024-03-25 17:40 ` dpdklab
2024-03-25 17:49 ` dpdklab
2024-03-25 17:50 ` dpdklab
2024-03-25 17:51 ` dpdklab
2024-03-25 17:59 ` dpdklab
2024-03-25 17:59 ` dpdklab
2024-03-25 18:00 ` dpdklab
2024-03-25 18:00 ` dpdklab
2024-03-25 18:01 ` dpdklab
2024-03-25 18:01 ` dpdklab
2024-03-25 18:01 ` dpdklab
2024-03-25 18:02 ` dpdklab
2024-03-25 18:02 ` dpdklab
2024-03-25 18:02 ` dpdklab
2024-03-25 18:03 ` dpdklab
2024-03-25 18:03 ` dpdklab
2024-03-25 18:04 ` dpdklab
2024-03-25 18:04 ` dpdklab
2024-03-25 18:04 ` dpdklab
2024-03-25 18:05 ` dpdklab
2024-03-25 18:05 ` dpdklab
2024-03-25 18:06 ` dpdklab
2024-03-25 18:09 ` dpdklab
2024-03-25 18:10 ` dpdklab
2024-03-25 18:15 ` dpdklab
2024-03-25 18:17 ` dpdklab
2024-03-25 18:18 ` dpdklab
2024-03-25 18:54 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 19:00 ` dpdklab
2024-04-01 15:07 ` dpdklab
2024-04-01 15:11 ` dpdklab
2024-04-01 15:15 ` dpdklab
2024-04-01 15:19 ` dpdklab
2024-04-01 15:39 ` 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=20240325164431.876216-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).