automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw145761 [PATCH] [v2] eal/x86: cache queried CPU flags
Date: Sun, 13 Oct 2024 18:51:15 -0700 (PDT)	[thread overview]
Message-ID: <670c7913.050a0220.369e80.3494SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241011133303.1496014-1-bruce.richardson@intel.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/145761

_Testing pending_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, October 11 2024 13:33:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:98613d32e3dac58d685f4f236cf8cc9733abaaf3

145761 --> testing pending

Upstream job id: Generic-VM-Unit-Test-DPDK#25649

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PEND           |
+---------------------+----------------+
| Debian Bullseye     | PEND           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Fedora 37           | PEND           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+


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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31435/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

      parent reply	other threads:[~2024-10-14  1:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241011133303.1496014-1-bruce.richardson@intel.com>
2024-10-11 13:10 ` |SUCCESS| pw145761 [PATCH v2] " qemudev
2024-10-11 13:15 ` qemudev
2024-10-11 13:34 ` checkpatch
2024-10-11 14:43 ` 0-day Robot
2024-10-13 22:19 ` |SUCCESS| pw145761 [PATCH] [v2] " dpdklab
2024-10-13 22:27 ` dpdklab
2024-10-13 22:27 ` dpdklab
2024-10-13 22:30 ` dpdklab
2024-10-13 22:39 ` dpdklab
2024-10-13 23:28 ` dpdklab
2024-10-13 23:33 ` dpdklab
2024-10-13 23:33 ` dpdklab
2024-10-13 23:53 ` dpdklab
2024-10-13 23:55 ` dpdklab
2024-10-14  1:39 ` |PENDING| " dpdklab
2024-10-14  1:51 ` dpdklab [this message]

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=670c7913.050a0220.369e80.3494SMTPIN_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).