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| pw137363 [PATCH] lib/hash: add SipHash function
Date: Tue, 27 Feb 2024 16:26:40 -0800 (PST)	[thread overview]
Message-ID: <65de7dc0.0d0a0220.912a4.f9c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227174012.343004-1-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 27 2024 17:39:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137363 --> testing pass

Test environment and result as below:

+------------------+--------------------+
|   Environment    | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13.2     | PASS               |
+------------------+--------------------+
| Debian 12 (arm)  | PASS               |
+------------------+--------------------+
| CentOS Stream 9  | PASS               |
+------------------+--------------------+
| Fedora 37        | PASS               |
+------------------+--------------------+
| CentOS Stream 8  | PASS               |
+------------------+--------------------+
| Ubuntu 20.04     | PASS               |
+------------------+--------------------+
| openSUSE Leap 15 | PASS               |
+------------------+--------------------+
| Fedora 38        | PASS               |
+------------------+--------------------+
| Debian Bullseye  | PASS               |
+------------------+--------------------+
| RHEL8            | PASS               |
+------------------+--------------------+
| Alpine           | PASS               |
+------------------+--------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

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

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28  0:26 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227174012.343004-1-stephen@networkplumber.org>
2024-02-27 17:40 ` |WARNING| " checkpatch
2024-02-27 17:41 ` |FAILURE| " qemudev
2024-02-27 18:44 ` 0-day Robot
2024-02-27 20:01 ` |SUCCESS| " dpdklab
2024-02-27 20:24 ` dpdklab
2024-02-27 20:37 ` dpdklab
2024-02-27 20:43 ` dpdklab
2024-02-27 20:44 ` dpdklab
2024-02-27 20:48 ` dpdklab
2024-02-27 20:52 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-28  0:25 ` |FAILURE| " dpdklab
2024-02-28  0:25 ` dpdklab
2024-02-28  0:25 ` dpdklab
2024-02-28  0:25 ` |SUCCESS| " dpdklab
2024-02-28  0:25 ` |FAILURE| " dpdklab
2024-02-28  0:26 ` dpdklab
2024-02-28  0:26 ` dpdklab
2024-02-28  0:26 ` dpdklab [this message]
2024-02-28  0:26 ` dpdklab
2024-02-28  0:27 ` |SUCCESS| " dpdklab
2024-02-28  0:27 ` dpdklab
2024-02-28  0:30 ` |FAILURE| " dpdklab
2024-02-28  0:31 ` |SUCCESS| " dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:32 ` dpdklab
2024-02-28  0:34 ` dpdklab
2024-02-28  0:35 ` dpdklab
2024-02-28  0:35 ` dpdklab
2024-02-28  0:38 ` |FAILURE| " dpdklab
2024-02-28  0:44 ` dpdklab
2024-02-28  0:44 ` |SUCCESS| " dpdklab
2024-02-28  0:45 ` dpdklab
2024-02-28  0:46 ` dpdklab
2024-02-28  0:46 ` |FAILURE| " dpdklab
2024-02-28  0:48 ` |SUCCESS| " dpdklab
2024-02-28  0:48 ` |FAILURE| " dpdklab
2024-02-28  0:49 ` |SUCCESS| " dpdklab
2024-02-28  0:56 ` |FAILURE| " dpdklab
2024-02-28  0:56 ` dpdklab
2024-02-28  0:57 ` dpdklab
2024-02-28  0:57 ` |SUCCESS| " dpdklab
2024-02-28  0:59 ` |FAILURE| " dpdklab
2024-02-28  1:11 ` dpdklab
2024-02-28  1:16 ` |SUCCESS| " dpdklab
2024-02-28  1:27 ` dpdklab
2024-02-28  1:28 ` dpdklab
2024-02-28  2:22 ` dpdklab
2024-02-28  3:48 ` dpdklab
2024-02-28  9:04 ` dpdklab
2024-02-28 11:45 ` dpdklab
2024-02-28 11:46 ` dpdklab
2024-02-28 18:23 ` dpdklab
2024-02-29  9:14 ` 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=65de7dc0.0d0a0220.912a4.f9c5SMTPIN_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).