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| [GIT MASTER] bd6c7e80fc799c2840a7fcaac4748baa337099e2
Date: Tue, 17 Sep 2024 18:35:29 -0700 (PDT)	[thread overview]
Message-ID: <66ea2e61.250a0220.16091c.d733SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: dpdk-next-crypto

bd6c7e80fc799c2840a7fcaac4748baa337099e2 --> testing pending

Upstream job id: Generic-Unit-Test-DPDK#263531

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PEND           |
+---------------------+----------------+
| Debian Bullseye     | PEND           |
+---------------------+----------------+
| Debian 12           | PEND           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

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

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30633/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-09-18  1:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  1:35 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-18  2:41 dpdklab
2024-09-18  1:46 dpdklab
2024-09-18  1:28 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=66ea2e61.250a0220.16091c.d733SMTPIN_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).