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| pw132420 [PATCH] [v2] config/arm: update aarch32 build wit
Date: Mon, 09 Oct 2023 04:15:34 -0700 (PDT)	[thread overview]
Message-ID: <6523e0d6.170a0220.165bb.5de5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Monday, October 09 2023 09:53:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c

132420 --> functional testing pass

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-09 11:15 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 11:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-09 13:23 dpdklab
2023-10-09 13:18 dpdklab
2023-10-09 13:16 dpdklab
2023-10-09 13:15 dpdklab
2023-10-09 13:03 dpdklab
2023-10-09 12:57 dpdklab
2023-10-09 12:57 dpdklab
2023-10-09 12:53 dpdklab
2023-10-09 12:47 dpdklab
2023-10-09 12:47 dpdklab
2023-10-09 12:46 dpdklab
2023-10-09 12:42 dpdklab
2023-10-09 12:38 dpdklab
2023-10-09 12:35 dpdklab
2023-10-09 12:28 dpdklab
2023-10-09 12:24 dpdklab
2023-10-09 12:23 dpdklab
2023-10-09 12:19 dpdklab
2023-10-09 12:17 dpdklab
2023-10-09 12:12 dpdklab
2023-10-09 12:01 dpdklab
2023-10-09 11:58 dpdklab
2023-10-09 11:58 dpdklab
2023-10-09 11:55 dpdklab
2023-10-09 11:53 dpdklab
2023-10-09 11:52 dpdklab
2023-10-09 11:42 dpdklab
2023-10-09 11:34 dpdklab
2023-10-09 11:32 dpdklab
2023-10-09 11:31 dpdklab
2023-10-09 11:30 dpdklab
2023-10-09 11:30 dpdklab
2023-10-09 11:26 dpdklab
2023-10-09 11:26 dpdklab
2023-10-09 11:25 dpdklab
2023-10-09 11:24 dpdklab
2023-10-09 11:24 dpdklab
2023-10-09 11:24 dpdklab
2023-10-09 11:24 dpdklab
2023-10-09 11:23 dpdklab
2023-10-09 11:23 dpdklab
2023-10-09 11:23 dpdklab
2023-10-09 11:23 dpdklab
2023-10-09 11:22 dpdklab
2023-10-09 11:15 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=6523e0d6.170a0220.165bb.5de5SMTPIN_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).