From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144429 [PATCH] mbuf: fix strict aliasing error in alloca
Date: Wed, 25 Sep 2024 08:23:40 -0700 (PDT) [thread overview]
Message-ID: <66f42afc.170a0220.3be304.9862SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240925140021.46320-2-rjarry@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/144429
_Functional Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Wednesday, September 25 2024 14:00:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144429 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#183345
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31132/
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-09-25 15:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240925140021.46320-2-rjarry@redhat.com>
2024-09-25 13:33 ` |SUCCESS| pw144429 [PATCH dpdk] mbuf: fix strict aliasing error in allocator qemudev
2024-09-25 13:37 ` qemudev
2024-09-25 14:01 ` checkpatch
2024-09-25 14:36 ` |SUCCESS| pw144429 [PATCH] mbuf: fix strict aliasing error in alloca dpdklab
2024-09-25 14:46 ` |PENDING| " dpdklab
2024-09-25 14:51 ` |SUCCESS| " dpdklab
2024-09-25 14:53 ` dpdklab
2024-09-25 14:54 ` |PENDING| " dpdklab
2024-09-25 14:54 ` dpdklab
2024-09-25 14:56 ` |SUCCESS| " dpdklab
2024-09-25 14:59 ` dpdklab
2024-09-25 15:04 ` dpdklab
2024-09-25 15:19 ` |FAILURE| pw144429 [PATCH dpdk] mbuf: fix strict aliasing error in allocator 0-day Robot
2024-09-25 15:19 ` |SUCCESS| pw144429 [PATCH] mbuf: fix strict aliasing error in alloca dpdklab
2024-09-25 15:23 ` dpdklab [this message]
2024-09-25 15:24 ` dpdklab
2024-09-25 15:40 ` |PENDING| " dpdklab
2024-09-25 15:59 ` |SUCCESS| " dpdklab
2024-09-25 15:59 ` dpdklab
2024-09-25 16:05 ` dpdklab
2024-09-25 17:20 ` 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=66f42afc.170a0220.3be304.9862SMTPIN_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).