From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw148951 [PATCH] [v4,1/1] usertools/devbind: allow changin
Date: Mon, 02 Dec 2024 02:39:32 -0800 (PST) [thread overview]
Message-ID: <674d8e64.050a0220.c7440.5981SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <c5d0388620157638338f67291f8862c6c96cec96.1733131888.git.anatoly.burakov@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/148951
_Testing pending_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Monday, December 02 2024 09:31:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1b3bf1128d9bda5595861814792f74b8f57160c8
148951 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#340117
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM) | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PEND |
+------------------------------------+--------------------+
| Fedora 40 (ARM) | PEND |
+------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | PEND |
+------------------------------------+--------------------+
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: Depends on container host
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32065/
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-12-02 10:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c5d0388620157638338f67291f8862c6c96cec96.1733131888.git.anatoly.burakov@intel.com>
2024-12-02 9:01 ` |SUCCESS| pw148951 [PATCH v4 1/1] usertools/devbind: allow changing UID/GID for VFIO qemudev
2024-12-02 9:05 ` qemudev
2024-12-02 9:32 ` |WARNING| " checkpatch
2024-12-02 10:22 ` |SUCCESS| " 0-day Robot
2024-12-02 10:28 ` |SUCCESS| pw148951 [PATCH] [v4,1/1] usertools/devbind: allow changin dpdklab
2024-12-02 10:35 ` dpdklab
2024-12-02 10:36 ` dpdklab
2024-12-02 10:39 ` dpdklab [this message]
2024-12-02 10:42 ` dpdklab
2024-12-02 10:45 ` dpdklab
2024-12-02 10:47 ` dpdklab
2024-12-02 10:57 ` dpdklab
2024-12-02 11:06 ` dpdklab
2024-12-02 11:18 ` dpdklab
2024-12-02 11:22 ` dpdklab
2024-12-02 11:25 ` |WARNING| " dpdklab
2024-12-02 11:26 ` |SUCCESS| " dpdklab
2024-12-02 12: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=674d8e64.050a0220.c7440.5981SMTPIN_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).