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| pw135072 [PATCH] crytodev: make logtype internal
Date: Tue, 12 Dec 2023 20:44:54 -0800 (PST)	[thread overview]
Message-ID: <657936c6.0c0a0220.1679b.448fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135072

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, December 12 2023 16:41:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

135072 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-13  4:44 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  4:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-13  8:52 dpdklab
2023-12-13  7:38 dpdklab
2023-12-13  7:23 dpdklab
2023-12-13  7:16 dpdklab
2023-12-13  7:15 dpdklab
2023-12-13  6:47 dpdklab
2023-12-13  6:42 dpdklab
2023-12-13  6:40 dpdklab
2023-12-13  6:40 dpdklab
2023-12-13  6:40 dpdklab
2023-12-13  6:40 dpdklab
2023-12-13  6:36 dpdklab
2023-12-13  6:35 dpdklab
2023-12-13  6:35 dpdklab
2023-12-13  6:33 dpdklab
2023-12-13  6:25 dpdklab
2023-12-13  6:19 dpdklab
2023-12-13  6:13 dpdklab
2023-12-13  6:13 dpdklab
2023-12-13  6:11 dpdklab
2023-12-13  6:11 dpdklab
2023-12-13  6:10 dpdklab
2023-12-13  6:10 dpdklab
2023-12-13  6:06 dpdklab
2023-12-13  6:05 dpdklab
2023-12-13  6:04 dpdklab
2023-12-13  6:03 dpdklab
2023-12-13  6:01 dpdklab
2023-12-13  6:00 dpdklab
2023-12-13  5:59 dpdklab
2023-12-13  5:58 dpdklab
2023-12-13  5:58 dpdklab
2023-12-13  5:56 dpdklab
2023-12-13  5:56 dpdklab
2023-12-13  5:56 dpdklab
2023-12-13  5:55 dpdklab
2023-12-13  5:55 dpdklab
2023-12-13  5:40 dpdklab
2023-12-13  5:38 dpdklab
2023-12-13  5:38 dpdklab
2023-12-13  5:37 dpdklab
2023-12-13  5:37 dpdklab
2023-12-13  5:37 dpdklab
2023-12-13  5:36 dpdklab
2023-12-13  5:35 dpdklab
2023-12-13  5:35 dpdklab
2023-12-13  5:35 dpdklab
2023-12-13  5:34 dpdklab
2023-12-13  5:33 dpdklab
2023-12-13  5:26 dpdklab
2023-12-13  5:25 dpdklab
2023-12-13  5:08 dpdklab
2023-12-13  5:03 dpdklab
2023-12-13  5:00 dpdklab
2023-12-13  5:00 dpdklab
2023-12-13  4:58 dpdklab
2023-12-13  4:52 dpdklab
2023-12-13  4:44 dpdklab
2023-12-13  4:44 dpdklab
2023-12-13  4:43 dpdklab
2023-12-13  4:43 dpdklab
2023-12-13  4:42 dpdklab
2023-12-13  4:41 dpdklab
2023-12-13  4:40 dpdklab
2023-12-13  4:30 dpdklab
2023-12-13  4:28 dpdklab
2023-12-13  4:25 dpdklab
     [not found] <20231212164118.61936-1-stephen@networkplumber.org>
2023-12-12 16:24 ` qemudev
2023-12-12 16:29 ` qemudev
2023-12-12 16:41 ` checkpatch
2023-12-12 17:43 ` 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=657936c6.0c0a0220.1679b.448fSMTPIN_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).