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| pw136707-136739 [PATCH] [v3,39/39] ip_frag: use C11 aligna
Date: Wed, 14 Feb 2024 07:05:42 -0800 (PST)	[thread overview]
Message-ID: <65ccd6c6.170a0220.5592b.4944SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, February 14 2024 07:06:22 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31d72ff4dc7c057366153e9918ac92bf9123a3bc

136707-136739 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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


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/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-14 15:05 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 15:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14 17:18 dpdklab
2024-02-14 16:43 dpdklab
2024-02-14 15:33 dpdklab
2024-02-14 14:46 dpdklab
2024-02-14 12:31 dpdklab
2024-02-14 10:12 dpdklab
2024-02-14 10:07 dpdklab
2024-02-14 10:06 dpdklab
2024-02-14 10:04 dpdklab
2024-02-14  9:54 dpdklab
2024-02-14  9:52 dpdklab
2024-02-14  9:52 dpdklab
2024-02-14  9:41 dpdklab
2024-02-14  9:23 dpdklab
2024-02-14  9:19 dpdklab
2024-02-14  9:19 dpdklab
2024-02-14  9:15 dpdklab
2024-02-14  9:14 dpdklab
2024-02-14  9:13 dpdklab
2024-02-14  9:12 dpdklab
2024-02-14  9:10 dpdklab
2024-02-14  9:06 dpdklab
2024-02-14  9:00 dpdklab
2024-02-14  9:00 dpdklab
2024-02-14  8:59 dpdklab
2024-02-14  8:58 dpdklab
2024-02-14  8:57 dpdklab
2024-02-14  8:55 dpdklab
2024-02-14  8:54 dpdklab
2024-02-14  8:54 dpdklab
2024-02-14  8:52 dpdklab
2024-02-14  8:52 dpdklab
2024-02-14  8:50 dpdklab
2024-02-14  8:50 dpdklab
2024-02-14  8:49 dpdklab
2024-02-14  8:48 dpdklab
2024-02-14  8:48 dpdklab
2024-02-14  8:47 dpdklab
2024-02-14  8:46 dpdklab
2024-02-14  8:44 dpdklab
2024-02-14  8:42 dpdklab
2024-02-14  8:41 dpdklab
2024-02-14  8:41 dpdklab
2024-02-14  8:40 dpdklab
2024-02-14  8:34 dpdklab
2024-02-14  8:31 dpdklab
2024-02-14  8:31 dpdklab
2024-02-14  8:31 dpdklab
2024-02-14  8:30 dpdklab
2024-02-14  8:30 dpdklab
2024-02-14  8:29 dpdklab
2024-02-14  8:28 dpdklab
2024-02-14  8:27 dpdklab
2024-02-14  8:27 dpdklab
2024-02-14  8:27 dpdklab
2024-02-14  8:26 dpdklab
2024-02-14  8:25 dpdklab
2024-02-14  8:24 dpdklab
2024-02-14  8:22 dpdklab
2024-02-14  8:22 dpdklab
2024-02-14  8:22 dpdklab
2024-02-14  8:22 dpdklab
2024-02-14  8:21 dpdklab
2024-02-14  8:21 dpdklab
2024-02-14  8:20 dpdklab
2024-02-14  8:20 dpdklab
2024-02-14  8:19 dpdklab
2024-02-14  8:19 dpdklab
2024-02-14  8:18 dpdklab
2024-02-14  8:06 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=65ccd6c6.170a0220.5592b.4944SMTPIN_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).