From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130662 [PATCH] [v2] net/iavf: fix checksum offloading
Date: Wed, 23 Aug 2023 04:40:25 -0700 (PDT) [thread overview]
Message-ID: <64e5f029.b00a0220.67243.f905SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130662
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, August 23 2023 06:29:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130662 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| Debian Buster | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27425/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-23 11:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 11:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-24 1:24 dpdklab
2023-08-24 0:59 dpdklab
2023-08-24 0:38 dpdklab
2023-08-24 0:34 dpdklab
2023-08-24 0:29 dpdklab
2023-08-23 13:35 dpdklab
2023-08-23 13:15 dpdklab
2023-08-23 12:47 dpdklab
2023-08-23 11:59 dpdklab
2023-08-23 11:57 dpdklab
2023-08-23 11:56 dpdklab
2023-08-23 11:56 dpdklab
2023-08-23 11:55 dpdklab
2023-08-23 11:54 dpdklab
2023-08-23 11:53 dpdklab
2023-08-23 11:52 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:51 dpdklab
2023-08-23 11:45 dpdklab
2023-08-23 11:42 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:41 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:39 dpdklab
2023-08-23 11:39 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:35 dpdklab
2023-08-23 11:35 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:32 dpdklab
2023-08-23 11:31 dpdklab
2023-08-23 11:19 dpdklab
[not found] <20230823062911.2483926-1-david.marchand@redhat.com>
2023-08-23 6:17 ` |SUCCESS| pw130662 [PATCH v2] " qemudev
2023-08-23 6:21 ` qemudev
2023-08-23 6:30 ` checkpatch
2023-08-23 7:19 ` 0-day Robot
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=64e5f029.b00a0220.67243.f905SMTPIN_ADDED_MISSING@mx.google.com \
--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).