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| pw140026 [PATCH] bpf: don't verify classic bpfs
Date: Mon, 13 May 2024 05:47:56 -0700 (PDT)	[thread overview]
Message-ID: <66420bfc.050a0220.77966.2801SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240512055545.98297-1-yoav.w@claroty.com>

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

_Testing PASS_

Submitter: Yoav Winstein <yoav.w@claroty.com>
Date: Sunday, May 12 2024 05:55:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

140026 --> testing pass

Test environment and result as below:

+---------------------+-------------------+--------------------+----------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+===================+====================+======================+
| Windows Server 2022 | PASS              | PASS               | PASS                 |
+---------------------+-------------------+--------------------+----------------------+
| FreeBSD 13.3        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| FreeBSD 14.0        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED           | PASS               | PASS                 |
+---------------------+-------------------+--------------------+----------------------+
| CentOS Stream 8     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| CentOS Stream 9     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Debian 12           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Fedora 39           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Fedora 38           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| openSUSE Leap 15    | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Ubuntu 22.04        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| RHEL8               | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Fedora 37           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Ubuntu 20.04        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Debian Bullseye     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+


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

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

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)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

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

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-13 12:47 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240512055545.98297-1-yoav.w@claroty.com>
2024-05-12  5:31 ` qemudev
2024-05-12  5:36 ` qemudev
2024-05-12  5:56 ` |WARNING| " checkpatch
2024-05-12  6:44 ` |FAILURE| " 0-day Robot
2024-05-13 11:50 ` |SUCCESS| " dpdklab
2024-05-13 11:52 ` dpdklab
2024-05-13 11:53 ` dpdklab
2024-05-13 11:54 ` dpdklab
2024-05-13 11:54 ` dpdklab
2024-05-13 12:00 ` dpdklab
2024-05-13 12:01 ` |WARNING| " dpdklab
2024-05-13 12:02 ` dpdklab
2024-05-13 12:02 ` |SUCCESS| " dpdklab
2024-05-13 12:02 ` |WARNING| " dpdklab
2024-05-13 12:25 ` dpdklab
2024-05-13 12:27 ` dpdklab
2024-05-13 12:27 ` |SUCCESS| " dpdklab
2024-05-13 12:28 ` dpdklab
2024-05-13 12:28 ` dpdklab
2024-05-13 12:29 ` dpdklab
2024-05-13 12:29 ` dpdklab
2024-05-13 12:30 ` dpdklab
2024-05-13 12:30 ` |WARNING| " dpdklab
2024-05-13 12:30 ` |SUCCESS| " dpdklab
2024-05-13 12:30 ` dpdklab
2024-05-13 12:31 ` dpdklab
2024-05-13 12:31 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:33 ` |WARNING| " dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:36 ` dpdklab
2024-05-13 12:36 ` |SUCCESS| " dpdklab
2024-05-13 12:38 ` dpdklab
2024-05-13 12:44 ` dpdklab
2024-05-13 12:45 ` dpdklab
2024-05-13 12:45 ` dpdklab
2024-05-13 12:46 ` dpdklab
2024-05-13 12:46 ` |WARNING| " dpdklab
2024-05-13 12:47 ` |SUCCESS| " dpdklab
2024-05-13 12:47 ` |WARNING| " dpdklab
2024-05-13 12:47 ` |SUCCESS| " dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:47 ` dpdklab
2024-05-13 12:47 ` dpdklab [this message]
2024-05-13 12:48 ` dpdklab
2024-05-13 12:48 ` dpdklab
2024-05-13 12:48 ` |WARNING| " dpdklab
2024-05-13 12:48 ` |SUCCESS| " dpdklab
2024-05-13 12:48 ` dpdklab
2024-05-13 12:49 ` dpdklab
2024-05-13 12:50 ` dpdklab
2024-05-13 12:58 ` dpdklab
2024-05-13 12:59 ` dpdklab
2024-05-13 13:00 ` dpdklab
2024-05-13 13:00 ` dpdklab
2024-05-13 13:01 ` dpdklab
2024-05-13 13:02 ` dpdklab
2024-05-13 13:03 ` dpdklab
2024-05-13 13:04 ` dpdklab
2024-05-13 13:05 ` dpdklab
2024-05-13 13:06 ` dpdklab
2024-05-13 13:07 ` dpdklab
2024-05-13 13:12 ` dpdklab
2024-05-13 13:13 ` dpdklab
2024-05-13 13:14 ` dpdklab
2024-05-13 13:14 ` dpdklab
2024-05-13 13:18 ` dpdklab
2024-05-13 13:18 ` dpdklab
2024-05-13 13:20 ` dpdklab
2024-05-13 13:21 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:22 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:24 ` dpdklab
2024-05-13 13:25 ` dpdklab
2024-05-13 13:25 ` dpdklab
2024-05-13 13:32 ` dpdklab
2024-05-13 13:33 ` dpdklab
2024-05-13 13:37 ` dpdklab
2024-05-13 13:37 ` dpdklab
2024-05-13 13:40 ` dpdklab
2024-05-13 13:44 ` dpdklab
2024-05-13 13:48 ` dpdklab
2024-05-13 14:09 ` 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=66420bfc.050a0220.77966.2801SMTPIN_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).