From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw143405-143413 [PATCH] [v3,9/9] member: use accelerated C
Date: Tue, 27 Aug 2024 11:30:31 -0700 (PDT) [thread overview]
Message-ID: <66ce1b47.170a0220.dfc60.c963SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240827153650.53170-5-daniel.gregory@bytedance.com>
Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/143413
_Testing pending_
Submitter: Daniel Gregory <daniel.gregory@bytedance.com>
Date: Tuesday, August 27 2024 15:36:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143405-143413 --> testing pending
Upstream job id: Generic-VM-Unit-Test-DPDK#25019
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PEND |
+---------------------+----------------+
| Debian Bullseye | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Debian 12 | PEND |
+---------------------+----------------+
| Fedora 38 | PEND |
+---------------------+----------------+
| Fedora 38 (Clang) | PEND |
+---------------------+----------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30864/
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-08-27 18:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240827153650.53170-5-daniel.gregory@bytedance.com>
2024-08-27 15:10 ` |SUCCESS| pw143405-143413 [PATCH v3 9/9] member: use accelerated CRC on riscv qemudev
2024-08-27 15:15 ` qemudev
2024-08-27 15:38 ` |SUCCESS| pw143413 " checkpatch
2024-08-27 17:04 ` 0-day Robot
2024-08-27 18:05 ` |PENDING| pw143405-143413 [PATCH] [v3,9/9] member: use accelerated C dpdklab
2024-08-27 18:20 ` |SUCCESS| " dpdklab
2024-08-27 18:22 ` dpdklab
2024-08-27 18:23 ` dpdklab
2024-08-27 18:23 ` |PENDING| " dpdklab
2024-08-27 18:24 ` |SUCCESS| " dpdklab
2024-08-27 18:30 ` dpdklab [this message]
2024-08-27 18:30 ` dpdklab
2024-08-27 18:40 ` dpdklab
2024-08-27 18:40 ` dpdklab
2024-08-27 18:48 ` dpdklab
2024-08-27 19:01 ` dpdklab
2024-08-27 19:03 ` dpdklab
2024-08-27 19:05 ` dpdklab
2024-08-27 19:13 ` dpdklab
2024-08-27 19:37 ` dpdklab
2024-08-27 20:18 ` dpdklab
2024-09-19 22:51 ` dpdklab
2024-09-19 23:11 ` 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=66ce1b47.170a0220.dfc60.c963SMTPIN_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).