From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw102748 [PATCH] ip_frag: fix the buf of fragmenting IPv4 fragment
Date: Thu, 28 Oct 2021 01:11:12 -0400 (EDT) [thread overview]
Message-ID: <20211028051112.B55FE60524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/102748
_Testing PASS_
Submitter: huichao cai <chcchc88@163.com>
Date: Monday, October 25 2021 07:55:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:daa02b5cddbb8e11b31d41e2bf7bb1ae64dcae2f
102748 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | PASS |
+------------------+----------------+
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19684/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-28 5:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 5:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-26 2:49 dpdklab
2021-10-26 2:03 dpdklab
2021-10-26 0:33 dpdklab
2021-10-25 22:22 dpdklab
2021-10-25 22:09 dpdklab
2021-10-25 21:56 dpdklab
2021-10-25 20:54 dpdklab
2021-10-25 20:24 dpdklab
2021-10-25 19:59 dpdklab
2021-10-25 19:53 dpdklab
2021-10-25 19:40 dpdklab
2021-10-25 19:39 dpdklab
2021-10-25 19:27 dpdklab
2021-10-25 19:24 dpdklab
[not found] <1635148553-50086-1-git-send-email-chcchc88@163.com>
2021-10-25 7:57 ` checkpatch
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=20211028051112.B55FE60524@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).