From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142218 [PATCH] vhost: fix offset while mmaping log base
Date: Mon, 08 Jul 2024 13:07:09 -0700 (PDT) [thread overview]
Message-ID: <668c46ed.050a0220.bd136.1359SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240708065749.1131-1-xiangwencheng@dayudpu.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142218
_Testing pending_
Submitter: BillXiang <xiangwencheng@dayudpu.com>
Date: Monday, July 08 2024 06:57:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36
142218 --> 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 | PASS | PEND | 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/30458/
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-08 20:07 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240708065749.1131-1-xiangwencheng@dayudpu.com>
2024-07-08 12:49 ` |SUCCESS| pw142218 [PATCH] vhost: fix offset while mmaping log base address qemudev
2024-07-08 12:54 ` qemudev
2024-07-08 13:13 ` checkpatch
2024-07-08 19:56 ` |SUCCESS| pw142218 [PATCH] vhost: fix offset while mmaping log base dpdklab
2024-07-08 19:57 ` dpdklab
2024-07-08 20:00 ` dpdklab
2024-07-08 20:00 ` dpdklab
2024-07-08 20:02 ` dpdklab
2024-07-08 20:05 ` dpdklab
2024-07-08 20:06 ` dpdklab
2024-07-08 20:06 ` |PENDING| " dpdklab
2024-07-08 20:07 ` dpdklab [this message]
2024-07-08 20:08 ` |SUCCESS| " dpdklab
2024-07-08 20:09 ` |PENDING| " dpdklab
2024-07-08 20:09 ` |SUCCESS| " dpdklab
2024-07-08 20:10 ` |PENDING| " dpdklab
2024-07-08 20:10 ` dpdklab
2024-07-08 20:10 ` dpdklab
2024-07-08 20:15 ` |SUCCESS| " dpdklab
2024-07-08 20:16 ` dpdklab
2024-07-08 20:19 ` dpdklab
2024-07-08 20:23 ` |PENDING| " dpdklab
2024-07-08 20:24 ` |SUCCESS| " dpdklab
2024-07-08 20:29 ` dpdklab
2024-07-08 20:30 ` |PENDING| " dpdklab
2024-07-08 20:42 ` |SUCCESS| " dpdklab
2024-07-08 20:56 ` |PENDING| " dpdklab
2024-07-08 20:58 ` dpdklab
2024-07-08 21:11 ` dpdklab
2024-07-08 21:13 ` dpdklab
2024-07-08 21:16 ` dpdklab
2024-07-08 21:21 ` dpdklab
2024-07-08 21:21 ` dpdklab
2024-07-08 21:24 ` dpdklab
2024-07-08 21:27 ` dpdklab
2024-07-08 21:28 ` dpdklab
2024-07-08 21:30 ` dpdklab
2024-07-08 21:35 ` dpdklab
2024-07-08 21:37 ` dpdklab
2024-07-08 21:42 ` dpdklab
2024-07-08 21:42 ` dpdklab
2024-07-08 21:43 ` dpdklab
2024-07-08 21:43 ` dpdklab
2024-07-08 21:52 ` dpdklab
2024-07-08 21:54 ` dpdklab
2024-07-08 21:55 ` dpdklab
2024-07-08 21:55 ` dpdklab
2024-07-08 21:55 ` dpdklab
2024-07-08 21:56 ` dpdklab
2024-07-08 21:59 ` |SUCCESS| " dpdklab
2024-07-08 22:02 ` |PENDING| " dpdklab
2024-07-08 22:07 ` dpdklab
2024-07-08 22:10 ` dpdklab
2024-07-08 22:11 ` dpdklab
2024-07-08 22:12 ` dpdklab
2024-07-08 22:18 ` dpdklab
2024-07-08 22:21 ` dpdklab
2024-07-08 22:26 ` dpdklab
2024-07-08 22:28 ` dpdklab
2024-07-08 22:28 ` dpdklab
2024-07-08 22:30 ` dpdklab
2024-07-08 22:32 ` dpdklab
2024-07-08 22:33 ` dpdklab
2024-07-08 22:35 ` dpdklab
2024-07-08 22:37 ` dpdklab
2024-07-08 22:38 ` dpdklab
2024-07-08 22:39 ` dpdklab
2024-07-08 22:40 ` dpdklab
2024-07-08 22:41 ` dpdklab
2024-07-08 22:43 ` dpdklab
2024-07-08 22:45 ` dpdklab
2024-07-08 22:47 ` dpdklab
2024-07-08 22:49 ` dpdklab
2024-07-08 22:51 ` dpdklab
2024-07-08 22:52 ` dpdklab
2024-07-08 22:52 ` dpdklab
2024-07-08 22:53 ` dpdklab
2024-07-08 22:55 ` |SUCCESS| " dpdklab
2024-07-08 23:01 ` dpdklab
2024-07-08 23:18 ` |PENDING| " dpdklab
2024-07-09 0:06 ` dpdklab
2024-07-09 0:11 ` dpdklab
2024-07-09 0:11 ` dpdklab
2024-07-09 0:19 ` dpdklab
2024-07-09 0:21 ` dpdklab
2024-07-09 0:30 ` dpdklab
2024-07-09 0:37 ` dpdklab
2024-07-09 0:38 ` dpdklab
2024-07-09 0:45 ` dpdklab
2024-07-09 0:46 ` dpdklab
2024-07-09 0:52 ` dpdklab
2024-07-09 0:54 ` dpdklab
2024-07-09 1:00 ` dpdklab
2024-07-09 1:01 ` dpdklab
2024-07-09 1:03 ` dpdklab
2024-07-09 1:06 ` dpdklab
2024-07-09 1:08 ` dpdklab
2024-07-09 1:14 ` dpdklab
2024-07-09 1:15 ` dpdklab
2024-07-09 1:16 ` dpdklab
2024-07-09 1:33 ` dpdklab
2024-07-09 1:41 ` dpdklab
2024-07-09 1:45 ` dpdklab
2024-07-09 1:47 ` dpdklab
2024-07-09 1:53 ` dpdklab
2024-07-09 1:56 ` |SUCCESS| " dpdklab
2024-07-09 2:09 ` |PENDING| " dpdklab
2024-07-09 2:09 ` dpdklab
2024-07-09 2:18 ` dpdklab
2024-07-09 2:26 ` dpdklab
2024-07-09 2:35 ` dpdklab
2024-07-09 2:41 ` |SUCCESS| " dpdklab
2024-07-09 19:09 ` dpdklab
2024-07-09 19:25 ` dpdklab
2024-07-09 19:37 ` dpdklab
2024-07-13 19:17 ` dpdklab
2024-07-14 9:59 ` dpdklab
2024-07-14 16:35 ` dpdklab
2024-07-15 7:47 ` dpdklab
2024-07-15 7:54 ` 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=668c46ed.050a0220.bd136.1359SMTPIN_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).