From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147514 [PATCH] igc: fix invalid length and corrupted mul
Date: Thu, 31 Oct 2024 13:18:03 -0700 (PDT) [thread overview]
Message-ID: <6723e5fb.170a0220.497c.ebe9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <f6a99a92-1b16-4f65-9d89-cc9e602d1698@allegro-packets.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147514
_Testing PASS_
Submitter: Martin Weiser <martin.weiser@allegro-packets.com>
Date: Monday, October 28 2024 14:17:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e281b02d873b4d62280d323157a5877b70d01e07
147514 --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#30993
Test environment and result as below:
+--------------+--------------------+
| Environment | dpdk_meson_compile |
+==============+====================+
| FreeBSD 14.1 | PASS |
+--------------+--------------------+
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31723/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-10-31 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f6a99a92-1b16-4f65-9d89-cc9e602d1698@allegro-packets.com>
2024-10-28 13:45 ` |SUCCESS| pw147514 [PATCH] igc: fix invalid length and corrupted multi-segment mbufs qemudev
2024-10-28 13:50 ` qemudev
2024-10-28 14:18 ` checkpatch
2024-10-28 15:05 ` 0-day Robot
2024-10-31 19:11 ` |SUCCESS| pw147514 [PATCH] igc: fix invalid length and corrupted mul dpdklab
2024-10-31 20:18 ` dpdklab [this message]
2024-10-31 22:30 ` dpdklab
2024-10-31 22:48 ` dpdklab
2024-10-31 22:58 ` |PENDING| " dpdklab
2024-10-31 23:36 ` |SUCCESS| " dpdklab
2024-10-31 23:46 ` |PENDING| " dpdklab
2024-11-01 0:08 ` |SUCCESS| " 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=6723e5fb.170a0220.497c.ebe9SMTPIN_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).