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: |SUCCESS| pw136331-136332 [PATCH] [v3,2/2] doc: remove outdated vers
Date: Fri, 02 Feb 2024 06:47:48 -0800 (PST)	[thread overview]
Message-ID: <65bd0094.a70a0220.992cf.41adSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136332

_Testing PASS_

Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Friday, February 02 2024 14:04:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2b551097b3443ebf662e4d140600a4c9b108e73c

136331-136332 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-02 14:47 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 14:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02 20:41 dpdklab
2024-02-02 20:10 dpdklab
2024-02-02 16:08 dpdklab
2024-02-02 16:07 dpdklab
2024-02-02 16:04 dpdklab
2024-02-02 16:04 dpdklab
2024-02-02 16:00 dpdklab
2024-02-02 15:43 dpdklab
2024-02-02 15:23 dpdklab
2024-02-02 15:20 dpdklab
2024-02-02 15:18 dpdklab
2024-02-02 15:17 dpdklab
2024-02-02 15:13 dpdklab
2024-02-02 15:12 dpdklab
2024-02-02 15:11 dpdklab
2024-02-02 15:10 dpdklab
2024-02-02 15:08 dpdklab
2024-02-02 15:08 dpdklab
2024-02-02 15:08 dpdklab
2024-02-02 15:06 dpdklab
2024-02-02 15:04 dpdklab
2024-02-02 15:03 dpdklab
2024-02-02 15:02 dpdklab
2024-02-02 15:02 dpdklab
2024-02-02 15:01 dpdklab
2024-02-02 15:00 dpdklab
2024-02-02 15:00 dpdklab
2024-02-02 14:59 dpdklab
2024-02-02 14:58 dpdklab
2024-02-02 14:57 dpdklab
2024-02-02 14:57 dpdklab
2024-02-02 14:56 dpdklab
2024-02-02 14:56 dpdklab
2024-02-02 14:55 dpdklab
2024-02-02 14:54 dpdklab
2024-02-02 14:53 dpdklab
2024-02-02 14:52 dpdklab
2024-02-02 14:52 dpdklab
2024-02-02 14:52 dpdklab
2024-02-02 14:52 dpdklab
2024-02-02 14:51 dpdklab
2024-02-02 14:49 dpdklab
2024-02-02 14:49 dpdklab
2024-02-02 14:48 dpdklab
2024-02-02 14:46 dpdklab
2024-02-02 14:46 dpdklab
2024-02-02 14:45 dpdklab
2024-02-02 14:45 dpdklab
2024-02-02 14:44 dpdklab
2024-02-02 14:44 dpdklab
2024-02-02 14:44 dpdklab
2024-02-02 14:43 dpdklab
2024-02-02 14:43 dpdklab
2024-02-02 14:43 dpdklab
2024-02-02 14:42 dpdklab
2024-02-02 14:42 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=65bd0094.a70a0220.992cf.41adSMTPIN_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).