From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw148475 [PATCH] eal/linux: redefine the name for rte_fbar
Date: Thu, 14 Nov 2024 13:42:54 -0800 (PST) [thread overview]
Message-ID: <67366ede.050a0220.38805a.0490SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_B09D0FCCA142E4AE5ABFE584E92DCED8CB0A@qq.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/148475
_Testing pending_
Submitter: Congjie Zhou <zcjie0802@qq.com>
Date: Thursday, November 14 2024 08:37:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148475 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#291785
Test environment and result as below:
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Environment | dpdk_unit_test | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+=======================+================+==============+===========================+==============================+
| CentOS Stream 9 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora 39 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm) | PEND | SKIPPED | PEND | PEND |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora 39 (ARM Clang) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora 40 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora 40 (ARM Clang) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| RHEL9 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 22.04 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 20.04 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 24.04 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------+----------------+--------------+---------------------------+------------------------------+
CentOS Stream 9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 39 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Ubuntu 22.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31930/
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-11-14 21:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_B09D0FCCA142E4AE5ABFE584E92DCED8CB0A@qq.com>
2024-11-14 8:05 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init() qemudev
2024-11-14 8:09 ` qemudev
2024-11-14 8:39 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init checkpatch
2024-11-14 11:05 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init() 0-day Robot
2024-11-14 14:40 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbar dpdklab
2024-11-14 14:42 ` dpdklab
2024-11-14 14:50 ` dpdklab
2024-11-14 15:26 ` dpdklab
2024-11-14 16:00 ` dpdklab
2024-11-14 17:08 ` dpdklab
2024-11-14 17:15 ` dpdklab
2024-11-14 20:17 ` dpdklab
2024-11-14 21:00 ` dpdklab
2024-11-14 21:09 ` dpdklab
2024-11-14 21:42 ` dpdklab [this message]
2024-11-14 22:53 ` |PENDING| " dpdklab
2024-11-14 23:25 ` |WARNING| " dpdklab
2024-11-15 0:54 ` |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=67366ede.050a0220.38805a.0490SMTPIN_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).