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| pw132138-132139 [PATCH] [v3,2/2] dts: reformat to 100 line
Date: Thu, 28 Sep 2023 11:01:40 -0700 (PDT)	[thread overview]
Message-ID: <6515bf84.810a0220.9e547.4d21SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132139

_Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Thursday, September 28 2023 12:18:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c56185fc183fc0532d2f03aaf04bbf0989ea91a5

132138-132139 --> testing pass

Test environment and result as below:

+----------------------+--------------------+
|     Environment      | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS               |
+----------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-28 18:01 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 18:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29  2:00 dpdklab
2023-09-28 21:18 dpdklab
2023-09-28 21:17 dpdklab
2023-09-28 21:14 dpdklab
2023-09-28 21:08 dpdklab
2023-09-28 21:04 dpdklab
2023-09-28 21:03 dpdklab
2023-09-28 21:00 dpdklab
2023-09-28 20:55 dpdklab
2023-09-28 20:52 dpdklab
2023-09-28 20:50 dpdklab
2023-09-28 20:48 dpdklab
2023-09-28 20:45 dpdklab
2023-09-28 19:26 dpdklab
2023-09-28 18:55 dpdklab
2023-09-28 18:36 dpdklab
2023-09-28 18:36 dpdklab
2023-09-28 18:35 dpdklab
2023-09-28 18:35 dpdklab
2023-09-28 18:35 dpdklab
2023-09-28 18:25 dpdklab
2023-09-28 18:24 dpdklab
2023-09-28 18:24 dpdklab
2023-09-28 18:23 dpdklab
2023-09-28 18:18 dpdklab
2023-09-28 18:16 dpdklab
2023-09-28 18:16 dpdklab
2023-09-28 18:11 dpdklab
2023-09-28 18:11 dpdklab
2023-09-28 18:10 dpdklab
2023-09-28 18:09 dpdklab
2023-09-28 18:07 dpdklab
2023-09-28 18:05 dpdklab
2023-09-28 17:56 dpdklab
2023-09-28 17:48 dpdklab
2023-09-28 17:39 dpdklab
2023-09-28 17:38 dpdklab
2023-09-28 17:38 dpdklab
2023-09-28 17:38 dpdklab
2023-09-28 17:37 dpdklab
2023-09-28 17:36 dpdklab
2023-09-28 17:36 dpdklab
2023-09-28 17:35 dpdklab
2023-09-28 17:34 dpdklab
2023-09-28 17:33 dpdklab
2023-09-28 17:32 dpdklab
2023-09-28 17:28 dpdklab
2023-09-28 17:18 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=6515bf84.810a0220.9e547.4d21SMTPIN_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).