From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138810 [PATCH v7 14/14] examples/ipsec-secgw: fix port ID restriction
Date: Tue, 26 Mar 2024 09:56:19 -0400 [thread overview]
Message-ID: <20240326135619.1743427-1-robot@bytheb.org> (raw)
In-Reply-To: <20240326125554.138840-15-sivaprasad.tummala@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138810/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8436490220
next prev parent reply other threads:[~2024-03-26 13:56 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240326125554.138840-15-sivaprasad.tummala@amd.com>
2024-03-26 12:35 ` |SUCCESS| pw138797-138810 " qemudev
2024-03-26 12:40 ` qemudev
2024-03-26 12:58 ` |SUCCESS| pw138810 " checkpatch
2024-03-26 13:32 ` |SUCCESS| pw138797-138810 [PATCH] [v7,14/14] examples/ipsec-secgw: f dpdklab
2024-03-26 13:32 ` dpdklab
2024-03-26 13:32 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:34 ` dpdklab
2024-03-26 13:34 ` dpdklab
2024-03-26 13:34 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:40 ` dpdklab
2024-03-26 13:41 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:44 ` dpdklab
2024-03-26 13:44 ` dpdklab
2024-03-26 13:45 ` dpdklab
2024-03-26 13:45 ` dpdklab
2024-03-26 13:45 ` dpdklab
2024-03-26 13:46 ` dpdklab
2024-03-26 13:47 ` dpdklab
2024-03-26 13:47 ` |FAILURE| " dpdklab
2024-03-26 13:47 ` |SUCCESS| " dpdklab
2024-03-26 13:49 ` dpdklab
2024-03-26 13:49 ` dpdklab
2024-03-26 13:51 ` dpdklab
2024-03-26 13:51 ` |FAILURE| " dpdklab
2024-03-26 13:53 ` |SUCCESS| " dpdklab
2024-03-26 13:55 ` |FAILURE| " dpdklab
2024-03-26 13:56 ` 0-day Robot [this message]
2024-03-26 13:57 ` dpdklab
2024-03-26 13:58 ` |SUCCESS| " dpdklab
2024-03-26 13:58 ` |FAILURE| " dpdklab
2024-03-26 13:59 ` dpdklab
2024-03-26 14:00 ` dpdklab
2024-03-26 14:04 ` |SUCCESS| " dpdklab
2024-03-26 14:05 ` dpdklab
2024-03-26 14:07 ` dpdklab
2024-03-26 14:34 ` dpdklab
2024-03-26 14:54 ` dpdklab
2024-04-01 23:15 ` dpdklab
2024-04-01 23:19 ` dpdklab
2024-04-01 23:23 ` dpdklab
2024-04-01 23:42 ` dpdklab
2024-04-01 23:46 ` dpdklab
2024-04-25 13:01 ` |FAILURE| " dpdklab
2024-04-25 13:01 ` |SUCCESS| " dpdklab
2024-04-25 13:02 ` dpdklab
2024-04-25 13:04 ` dpdklab
2024-04-25 13:05 ` dpdklab
2024-04-25 13:08 ` dpdklab
2024-04-25 13:08 ` dpdklab
2024-04-25 13:10 ` dpdklab
2024-04-25 13:13 ` dpdklab
2024-04-25 13:13 ` dpdklab
2024-04-25 13:16 ` dpdklab
2024-04-25 13:18 ` dpdklab
2024-04-25 13:19 ` dpdklab
2024-04-25 13:23 ` dpdklab
2024-04-25 13:25 ` dpdklab
2024-04-25 13:27 ` dpdklab
2024-04-25 13:29 ` dpdklab
2024-04-25 13:32 ` |WARNING| " dpdklab
2024-04-25 14:03 ` |SUCCESS| " dpdklab
2024-04-25 14:05 ` dpdklab
2024-04-25 14:08 ` dpdklab
2024-04-25 14:10 ` dpdklab
2024-04-25 14:15 ` dpdklab
2024-04-25 14:17 ` dpdklab
2024-04-25 14:18 ` dpdklab
2024-04-25 14:22 ` dpdklab
2024-04-25 14:30 ` dpdklab
2024-04-25 14:44 ` dpdklab
2024-04-25 15:06 ` 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=20240326135619.1743427-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).