automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Visa Hankala <visa@hankala.org>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130049 [PATCH] net/bonding: Fix header for C++
Date: Thu, 10 Aug 2023 07:30:47 -0700 (PDT)	[thread overview]
Message-ID: <64d4f497.a70a0220.c1c07.60dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130049

_Testing PASS_

Submitter: Visa Hankala <visa@hankala.org>
Date: Wednesday, August 09 2023 15:52:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130049 --> testing pass

Test environment and result as below:

+--------------------------+----------------+---------------------------+
|       Environment        | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| Windows Server 2019      | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Debian Bullseye          | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM)    | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Fedora 37 (ARM)          | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Debian 11 (Buster) (ARM) | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Debian Buster            | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9          | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM)          | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Debian 11                | SKIPPED        | PASS                      |
+--------------------------+----------------+---------------------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Debian 11
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-10 14:30 UTC|newest]

Thread overview: 101+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 14:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14  1:57 dpdklab
2023-08-14  1:54 dpdklab
2023-08-14  1:45 dpdklab
2023-08-14  1:42 dpdklab
2023-08-14  1:41 dpdklab
2023-08-14  1:41 dpdklab
2023-08-14  1:41 dpdklab
2023-08-14  1:40 dpdklab
2023-08-14  1:39 dpdklab
2023-08-14  1:38 dpdklab
2023-08-14  1:35 dpdklab
2023-08-14  1:34 dpdklab
2023-08-13 21:57 dpdklab
2023-08-13 19:14 dpdklab
2023-08-11 21:35 dpdklab
2023-08-11 20:15 dpdklab
2023-08-11 20:13 dpdklab
2023-08-11 20:12 dpdklab
2023-08-11 20:11 dpdklab
2023-08-11 20:09 dpdklab
2023-08-11 20:09 dpdklab
2023-08-11 20:06 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:04 dpdklab
2023-08-11  8:10 dpdklab
2023-08-11  4:35 dpdklab
2023-08-11  4:34 dpdklab
2023-08-11  4:34 dpdklab
2023-08-11  4:33 dpdklab
2023-08-11  4:31 dpdklab
2023-08-11  4:30 dpdklab
2023-08-11  4:28 dpdklab
2023-08-11  4:25 dpdklab
2023-08-11  4:22 dpdklab
2023-08-11  4:20 dpdklab
2023-08-11  4:20 dpdklab
2023-08-11  4:15 dpdklab
2023-08-11  4:12 dpdklab
2023-08-11  4:10 dpdklab
2023-08-11  3:58 dpdklab
2023-08-11  3:57 dpdklab
2023-08-11  3:56 dpdklab
2023-08-11  3:47 dpdklab
2023-08-11  2:59 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:42 dpdklab
2023-08-11  2:41 dpdklab
2023-08-11  2:41 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:39 dpdklab
2023-08-11  2:29 dpdklab
2023-08-11  2:26 dpdklab
2023-08-11  2:24 dpdklab
2023-08-11  2:20 dpdklab
2023-08-11  2:01 dpdklab
2023-08-10 16:11 dpdklab
2023-08-10 15:54 dpdklab
2023-08-10 15:30 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:06 dpdklab
2023-08-10 14:57 dpdklab
2023-08-10 14:56 dpdklab
2023-08-10 14:38 dpdklab
2023-08-10 14:36 dpdklab
2023-08-10 14:31 dpdklab
2023-08-10 14:31 dpdklab
2023-08-10 14:31 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
     [not found] <hxLTO3XMJ2hUmnvx@hankala.org>
2023-08-09 15:41 ` qemudev
2023-08-09 15:46 ` qemudev
2023-08-09 15:54 ` checkpatch
2023-08-09 16:39 ` 0-day Robot

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=64d4f497.a70a0220.c1c07.60dfSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=visa@hankala.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).