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| pw132611-132612 [PATCH] [v2,2/2] doc/guides: refer to gene
Date: Sun, 15 Oct 2023 20:23:14 -0700 (PDT)	[thread overview]
Message-ID: <652caca2.810a0220.67a57.e0e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Friday, October 13 2023 21:42:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:441e777b85f1ea1eb6a2a970ff5d5c8e027f520c

132611-132612 --> 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/27930/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-16  3:23 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  3:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16  4:59 dpdklab
2023-10-16  4:58 dpdklab
2023-10-16  4:58 dpdklab
2023-10-16  4:54 dpdklab
2023-10-16  4:07 dpdklab
2023-10-16  4:01 dpdklab
2023-10-16  3:54 dpdklab
2023-10-16  3:50 dpdklab
2023-10-16  3:50 dpdklab
2023-10-16  3:41 dpdklab
2023-10-16  3:40 dpdklab
2023-10-16  3:40 dpdklab
2023-10-16  3:40 dpdklab
2023-10-16  3:38 dpdklab
2023-10-16  3:33 dpdklab
2023-10-16  3:25 dpdklab
2023-10-16  3:22 dpdklab
2023-10-16  3:21 dpdklab
2023-10-16  3:20 dpdklab
2023-10-16  3:16 dpdklab
2023-10-16  3:12 dpdklab
2023-10-16  3:11 dpdklab
2023-10-16  3:08 dpdklab
2023-10-16  2:59 dpdklab
2023-10-16  2:59 dpdklab
2023-10-16  2:58 dpdklab
2023-10-16  2:53 dpdklab
2023-10-16  2:52 dpdklab
2023-10-16  2:52 dpdklab
2023-10-16  2:49 dpdklab
2023-10-16  2:49 dpdklab
2023-10-16  2:48 dpdklab
2023-10-16  2:46 dpdklab
2023-10-16  2:42 dpdklab
2023-10-16  2:39 dpdklab
2023-10-16  2:36 dpdklab
2023-10-16  2:32 dpdklab
2023-10-16  2:30 dpdklab
2023-10-16  2:23 dpdklab
2023-10-16  2:23 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=652caca2.810a0220.67a57.e0e5SMTPIN_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).