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| pw142668 [PATCH] [v2] doc: announce rte_ipsec API changes
Date: Tue, 23 Jul 2024 19:09:52 -0700 (PDT)	[thread overview]
Message-ID: <66a06270.170a0220.e097e.26f5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723133706.2150828-1-asasidharan@marvell.com>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142668

_Testing pending_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Tuesday, July 23 2024 13:37:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92439dc9ac51529de448f4484864e2ef7b1bc07c

142668 --> testing pending

Upstream job id: Windows-Compile-DPDK-Mingw64#20965

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.3        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PEND               | PASS                 |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PEND               | PASS                 |
+---------------------+--------------------+----------------------+


FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-24  2:09 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240723133706.2150828-1-asasidharan@marvell.com>
2024-07-23 13:10 ` |SUCCESS| pw142668 [PATCH v2] " qemudev
2024-07-23 13:15 ` qemudev
2024-07-23 13:37 ` checkpatch
2024-07-23 14:23 ` 0-day Robot
2024-07-23 23:53 ` |SUCCESS| pw142668 [PATCH] [v2] " dpdklab
2024-07-23 23:56 ` dpdklab
2024-07-24  0:00 ` dpdklab
2024-07-24  0:01 ` dpdklab
2024-07-24  0:09 ` dpdklab
2024-07-24  0:13 ` dpdklab
2024-07-24  0:15 ` dpdklab
2024-07-24  0:33 ` dpdklab
2024-07-24  0:36 ` |PENDING| " dpdklab
2024-07-24  0:46 ` dpdklab
2024-07-24  0:46 ` dpdklab
2024-07-24  0:49 ` dpdklab
2024-07-24  0:51 ` |SUCCESS| " dpdklab
2024-07-24  0:53 ` |PENDING| " dpdklab
2024-07-24  0:56 ` dpdklab
2024-07-24  0:59 ` dpdklab
2024-07-24  0:59 ` dpdklab
2024-07-24  1:01 ` dpdklab
2024-07-24  1:02 ` dpdklab
2024-07-24  1:05 ` dpdklab
2024-07-24  1:06 ` |SUCCESS| " dpdklab
2024-07-24  1:09 ` |PENDING| " dpdklab
2024-07-24  1:13 ` dpdklab
2024-07-24  1:14 ` |SUCCESS| " dpdklab
2024-07-24  1:21 ` |PENDING| " dpdklab
2024-07-24  1:23 ` dpdklab
2024-07-24  1:24 ` |SUCCESS| " dpdklab
2024-07-24  1:35 ` dpdklab
2024-07-24  1:40 ` dpdklab
2024-07-24  1:44 ` dpdklab
2024-07-24  1:49 ` dpdklab
2024-07-24  1:50 ` |PENDING| " dpdklab
2024-07-24  1:51 ` dpdklab
2024-07-24  1:52 ` dpdklab
2024-07-24  1:53 ` dpdklab
2024-07-24  1:53 ` dpdklab
2024-07-24  1:56 ` dpdklab
2024-07-24  2:00 ` dpdklab
2024-07-24  2:02 ` dpdklab
2024-07-24  2:03 ` dpdklab
2024-07-24  2:03 ` dpdklab
2024-07-24  2:03 ` dpdklab
2024-07-24  2:04 ` dpdklab
2024-07-24  2:04 ` dpdklab
2024-07-24  2:05 ` dpdklab
2024-07-24  2:05 ` dpdklab
2024-07-24  2:07 ` dpdklab
2024-07-24  2:07 ` dpdklab
2024-07-24  2:09 ` dpdklab [this message]
2024-07-24  2:09 ` dpdklab
2024-07-24  2:10 ` dpdklab
2024-07-24  2:11 ` dpdklab
2024-07-24  2:15 ` |SUCCESS| " dpdklab
2024-07-24  2:16 ` dpdklab
2024-07-24  2:17 ` dpdklab
2024-07-24  2:17 ` |PENDING| " dpdklab
2024-07-24  2:18 ` dpdklab
2024-07-24  2:22 ` dpdklab
2024-07-24  2:23 ` dpdklab
2024-07-24  2:23 ` dpdklab
2024-07-24  2:24 ` dpdklab
2024-07-24  2:27 ` dpdklab
2024-07-24  2:27 ` dpdklab
2024-07-24  2:30 ` dpdklab
2024-07-24  2:30 ` dpdklab
2024-07-24  2:32 ` |SUCCESS| " dpdklab
2024-07-24  2:32 ` |PENDING| " dpdklab
2024-07-24  2:33 ` |SUCCESS| " dpdklab
2024-07-24  2:33 ` |PENDING| " dpdklab
2024-07-24  2:34 ` dpdklab
2024-07-24  2:34 ` dpdklab
2024-07-24  2:34 ` |SUCCESS| " dpdklab
2024-07-24  2:36 ` |PENDING| " dpdklab
2024-07-24  2:37 ` |SUCCESS| " dpdklab
2024-07-24  2:38 ` dpdklab
2024-07-24  2:40 ` |PENDING| " dpdklab
2024-07-24  2:41 ` dpdklab
2024-07-24  2:42 ` dpdklab
2024-07-24  2:43 ` dpdklab
2024-07-24  2:43 ` dpdklab
2024-07-24  2:44 ` dpdklab
2024-07-24  2:47 ` dpdklab
2024-07-24  2:48 ` dpdklab
2024-07-24  2:48 ` dpdklab
2024-07-24  2:49 ` dpdklab
2024-07-24  2:49 ` dpdklab
2024-07-24  2:50 ` dpdklab
2024-07-24  2:50 ` dpdklab
2024-07-24  2:50 ` dpdklab
2024-07-24  2:51 ` dpdklab
2024-07-24  2:51 ` dpdklab
2024-07-24  2:51 ` dpdklab
2024-07-24  2:51 ` dpdklab
2024-07-24  2:51 ` dpdklab
2024-07-24  2:54 ` dpdklab
2024-07-24  2:54 ` dpdklab
2024-07-24  2:55 ` dpdklab
2024-07-24  2:57 ` dpdklab
2024-07-24  2:58 ` dpdklab
2024-07-24  2:59 ` dpdklab
2024-07-24  2:59 ` dpdklab
2024-07-24  3:00 ` dpdklab
2024-07-24  3:02 ` dpdklab
2024-07-24  3:02 ` dpdklab
2024-07-24  3:05 ` dpdklab
2024-07-24  3:07 ` dpdklab
2024-07-24  3:07 ` dpdklab
2024-07-24  3:17 ` |SUCCESS| " dpdklab
2024-07-24  3:29 ` |PENDING| " dpdklab
2024-07-24  3:52 ` dpdklab
2024-07-24  4:08 ` dpdklab
2024-07-24  4:11 ` |SUCCESS| " dpdklab
2024-07-25 11:20 ` 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=66a06270.170a0220.e097e.26f5SMTPIN_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).