From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>,
dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130508 [PATCH] net/iavf: fix checksum offloading
Date: Fri, 18 Aug 2023 02:58:22 -0700 (PDT) [thread overview]
Message-ID: <64df40be.170a0220.be902.2e1dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130508
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, August 18 2023 09:03:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130508 --> testing pass
Test environment and result as below:
+--------------------------+----------------+------------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+================+==============================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+--------------------------+----------------+------------------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27379/
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-18 9:58 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 9:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 22:57 dpdklab
2023-08-18 22:53 dpdklab
2023-08-18 22:36 dpdklab
2023-08-18 22:31 dpdklab
2023-08-18 22:27 dpdklab
[not found] <20230818090351.2402519-1-david.marchand@redhat.com>
2023-08-18 8:56 ` qemudev
2023-08-18 9:00 ` qemudev
2023-08-18 9:05 ` checkpatch
2023-08-18 17:59 ` 0-day Robot
2023-08-18 11:07 dpdklab
2023-08-18 10:34 dpdklab
2023-08-18 10:26 dpdklab
2023-08-18 10:26 dpdklab
2023-08-18 10:25 dpdklab
2023-08-18 10:18 dpdklab
2023-08-18 10:15 dpdklab
2023-08-18 10:15 dpdklab
2023-08-18 10:14 dpdklab
2023-08-18 10:13 dpdklab
2023-08-18 10:13 dpdklab
2023-08-18 10:13 dpdklab
2023-08-18 10:12 dpdklab
2023-08-18 10:03 dpdklab
2023-08-18 10:02 dpdklab
2023-08-18 10:01 dpdklab
2023-08-18 10:01 dpdklab
2023-08-18 10:01 dpdklab
2023-08-18 10:00 dpdklab
2023-08-18 9:59 dpdklab
2023-08-18 9:59 dpdklab
2023-08-18 9:58 dpdklab
2023-08-18 9:57 dpdklab
2023-08-18 9:57 dpdklab
2023-08-18 9:57 dpdklab
2023-08-18 9:57 dpdklab
2023-08-18 9:52 dpdklab
2023-08-18 9:51 dpdklab
2023-08-18 9:47 dpdklab
2023-08-18 9:46 dpdklab
2023-08-18 9:46 dpdklab
2023-08-18 9:46 dpdklab
2023-08-18 9:45 dpdklab
2023-08-18 9:45 dpdklab
2023-08-18 9:43 dpdklab
2023-08-18 9:42 dpdklab
2023-08-18 9:42 dpdklab
2023-08-18 9:42 dpdklab
2023-08-18 9:41 dpdklab
2023-08-18 9:41 dpdklab
2023-08-18 9:40 dpdklab
2023-08-18 9:38 dpdklab
2023-08-18 9:38 dpdklab
2023-08-18 9:37 dpdklab
2023-08-18 9:37 dpdklab
2023-08-18 9:36 dpdklab
2023-08-18 9:36 dpdklab
2023-08-18 9:36 dpdklab
2023-08-18 9:35 dpdklab
2023-08-18 9:35 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=64df40be.170a0220.be902.2e1dSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).