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| pw139809-139812 [PATCH] [v2,5/5] baseband/acc: cosmetic lo
Date: Fri, 03 May 2024 00:59:11 -0700 (PDT)	[thread overview]
Message-ID: <6634994f.d40a0220.55b23.7a04SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240502204548.236729-6-hernan.vargas@intel.com>

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

_Testing PASS_

Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Thursday, May 02 2024 20:45:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:98b4ecb4e4d73e93fdfa53f552b48d71104b445f

139809-139812 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.0        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


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

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

FreeBSD 14.0
	Kernel: 14.0
	Compiler: clang 16.0.6

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/29903/

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-03  7:59 UTC|newest]

Thread overview: 179+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240502204548.236729-6-hernan.vargas@intel.com>
2024-05-02 20:28 ` |SUCCESS| pw139809-139812 [PATCH v2 5/5] baseband/acc: cosmetic log changes qemudev
2024-05-02 20:32 ` qemudev
2024-05-02 21:43 ` |SUCCESS| pw139812 " 0-day Robot
2024-05-03  6:53 ` |SUCCESS| pw139809-139812 [PATCH] [v2,5/5] baseband/acc: cosmetic lo dpdklab
2024-05-03  6:56 ` dpdklab
2024-05-03  6:59 ` dpdklab
2024-05-03  7:16 ` dpdklab
2024-05-03  7:28 ` dpdklab
2024-05-03  7:42 ` dpdklab
2024-05-03  7:51 ` dpdklab
2024-05-03  7:54 ` dpdklab
2024-05-03  7:57 ` dpdklab
2024-05-03  7:59 ` dpdklab [this message]
2024-05-03  7:59 ` dpdklab
2024-05-03  8:01 ` dpdklab
2024-05-03  8:15 ` dpdklab
2024-05-03  8:17 ` dpdklab
2024-05-03  8:18 ` dpdklab
2024-05-03  8:19 ` |SUCCESS| pw139812 [PATCH v2 5/5] baseband/acc: cosmetic log changes checkpatch
2024-05-03  8:21 ` |SUCCESS| pw139809-139812 [PATCH] [v2,5/5] baseband/acc: cosmetic lo dpdklab
2024-05-03  8:25 ` dpdklab
2024-05-03  8:26 ` dpdklab
2024-05-03  8:28 ` dpdklab
2024-05-03  8:28 ` dpdklab
2024-05-03  8:29 ` dpdklab
2024-05-03  8:30 ` dpdklab
2024-05-03  8:31 ` dpdklab
2024-05-03  8:32 ` dpdklab
2024-05-03  8:36 ` dpdklab
2024-05-03  8:36 ` dpdklab
2024-05-03  8:37 ` dpdklab
2024-05-03  8:37 ` dpdklab
2024-05-03  8:38 ` dpdklab
2024-05-03  8:38 ` dpdklab
2024-05-03  8:39 ` dpdklab
2024-05-03  8:40 ` dpdklab
2024-05-03  8:43 ` dpdklab
2024-05-03  8:44 ` dpdklab
2024-05-03  8:45 ` dpdklab
2024-05-03  8:46 ` dpdklab
2024-05-03  8:47 ` dpdklab
2024-05-03  8:48 ` dpdklab
2024-05-03  8:48 ` dpdklab
2024-05-03  8:49 ` dpdklab
2024-05-03  8:50 ` dpdklab
2024-05-03  8:50 ` dpdklab
2024-05-03  8:50 ` dpdklab
2024-05-03  8:51 ` dpdklab
2024-05-03  8:52 ` dpdklab
2024-05-03  8:52 ` dpdklab
2024-05-03  8:52 ` dpdklab
2024-05-03  8:54 ` dpdklab
2024-05-03  8:54 ` dpdklab
2024-05-03  8:54 ` dpdklab
2024-05-03  8:55 ` dpdklab
2024-05-03  8:56 ` dpdklab
2024-05-03  8:56 ` dpdklab
2024-05-03  8:56 ` dpdklab
2024-05-03  8:57 ` dpdklab
2024-05-03  8:57 ` dpdklab
2024-05-03  8:57 ` dpdklab
2024-05-03  8:58 ` dpdklab
2024-05-03  8:58 ` dpdklab
2024-05-03  9:02 ` dpdklab
2024-05-03  9:05 ` dpdklab
2024-05-03  9:11 ` dpdklab
2024-05-03  9:12 ` dpdklab
2024-05-03  9:13 ` dpdklab
2024-05-03  9:14 ` dpdklab
2024-05-03  9:14 ` dpdklab
2024-05-03  9:14 ` dpdklab
2024-05-03  9:16 ` dpdklab
2024-05-03  9:16 ` dpdklab
2024-05-03  9:17 ` dpdklab
2024-05-03  9:17 ` dpdklab
2024-05-03  9:18 ` dpdklab
2024-05-03  9:18 ` dpdklab
2024-05-03  9:19 ` dpdklab
2024-05-03  9:19 ` dpdklab
2024-05-03  9:20 ` dpdklab
2024-05-03  9:20 ` dpdklab
2024-05-03  9:20 ` dpdklab
2024-05-03  9:20 ` dpdklab
2024-05-03  9:21 ` dpdklab
2024-05-03  9:23 ` dpdklab
2024-05-03  9:31 ` dpdklab
2024-05-03  9:31 ` dpdklab
2024-05-03  9:31 ` dpdklab
2024-05-03  9:31 ` dpdklab
2024-05-03  9:31 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:32 ` dpdklab
2024-05-03  9:33 ` dpdklab
2024-05-03  9:33 ` dpdklab
2024-05-03  9:37 ` dpdklab
2024-05-03  9:37 ` dpdklab
2024-05-03  9:37 ` dpdklab
2024-05-03  9:38 ` dpdklab
2024-05-03  9:38 ` dpdklab
2024-05-03  9:38 ` dpdklab
2024-05-03  9:38 ` dpdklab
2024-05-03  9:38 ` dpdklab
2024-05-03  9:38 ` dpdklab
2024-05-03  9:39 ` dpdklab
2024-05-03  9:39 ` dpdklab
2024-05-03  9:39 ` dpdklab
2024-05-03  9:40 ` dpdklab
2024-05-03  9:40 ` dpdklab
2024-05-03  9:40 ` dpdklab
2024-05-03  9:41 ` dpdklab
2024-05-03  9:45 ` dpdklab
2024-05-03  9:46 ` dpdklab
2024-05-03  9:46 ` dpdklab
2024-05-03  9:47 ` dpdklab
2024-05-03  9:47 ` dpdklab
2024-05-03  9:47 ` dpdklab
2024-05-03  9:49 ` dpdklab
2024-05-03  9:49 ` |SUCCESS| pw139812 [PATCH v2 5/5] baseband/acc: cosmetic log changes checkpatch
2024-05-03  9:50 ` |SUCCESS| pw139809-139812 [PATCH] [v2,5/5] baseband/acc: cosmetic lo dpdklab
2024-05-03  9:50 ` dpdklab
2024-05-03  9:50 ` dpdklab
2024-05-03  9:50 ` dpdklab
2024-05-03  9:51 ` dpdklab
2024-05-03  9:51 ` dpdklab
2024-05-03  9:52 ` dpdklab
2024-05-03  9:52 ` dpdklab
2024-05-03  9:52 ` dpdklab
2024-05-03  9:52 ` dpdklab
2024-05-03  9:56 ` |SUCCESS| pw139812 [PATCH v2 5/5] baseband/acc: cosmetic log changes checkpatch
2024-05-03 10:01 ` |SUCCESS| pw139809-139812 [PATCH] [v2,5/5] baseband/acc: cosmetic lo dpdklab
2024-05-03 10:04 ` dpdklab
2024-05-03 10:05 ` dpdklab
2024-05-03 10:06 ` dpdklab
2024-05-03 10:09 ` dpdklab
2024-05-03 10:10 ` dpdklab
2024-05-03 10:11 ` dpdklab
2024-05-03 10:13 ` dpdklab
2024-05-03 10:16 ` dpdklab
2024-05-03 10:16 ` dpdklab
2024-05-03 10:17 ` dpdklab
2024-05-03 10:19 ` dpdklab
2024-05-03 10:19 ` dpdklab
2024-05-03 10:22 ` dpdklab
2024-05-03 10:26 ` dpdklab
2024-05-03 10:28 ` dpdklab
2024-05-03 10:29 ` dpdklab
2024-05-03 10:31 ` dpdklab
2024-05-03 10:34 ` dpdklab
2024-05-03 10:48 ` dpdklab
2024-05-03 10:48 ` dpdklab
2024-05-03 11:01 ` dpdklab
2024-05-03 11:02 ` dpdklab
2024-05-03 11:09 ` dpdklab
2024-05-03 11:36 ` dpdklab
2024-05-03 11:49 ` dpdklab
2024-05-03 12:11 ` dpdklab
2024-05-03 12:24 ` dpdklab
2024-05-03 12:47 ` dpdklab
2024-05-03 12:51 ` dpdklab
2024-05-03 13:41 ` dpdklab
2024-05-03 18:40 ` dpdklab
2024-05-03 19:28 ` dpdklab
2024-05-05  3:47 ` dpdklab
2024-05-05  3:51 ` dpdklab
2024-05-05  3:57 ` dpdklab
2024-05-05  4:02 ` dpdklab
2024-05-05  4:41 ` dpdklab
2024-05-05  5:10 ` dpdklab
2024-05-05  5:43 ` dpdklab
2024-05-05  5:48 ` dpdklab
2024-05-05  6:08 ` dpdklab
2024-05-05  6:13 ` dpdklab
2024-05-06 10:51 ` dpdklab
2024-05-06 11:05 ` 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=6634994f.d40a0220.55b23.7a04SMTPIN_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).