From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142002-142003 [PATCH] [v1,2/2] baseband/acc: improvement
Date: Mon, 01 Jul 2024 19:21:02 -0700 (PDT) [thread overview]
Message-ID: <6683640e.050a0220.497d7.61f7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240701223424.427588-3-nicolas.chautru@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142003
_Testing pending_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Monday, July 01 2024 22:34:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e195680f6f1c109cd7812b1ef6f2a38cea70ea9b
142002-142003 --> testing pending
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PEND | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PEND | PASS | PEND |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1 | PEND | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30366/
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-07-02 2:21 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701223424.427588-3-nicolas.chautru@intel.com>
2024-07-01 22:08 ` |SUCCESS| pw142002-142003 [PATCH v1 2/2] baseband/acc: improvement to logging mechanism qemudev
2024-07-01 22:12 ` qemudev
2024-07-01 22:35 ` |SUCCESS| pw142003 " checkpatch
2024-07-01 23:25 ` |FAILURE| " 0-day Robot
2024-07-02 2:06 ` |SUCCESS| pw142002-142003 [PATCH] [v1,2/2] baseband/acc: improvement dpdklab
2024-07-02 2:10 ` dpdklab
2024-07-02 2:10 ` dpdklab
2024-07-02 2:13 ` |PENDING| " dpdklab
2024-07-02 2:13 ` |SUCCESS| " dpdklab
2024-07-02 2:14 ` dpdklab
2024-07-02 2:20 ` dpdklab
2024-07-02 2:20 ` dpdklab
2024-07-02 2:21 ` dpdklab [this message]
2024-07-02 2:21 ` |PENDING| " dpdklab
2024-07-02 2:22 ` dpdklab
2024-07-02 2:24 ` dpdklab
2024-07-02 2:26 ` |SUCCESS| " dpdklab
2024-07-02 2:26 ` dpdklab
2024-07-02 2:33 ` dpdklab
2024-07-02 2:36 ` |PENDING| " dpdklab
2024-07-02 2:38 ` |SUCCESS| " dpdklab
2024-07-02 2:43 ` dpdklab
2024-07-02 2:45 ` dpdklab
2024-07-02 2:47 ` |PENDING| " dpdklab
2024-07-02 2:52 ` |WARNING| " dpdklab
2024-07-02 2:53 ` |SUCCESS| " dpdklab
2024-07-02 2:54 ` |PENDING| " dpdklab
2024-07-02 3:05 ` |SUCCESS| " dpdklab
2024-07-02 3:11 ` |WARNING| " dpdklab
2024-07-02 3:12 ` dpdklab
2024-07-02 3:18 ` dpdklab
2024-07-02 3:20 ` dpdklab
2024-07-02 3:27 ` dpdklab
2024-07-02 3:35 ` |PENDING| " dpdklab
2024-07-02 3:35 ` dpdklab
2024-07-02 3:37 ` |WARNING| " dpdklab
2024-07-02 3:39 ` |PENDING| " dpdklab
2024-07-02 3:40 ` |WARNING| " dpdklab
2024-07-02 3:42 ` |PENDING| " dpdklab
2024-07-02 3:42 ` |WARNING| " dpdklab
2024-07-02 3:44 ` dpdklab
2024-07-02 3:44 ` dpdklab
2024-07-02 3:44 ` |PENDING| " dpdklab
2024-07-02 3:47 ` |WARNING| " dpdklab
2024-07-02 3:51 ` |PENDING| " dpdklab
2024-07-02 3:54 ` |WARNING| " dpdklab
2024-07-02 3:58 ` |PENDING| " dpdklab
2024-07-02 3:59 ` dpdklab
2024-07-02 4:00 ` dpdklab
2024-07-02 4:06 ` dpdklab
2024-07-02 4:07 ` dpdklab
2024-07-02 4:07 ` |WARNING| " dpdklab
2024-07-02 4:10 ` |PENDING| " dpdklab
2024-07-02 4:11 ` dpdklab
2024-07-02 4:15 ` |SUCCESS| " dpdklab
2024-07-02 4:15 ` dpdklab
2024-07-02 5:39 ` |PENDING| " dpdklab
2024-07-02 5:40 ` dpdklab
2024-07-02 5:40 ` dpdklab
2024-07-02 5:45 ` dpdklab
2024-07-02 5:47 ` dpdklab
2024-07-02 5:51 ` dpdklab
2024-07-02 5:52 ` dpdklab
2024-07-02 5:53 ` dpdklab
2024-07-02 5:54 ` dpdklab
2024-07-02 5:56 ` dpdklab
2024-07-02 5:59 ` dpdklab
2024-07-02 6:05 ` dpdklab
2024-07-02 6:06 ` dpdklab
2024-07-02 6:06 ` dpdklab
2024-07-02 6:12 ` dpdklab
2024-07-02 6:14 ` dpdklab
2024-07-02 6:15 ` dpdklab
2024-07-02 6:16 ` dpdklab
2024-07-02 6:19 ` dpdklab
2024-07-02 6:21 ` dpdklab
2024-07-02 6:25 ` dpdklab
2024-07-02 6:29 ` dpdklab
2024-07-02 6:31 ` dpdklab
2024-07-02 6:32 ` dpdklab
2024-07-02 6:33 ` dpdklab
2024-07-02 6:37 ` dpdklab
2024-07-02 6:40 ` dpdklab
2024-07-02 6:43 ` |SUCCESS| " dpdklab
2024-07-02 6:44 ` |PENDING| " dpdklab
2024-07-02 6:51 ` dpdklab
2024-07-02 6:58 ` dpdklab
2024-07-02 6:59 ` dpdklab
2024-07-02 7:05 ` dpdklab
2024-07-02 7:42 ` dpdklab
2024-07-02 7:46 ` dpdklab
2024-07-02 8:08 ` |SUCCESS| " dpdklab
2024-07-02 9:30 ` |PENDING| " dpdklab
2024-07-02 9:32 ` dpdklab
2024-07-02 9:40 ` dpdklab
2024-07-02 9:41 ` dpdklab
2024-07-02 9:46 ` dpdklab
2024-07-02 9:48 ` dpdklab
2024-07-02 9:54 ` dpdklab
2024-07-02 10:07 ` dpdklab
2024-07-02 10:20 ` dpdklab
2024-07-02 10:27 ` dpdklab
2024-07-02 10:32 ` dpdklab
2024-07-02 10:43 ` dpdklab
2024-07-02 10:48 ` dpdklab
2024-07-02 10:52 ` dpdklab
2024-07-02 10:56 ` dpdklab
2024-07-02 11:00 ` |SUCCESS| " dpdklab
2024-07-02 15:12 ` dpdklab
2024-07-02 16:34 ` dpdklab
2024-07-02 16:48 ` dpdklab
2024-07-02 16:57 ` 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=6683640e.050a0220.497d7.61f7SMTPIN_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).