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: [dpdk-test-report] |SUCCESS| pw96657 [PATCH] [v5] bus: clarify log for non-NUMA-aware devices
Date: Wed,  4 Aug 2021 19:10:52 -0400 (EDT)	[thread overview]
Message-ID: <20210804231052.7B82C487@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/96657

_Testing PASS_

Submitter: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Date: Wednesday, August 04 2021 08:03:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:45633c460c223a67dd1a7cc084c3eceb5e17687c

96657 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | PASS           |
+------------------+----------------+


Ubuntu 20.04 ARM
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-08-04 23:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 23:10 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-05  2:49 dpdklab
2021-08-05  2:38 dpdklab
2021-08-05  1:57 dpdklab
2021-08-05  0:11 dpdklab
2021-08-04 23:56 dpdklab
2021-08-04 23:39 dpdklab
2021-08-04 23:27 dpdklab
2021-08-04 21:26 dpdklab
2021-08-04 21:18 dpdklab
2021-08-04 21:06 dpdklab
2021-08-04 20:53 dpdklab
     [not found] <20210804080301.1440491-1-dkozlyuk@nvidia.com>
2021-08-04  8:04 ` [dpdk-test-report] |SUCCESS| pw96657 [PATCH v5] " checkpatch

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=20210804231052.7B82C487@noxus.dpdklab.iol.unh.edu \
    --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).