From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147877 [PATCH] [v2] igc: fix invalid length and corrupte
Date: Fri, 01 Nov 2024 11:57:16 -0700 (PDT) [thread overview]
Message-ID: <6725248c.050a0220.1e3d8c.dfe1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147877
_Testing PASS_
Submitter: Martin Weiser <martin.weiser@allegro-packets.com>
Date: Friday, November 01 2024 13:57:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:035326eb9633c344ee61e03fbcdf120a76c54830
147877 --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#329140
Test environment and result as below:
+-------------------+--------------------+------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_compile_ovs | dpdk_compile_spdk |
+===================+====================+==================+===================+
| FreeBSD 13.4 | PASS | SKIPPED | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
| CentOS Stream 9 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Debian 12 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Fedora 39 (Clang) | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Fedora 39 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Fedora 40 (Clang) | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Fedora 40 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| openSUSE Leap 15 | PASS | PASS | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
| RHEL8 | PASS | PASS | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
| RHEL9 | PASS | PASS | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
| Ubuntu 20.04 | PASS | PASS | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
| Ubuntu 22.04 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Ubuntu 24.04 | PASS | PASS | PASS |
+-------------------+--------------------+------------------+-------------------+
| Alpine | PASS | PASS | SKIPPED |
+-------------------+--------------------+------------------+-------------------+
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
openSUSE Leap 15
Kernel: Depends on container host
Compiler: gcc (SUSE Linux) 7.5.0
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Alpine
Kernel: Depends on container host
Compiler: gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31805/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-11-01 18:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com>
2024-11-01 13:27 ` |SUCCESS| pw147877 [PATCH v2] igc: fix invalid length and corrupted multi-segment mbufs qemudev
2024-11-01 13:31 ` qemudev
2024-11-01 13:59 ` |WARNING| " checkpatch
2024-11-01 15:30 ` |SUCCESS| pw147877 [PATCH] [v2] igc: fix invalid length and corrupte dpdklab
2024-11-01 15:33 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:48 ` dpdklab
2024-11-01 15:49 ` |PENDING| " dpdklab
2024-11-01 15:55 ` |SUCCESS| " dpdklab
2024-11-01 15:56 ` dpdklab
2024-11-01 16:32 ` |PENDING| " dpdklab
2024-11-01 16:35 ` dpdklab
2024-11-01 17:06 ` |SUCCESS| " dpdklab
2024-11-01 17:07 ` dpdklab
2024-11-01 18:26 ` |PENDING| " dpdklab
2024-11-01 18:57 ` dpdklab [this message]
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=6725248c.050a0220.1e3d8c.dfe1SMTPIN_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).