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| pw142713 [PATCH] eal/linux: clear asan after allocation an
Date: Thu, 25 Jul 2024 06:12:19 -0700 (PDT)	[thread overview]
Message-ID: <66a24f33.050a0220.3e52f.1b77SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723083419.12435-1-amichon@kalrayinc.com>

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

_Testing pending_

Submitter: Alex Michon <amichon@kalrayinc.com>
Date: Tuesday, July 23 2024 08:34:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43

142713 --> testing pending

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

Test environment and result as below:

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


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

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

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-25 13:16 UTC|newest]

Thread overview: 120+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240723083419.12435-1-amichon@kalrayinc.com>
2024-07-25  7:06 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation and before prefaulting qemudev
2024-07-25  7:11 ` qemudev
2024-07-25  7:25 ` checkpatch
2024-07-25  8:52 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation an dpdklab
2024-07-25  8:56 ` dpdklab
2024-07-25  8:58 ` dpdklab
2024-07-25  9:01 ` dpdklab
2024-07-25  9:01 ` dpdklab
2024-07-25  9:11 ` dpdklab
2024-07-25  9:14 ` dpdklab
2024-07-25  9:15 ` dpdklab
2024-07-25  9:19 ` dpdklab
2024-07-25 10:07 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation and before prefaulting qemudev
2024-07-25 10:08 ` qemudev
2024-07-25 10:19 ` |PENDING| pw142713 [PATCH] eal/linux: clear asan after allocation an dpdklab
2024-07-25 10:22 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation and before prefaulting qemudev
2024-07-25 10:23 ` qemudev
2024-07-25 10:24 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation an dpdklab
2024-07-25 10:25 ` |PENDING| " dpdklab
2024-07-25 10:26 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation and before prefaulting qemudev
2024-07-25 10:27 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation an dpdklab
2024-07-25 10:27 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation and before prefaulting qemudev
2024-07-25 10:29 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation an dpdklab
2024-07-25 10:30 ` |PENDING| " dpdklab
2024-07-25 10:31 ` dpdklab
2024-07-25 10:31 ` dpdklab
2024-07-25 10:32 ` dpdklab
2024-07-25 10:35 ` |SUCCESS| " dpdklab
2024-07-25 10:42 ` |SUCCESS| pw142713 [PATCH] eal/linux: clear asan after allocation and before prefaulting qemudev
2024-07-25 10:42 ` qemudev
2024-07-25 10:46 ` |PENDING| pw142713 [PATCH] eal/linux: clear asan after allocation an dpdklab
2024-07-25 10:46 ` dpdklab
2024-07-25 10:47 ` dpdklab
2024-07-25 10:48 ` dpdklab
2024-07-25 10:49 ` dpdklab
2024-07-25 10:54 ` dpdklab
2024-07-25 10:55 ` dpdklab
2024-07-25 10:56 ` dpdklab
2024-07-25 10:56 ` dpdklab
2024-07-25 10:58 ` |SUCCESS| " dpdklab
2024-07-25 11:07 ` |PENDING| " dpdklab
2024-07-25 11:11 ` |SUCCESS| " dpdklab
2024-07-25 11:14 ` dpdklab
2024-07-25 11:17 ` dpdklab
2024-07-25 12:48 ` |PENDING| " dpdklab
2024-07-25 12:54 ` dpdklab
2024-07-25 13:02 ` dpdklab
2024-07-25 13:08 ` dpdklab
2024-07-25 13:12 ` dpdklab [this message]
2024-07-25 13:22 ` dpdklab
2024-07-25 13:22 ` |SUCCESS| " dpdklab
2024-07-25 13:46 ` |PENDING| " dpdklab
2024-07-25 13:49 ` dpdklab
2024-07-25 13:59 ` dpdklab
2024-07-25 14:22 ` dpdklab
2024-07-25 14:24 ` dpdklab
2024-07-25 14:26 ` dpdklab
2024-07-25 14:30 ` dpdklab
2024-07-25 14:31 ` dpdklab
2024-07-25 14:34 ` dpdklab
2024-07-25 14:41 ` dpdklab
2024-07-25 14:41 ` dpdklab
2024-07-25 14:49 ` dpdklab
2024-07-25 14:49 ` dpdklab
2024-07-25 14:52 ` dpdklab
2024-07-25 14:55 ` dpdklab
2024-07-25 15:00 ` dpdklab
2024-07-25 15:00 ` dpdklab
2024-07-25 15:21 ` dpdklab
2024-07-25 15:23 ` dpdklab
2024-07-25 15:25 ` dpdklab
2024-07-25 15:26 ` dpdklab
2024-07-25 15:28 ` dpdklab
2024-07-25 15:29 ` dpdklab
2024-07-25 15:30 ` dpdklab
2024-07-25 15:31 ` dpdklab
2024-07-25 15:31 ` dpdklab
2024-07-25 15:31 ` dpdklab
2024-07-25 15:33 ` dpdklab
2024-07-25 15:36 ` dpdklab
2024-07-25 15:36 ` dpdklab
2024-07-25 15:37 ` dpdklab
2024-07-25 15:46 ` dpdklab
2024-07-25 15:46 ` dpdklab
2024-07-25 15:46 ` dpdklab
2024-07-25 15:50 ` dpdklab
2024-07-25 15:50 ` dpdklab
2024-07-25 15:54 ` dpdklab
2024-07-25 15:59 ` dpdklab
2024-07-25 16:01 ` dpdklab
2024-07-25 16:02 ` dpdklab
2024-07-25 16:03 ` dpdklab
2024-07-25 16:05 ` dpdklab
2024-07-25 16:07 ` dpdklab
2024-07-25 16:10 ` dpdklab
2024-07-25 16:10 ` dpdklab
2024-07-25 16:12 ` |SUCCESS| " dpdklab
2024-07-25 16:22 ` |PENDING| " dpdklab
2024-07-25 16:24 ` dpdklab
2024-07-25 16:26 ` dpdklab
2024-07-25 16:27 ` |SUCCESS| " dpdklab
2024-07-25 16:27 ` |PENDING| " dpdklab
2024-07-25 16:28 ` dpdklab
2024-07-25 16:29 ` dpdklab
2024-07-25 16:30 ` dpdklab
2024-07-25 16:32 ` dpdklab
2024-07-25 16:33 ` dpdklab
2024-07-25 16:35 ` dpdklab
2024-07-25 16:38 ` dpdklab
2024-07-25 16:43 ` dpdklab
2024-07-25 16:43 ` dpdklab
2024-07-25 16:50 ` dpdklab
2024-07-25 16:50 ` dpdklab
2024-07-25 16:50 ` dpdklab
2024-07-25 16:55 ` dpdklab
2024-07-25 16:55 ` dpdklab
2024-07-25 17:00 ` dpdklab
2024-07-25 17:01 ` dpdklab
2024-07-25 17:01 ` dpdklab
2024-07-25 17:17 ` |SUCCESS| " 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=66a24f33.050a0220.3e52f.1b77SMTPIN_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).