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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125243-125246 [PATCH] [6/6] windows: remove most pthread lifetime shim functions
Date: Mon, 20 Mar 2023 00:05:43 +0000 (UTC)	[thread overview]
Message-ID: <20230320000543.B509860214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125246

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, March 17 2023 22:34:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ce5440e0350df101443aa4d0e96bea0a06ef9364

125243-125246 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-20  0:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  0:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22  6:31 dpdklab
2023-03-22  5:38 dpdklab
2023-03-22  3:26 dpdklab
2023-03-22  3:26 dpdklab
2023-03-22  1:49 dpdklab
2023-03-22  1:49 dpdklab
2023-03-20 20:36 dpdklab
2023-03-20 19:35 dpdklab
2023-03-20 19:06 dpdklab
2023-03-20 19:02 dpdklab
2023-03-20 18:54 dpdklab
2023-03-20 18:48 dpdklab
2023-03-20 18:21 dpdklab
2023-03-20 18:15 dpdklab
2023-03-20  8:01 dpdklab
2023-03-20  0:10 dpdklab
2023-03-20  0:01 dpdklab
2023-03-19 23:46 dpdklab
2023-03-19 23:41 dpdklab
2023-03-19 23:37 dpdklab
2023-03-19 17:06 dpdklab
2023-03-19 15:13 dpdklab
2023-03-18  0:44 dpdklab
2023-03-17 23:50 dpdklab
2023-03-17 23:47 dpdklab
2023-03-17 23:41 dpdklab
2023-03-17 23:38 dpdklab
2023-03-17 23:33 dpdklab
2023-03-17 23:31 dpdklab
2023-03-17 23:28 dpdklab
2023-03-17 23:27 dpdklab
2023-03-17 23:22 dpdklab
2023-03-17 23:21 dpdklab
2023-03-17 23:18 dpdklab
2023-03-17 23:18 dpdklab
2023-03-17 23:12 dpdklab
2023-03-17 23:09 dpdklab
     [not found] <1679092460-9930-7-git-send-email-roretzla@linux.microsoft.com>
2023-03-17 22:24 ` |SUCCESS| pw125243-125246 [PATCH 6/6] " qemudev
2023-03-17 22:28 ` qemudev

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=20230320000543.B509860214@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).