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, "Burakov,
	Anatoly" <anatoly.burakov@intel.com>
Subject: |FAILURE| pw143690-143694 [PATCH] [RFC,v1,5/5] lcore: store physical
Date: Fri, 06 Sep 2024 19:30:34 -0700 (PDT)	[thread overview]
Message-ID: <66dbbaca.250a0220.2b48dd.15fdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <f68d303116b86fd1df004c43941c72444a697c9d.1725622420.git.anatoly.burakov@intel.com>

Test-Label: iol-broadcom-Functional
Test-Status: FAILURE
http://dpdk.org/patch/143694

_Functional Testing issues_

Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Friday, September 06 2024 11:47:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143690-143694 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#178979

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  FAIL  |
+------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-07  2:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f68d303116b86fd1df004c43941c72444a697c9d.1725622420.git.anatoly.burakov@intel.com>
2024-09-06 11:21 ` |SUCCESS| pw143690-143694 [RFC PATCH v1 5/5] lcore: store physical package ID internally qemudev
2024-09-06 11:25 ` qemudev
2024-09-06 11:48 ` |WARNING| pw143694 " checkpatch
2024-09-06 12:44 ` |SUCCESS| " 0-day Robot
2024-09-06 16:29 ` |SUCCESS| pw143690-143694 [PATCH] [RFC,v1,5/5] lcore: store physical dpdklab
2024-09-06 16:33 ` dpdklab
2024-09-06 16:41 ` |PENDING| " dpdklab
2024-09-06 16:44 ` |FAILURE| " dpdklab
2024-09-06 16:47 ` |PENDING| " dpdklab
2024-09-06 16:53 ` |FAILURE| " dpdklab
2024-09-06 16:59 ` |SUCCESS| " dpdklab
2024-09-06 17:01 ` dpdklab
2024-09-06 18:47 ` dpdklab
2024-09-06 19:39 ` |FAILURE| " dpdklab
2024-09-06 22:59 ` |SUCCESS| " dpdklab
2024-09-06 22:59 ` dpdklab
2024-09-07  2:27 ` dpdklab
2024-09-07  2:30 ` dpdklab [this message]
2024-09-07  2:34 ` |FAILURE| " dpdklab
2024-09-07  2:53 ` dpdklab
2024-09-07  2:56 ` dpdklab
2024-09-07  7:57 ` |PENDING| " dpdklab
2024-09-07 10:54 ` |FAILURE| " dpdklab
2024-09-07 17:28 ` |SUCCESS| " dpdklab
2024-09-08  3:06 ` dpdklab
2024-09-17  7:55 ` |FAILURE| " dpdklab
2024-09-17  8:15 ` |SUCCESS| " 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=66dbbaca.250a0220.2b48dd.15fdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=anatoly.burakov@intel.com \
    --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).