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| pw143857-143855 [PATCH] [v6,6/6] eal: extend bitops to han
Date: Tue, 10 Sep 2024 19:24:46 -0700 (PDT)	[thread overview]
Message-ID: <66e0ff6e.050a0220.89e52.f5d7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240910083139.699291-7-mattias.ronnblom@ericsson.com>

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

_Testing PASS_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Tuesday, September 10 2024 08:31:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143857-143855 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#22103

Test environment and result as below:

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


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

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

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

UNH-IOL DPDK Community Lab

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

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

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240910083139.699291-7-mattias.ronnblom@ericsson.com>
2024-09-10  8:16 ` |SUCCESS| pw143857-143855 [PATCH v6 6/6] eal: extend bitops to handle volatile pointers qemudev
2024-09-10  8:21 ` qemudev
2024-09-10  8:43 ` |WARNING| pw143855 " checkpatch
2024-09-10  9:45 ` |FAILURE| " 0-day Robot
2024-09-10 23:20 ` |SUCCESS| pw143857-143855 [PATCH] [v6,6/6] eal: extend bitops to han dpdklab
2024-09-10 23:40 ` dpdklab
2024-09-11  0:18 ` dpdklab
2024-09-11  2:24 ` dpdklab [this message]
2024-09-11  2:35 ` |PENDING| " dpdklab
2024-09-11  2:56 ` dpdklab
2024-09-11  3:20 ` |SUCCESS| " dpdklab
2024-09-11  3:46 ` |PENDING| " dpdklab
2024-09-11  4:17 ` |SUCCESS| " dpdklab
2024-09-11  5:09 ` dpdklab
2024-09-11  8:58 ` dpdklab
2024-09-11  9:04 ` dpdklab
2024-09-11  9:09 ` dpdklab
2024-09-11  9:10 ` dpdklab
2024-09-11  9:30 ` dpdklab
2024-09-11  9:34 ` dpdklab
2024-09-11  9:34 ` dpdklab
2024-09-11  9:35 ` dpdklab
2024-09-11  9:54 ` dpdklab
2024-09-15 22:59 ` dpdklab
2024-09-16  4:51 ` 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=66e0ff6e.050a0220.89e52.f5d7SMTPIN_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).