From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130044 [PATCH] app: fix silent enqueue fail in test_mbuf
Date: Thu, 10 Aug 2023 09:11:17 -0700 (PDT) [thread overview]
Message-ID: <64d50c25.170a0220.57802.ee10SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130044
_Testing PASS_
Submitter: jhascoet <ju.hascoet@gmail.com>
Date: Wednesday, August 09 2023 14:14:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130044 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+--------------------+
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27264/
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-10 16:11 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 16:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 2:10 dpdklab
2023-08-14 2:03 dpdklab
2023-08-14 1:59 dpdklab
2023-08-14 1:58 dpdklab
2023-08-14 1:57 dpdklab
2023-08-14 1:57 dpdklab
2023-08-14 1:57 dpdklab
2023-08-14 1:54 dpdklab
2023-08-14 1:51 dpdklab
2023-08-14 1:50 dpdklab
2023-08-14 1:48 dpdklab
2023-08-13 22:13 dpdklab
2023-08-13 19:16 dpdklab
2023-08-11 22:59 dpdklab
2023-08-11 21:42 dpdklab
2023-08-11 21:42 dpdklab
2023-08-11 21:41 dpdklab
2023-08-11 21:39 dpdklab
2023-08-11 21:38 dpdklab
2023-08-11 21:38 dpdklab
2023-08-11 21:30 dpdklab
2023-08-11 21:11 dpdklab
2023-08-11 8:37 dpdklab
2023-08-11 5:29 dpdklab
2023-08-11 5:26 dpdklab
2023-08-11 5:23 dpdklab
2023-08-11 5:14 dpdklab
2023-08-11 5:00 dpdklab
2023-08-11 5:00 dpdklab
2023-08-11 5:00 dpdklab
2023-08-11 4:59 dpdklab
2023-08-11 4:59 dpdklab
2023-08-11 4:59 dpdklab
2023-08-11 4:58 dpdklab
2023-08-11 4:34 dpdklab
2023-08-11 4:23 dpdklab
2023-08-11 4:22 dpdklab
2023-08-11 4:19 dpdklab
2023-08-11 4:18 dpdklab
2023-08-11 4:13 dpdklab
2023-08-11 4:12 dpdklab
2023-08-11 4:12 dpdklab
2023-08-11 4:12 dpdklab
2023-08-11 4:08 dpdklab
2023-08-11 4:08 dpdklab
2023-08-11 4:07 dpdklab
2023-08-11 4:05 dpdklab
2023-08-11 4:02 dpdklab
2023-08-11 4:02 dpdklab
2023-08-11 4:01 dpdklab
2023-08-11 4:00 dpdklab
2023-08-11 3:59 dpdklab
2023-08-11 3:59 dpdklab
2023-08-11 3:59 dpdklab
2023-08-11 3:58 dpdklab
2023-08-11 3:58 dpdklab
2023-08-11 3:58 dpdklab
2023-08-11 3:58 dpdklab
2023-08-11 3:57 dpdklab
2023-08-11 2:26 dpdklab
2023-08-10 18:06 dpdklab
2023-08-10 16:59 dpdklab
2023-08-10 16:57 dpdklab
2023-08-10 16:56 dpdklab
2023-08-10 16:56 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:54 dpdklab
2023-08-10 16:53 dpdklab
2023-08-10 16:51 dpdklab
2023-08-10 16:51 dpdklab
2023-08-10 16:51 dpdklab
2023-08-10 16:48 dpdklab
2023-08-10 16:47 dpdklab
2023-08-10 16:45 dpdklab
2023-08-10 16:40 dpdklab
2023-08-10 16:28 dpdklab
2023-08-10 16:21 dpdklab
2023-08-10 16:20 dpdklab
2023-08-10 16:19 dpdklab
2023-08-10 16:11 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:02 dpdklab
2023-08-10 16:01 dpdklab
2023-08-10 15:54 dpdklab
2023-08-10 15:53 dpdklab
2023-08-10 15:52 dpdklab
2023-08-10 15:50 dpdklab
2023-08-10 15:50 dpdklab
2023-08-10 15:44 dpdklab
2023-08-10 15:42 dpdklab
2023-08-10 15:42 dpdklab
2023-08-10 15:41 dpdklab
2023-08-10 15:41 dpdklab
2023-08-10 15:31 dpdklab
2023-08-10 15:29 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:16 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=64d50c25.170a0220.57802.ee10SMTPIN_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).