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| pw126886 [PATCH] eal: fix eal init may failed when too much continuous memsegs under legacy mode
Date: Tue, 16 May 2023 06:44:49 -0700 (PDT)	[thread overview]
Message-ID: <646388d1.630a0220.44f5b.501eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Tuesday, May 16 2023 12:21:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

126886 --> 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/26241/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-16 13:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 13:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16 23:39 dpdklab
2023-05-16 23:30 dpdklab
2023-05-16 23:25 dpdklab
2023-05-16 23:20 dpdklab
2023-05-16 23:05 dpdklab
2023-05-16 18:44 dpdklab
2023-05-16 18:43 dpdklab
2023-05-16 15:49 dpdklab
2023-05-16 15:35 dpdklab
2023-05-16 15:28 dpdklab
2023-05-16 15:28 dpdklab
2023-05-16 15:27 dpdklab
2023-05-16 15:20 dpdklab
2023-05-16 15:13 dpdklab
2023-05-16 15:12 dpdklab
2023-05-16 15:11 dpdklab
2023-05-16 15:07 dpdklab
2023-05-16 15:02 dpdklab
2023-05-16 14:55 dpdklab
2023-05-16 14:50 dpdklab
2023-05-16 14:47 dpdklab
2023-05-16 14:34 dpdklab
2023-05-16 14:08 dpdklab
2023-05-16 13:57 dpdklab
2023-05-16 13:55 dpdklab
2023-05-16 13:49 dpdklab
2023-05-16 13:48 dpdklab
2023-05-16 13:48 dpdklab
2023-05-16 13:42 dpdklab
     [not found] <20230516122108.38617-1-changfengnan@bytedance.com>
2023-05-16 12:12 ` qemudev
2023-05-16 12:16 ` qemudev
2023-05-16 13:20 ` 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=646388d1.630a0220.44f5b.501eSMTPIN_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).