From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136940 [PATCH] [RFC] eal: increase maximum number of fil
Date: Tue, 20 Feb 2024 17:36:40 -0800 (PST) [thread overview]
Message-ID: <65d553a8.170a0220.bcb50.63e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136940
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 20 2024 23:09:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0033e92f4697add2772a6e459dcb55a1962ee80c
136940 --> testing pass
Test environment and result as below:
+--------------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+==========================+================+==============+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM Clang) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | 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 Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29200/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-21 1:36 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 1:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 15:11 dpdklab
2024-02-21 8:22 dpdklab
2024-02-21 8:15 dpdklab
2024-02-21 7:35 dpdklab
2024-02-21 7:16 dpdklab
2024-02-21 6:47 dpdklab
2024-02-21 5:31 dpdklab
2024-02-21 2:30 dpdklab
2024-02-21 2:04 dpdklab
2024-02-21 2:02 dpdklab
2024-02-21 1:40 dpdklab
2024-02-21 1:37 dpdklab
2024-02-21 1:34 dpdklab
2024-02-21 1:31 dpdklab
2024-02-21 1:27 dpdklab
2024-02-21 1:26 dpdklab
2024-02-21 1:24 dpdklab
2024-02-21 1:14 dpdklab
2024-02-21 0:55 dpdklab
2024-02-21 0:51 dpdklab
2024-02-21 0:37 dpdklab
2024-02-21 0:37 dpdklab
2024-02-21 0:33 dpdklab
2024-02-21 0:32 dpdklab
2024-02-21 0:31 dpdklab
2024-02-21 0:28 dpdklab
2024-02-21 0:28 dpdklab
2024-02-21 0:27 dpdklab
2024-02-21 0:26 dpdklab
2024-02-21 0:25 dpdklab
2024-02-21 0:25 dpdklab
2024-02-21 0:24 dpdklab
2024-02-21 0:23 dpdklab
2024-02-21 0:21 dpdklab
2024-02-21 0:20 dpdklab
2024-02-21 0:19 dpdklab
2024-02-21 0:19 dpdklab
2024-02-21 0:16 dpdklab
2024-02-21 0:15 dpdklab
2024-02-21 0:12 dpdklab
2024-02-21 0:10 dpdklab
2024-02-21 0:05 dpdklab
2024-02-21 0:05 dpdklab
2024-02-21 0:04 dpdklab
2024-02-21 0:04 dpdklab
2024-02-21 0:03 dpdklab
2024-02-21 0:03 dpdklab
2024-02-21 0:01 dpdklab
2024-02-21 0:01 dpdklab
2024-02-21 0:01 dpdklab
2024-02-20 23:59 dpdklab
2024-02-20 23:57 dpdklab
2024-02-20 23:53 dpdklab
2024-02-20 23:52 dpdklab
2024-02-20 23:51 dpdklab
2024-02-20 23:51 dpdklab
2024-02-20 23:50 dpdklab
2024-02-20 23:50 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=65d553a8.170a0220.bcb50.63e1SMTPIN_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).