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| pw140526-140534 [PATCH] [v2,17/17] net/ntnic: add NIM modu
Date: Fri, 31 May 2024 09:57:59 -0700 (PDT)	[thread overview]
Message-ID: <665a0197.630a0220.93b3a.5a60SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240531154731.1856874-17-sil-plv@napatech.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140534

_Testing PASS_

Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Friday, May 31 2024 15:47:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2dbb63594a9a985e2c8639b57f9fcd1468b9de97

140526-140534 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+


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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-31 16:58 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240531154731.1856874-17-sil-plv@napatech.com>
2024-05-31 15:25 ` |SUCCESS| pw140526-140534 [PATCH v2 17/17] net/ntnic: add NIM module qemudev
2024-05-31 15:30 ` qemudev
2024-05-31 15:55 ` |SUCCESS| pw140534 " checkpatch
2024-05-31 16:30 ` |FAILURE| pw140526-140534 [PATCH] [v2,17/17] net/ntnic: add NIM modu dpdklab
2024-05-31 16:30 ` |SUCCESS| " dpdklab
2024-05-31 16:30 ` dpdklab
2024-05-31 16:31 ` dpdklab
2024-05-31 16:31 ` dpdklab
2024-05-31 16:31 ` dpdklab
2024-05-31 16:31 ` dpdklab
2024-05-31 16:31 ` dpdklab
2024-05-31 16:32 ` dpdklab
2024-05-31 16:32 ` dpdklab
2024-05-31 16:32 ` |FAILURE| " dpdklab
2024-05-31 16:32 ` dpdklab
2024-05-31 16:33 ` |SUCCESS| " dpdklab
2024-05-31 16:33 ` dpdklab
2024-05-31 16:33 ` |FAILURE| " dpdklab
2024-05-31 16:34 ` dpdklab
2024-05-31 16:34 ` |SUCCESS| " dpdklab
2024-05-31 16:34 ` dpdklab
2024-05-31 16:34 ` dpdklab
2024-05-31 16:34 ` |FAILURE| " dpdklab
2024-05-31 16:35 ` |SUCCESS| " dpdklab
2024-05-31 16:35 ` dpdklab
2024-05-31 16:36 ` dpdklab
2024-05-31 16:36 ` |FAILURE| " dpdklab
2024-05-31 16:37 ` |SUCCESS| " dpdklab
2024-05-31 16:37 ` dpdklab
2024-05-31 16:37 ` dpdklab
2024-05-31 16:37 ` dpdklab
2024-05-31 16:37 ` dpdklab
2024-05-31 16:37 ` dpdklab
2024-05-31 16:37 ` dpdklab
2024-05-31 16:38 ` dpdklab
2024-05-31 16:38 ` dpdklab
2024-05-31 16:38 ` dpdklab
2024-05-31 16:38 ` dpdklab
2024-05-31 16:38 ` dpdklab
2024-05-31 16:38 ` dpdklab
2024-05-31 16:39 ` |FAILURE| " dpdklab
2024-05-31 16:40 ` |SUCCESS| " dpdklab
2024-05-31 16:40 ` dpdklab
2024-05-31 16:40 ` dpdklab
2024-05-31 16:40 ` dpdklab
2024-05-31 16:40 ` |FAILURE| " dpdklab
2024-05-31 16:41 ` |SUCCESS| " dpdklab
2024-05-31 16:41 ` |FAILURE| " dpdklab
2024-05-31 16:43 ` dpdklab
2024-05-31 16:43 ` |SUCCESS| pw140534 [PATCH v2 17/17] net/ntnic: add NIM module 0-day Robot
2024-05-31 16:44 ` |FAILURE| pw140526-140534 [PATCH] [v2,17/17] net/ntnic: add NIM modu dpdklab
2024-05-31 16:45 ` dpdklab
2024-05-31 16:45 ` |SUCCESS| " dpdklab
2024-05-31 16:46 ` dpdklab
2024-05-31 16:48 ` dpdklab
2024-05-31 16:50 ` dpdklab
2024-05-31 16:51 ` |FAILURE| " dpdklab
2024-05-31 16:53 ` |SUCCESS| " dpdklab
2024-05-31 16:55 ` |FAILURE| " dpdklab
2024-05-31 16:56 ` dpdklab
2024-05-31 16:57 ` dpdklab [this message]
2024-05-31 16:59 ` dpdklab
2024-05-31 17:01 ` |SUCCESS| " dpdklab
2024-05-31 17:02 ` |FAILURE| " dpdklab
2024-05-31 17:02 ` |SUCCESS| " dpdklab
2024-05-31 17:02 ` |FAILURE| " dpdklab
2024-05-31 17:03 ` dpdklab
2024-05-31 17:03 ` dpdklab
2024-05-31 17:05 ` |SUCCESS| " dpdklab
2024-05-31 17:05 ` |FAILURE| " dpdklab
2024-05-31 17:06 ` |SUCCESS| " dpdklab
2024-05-31 17:09 ` |FAILURE| " dpdklab
2024-05-31 17:09 ` dpdklab
2024-05-31 17:10 ` dpdklab
2024-05-31 17:10 ` dpdklab
2024-05-31 17:10 ` |SUCCESS| " dpdklab
2024-05-31 17:10 ` |FAILURE| " dpdklab
2024-05-31 17:11 ` dpdklab
2024-05-31 17:11 ` dpdklab
2024-05-31 17:13 ` |SUCCESS| " dpdklab
2024-05-31 17:13 ` |FAILURE| " dpdklab
2024-05-31 17:17 ` dpdklab
2024-05-31 17:19 ` dpdklab
2024-05-31 17:20 ` dpdklab
2024-05-31 17:21 ` dpdklab
2024-05-31 17:22 ` dpdklab
2024-05-31 17:24 ` dpdklab
2024-05-31 17:25 ` dpdklab
2024-05-31 17:26 ` dpdklab
2024-05-31 17:27 ` dpdklab
2024-05-31 17:28 ` dpdklab
2024-05-31 17:32 ` dpdklab
2024-05-31 17:43 ` dpdklab
2024-05-31 17:43 ` dpdklab
2024-05-31 17:44 ` |SUCCESS| " dpdklab
2024-05-31 17:46 ` |FAILURE| " 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=665a0197.630a0220.93b3a.5a60SMTPIN_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).