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| pw134829-134846 [PATCH] [18/18] hash: convert RTE_LOGTYPE_
Date: Mon, 04 Dec 2023 19:22:52 -0800 (PST)	[thread overview]
Message-ID: <656e978c.170a0220.93fc1.c972SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, December 05 2023 02:09:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a526461b0764de52b09b073df84f9e87ec120c93

134829-134846 --> 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/28522/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-05  3:22 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  3:22 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-05  7:42 dpdklab
2023-12-05  7:40 dpdklab
2023-12-05  7:20 dpdklab
2023-12-05  4:53 dpdklab
2023-12-05  4:49 dpdklab
2023-12-05  4:48 dpdklab
2023-12-05  4:43 dpdklab
2023-12-05  4:13 dpdklab
2023-12-05  4:09 dpdklab
2023-12-05  4:02 dpdklab
2023-12-05  4:00 dpdklab
2023-12-05  3:58 dpdklab
2023-12-05  3:58 dpdklab
2023-12-05  3:55 dpdklab
2023-12-05  3:55 dpdklab
2023-12-05  3:55 dpdklab
2023-12-05  3:54 dpdklab
2023-12-05  3:54 dpdklab
2023-12-05  3:52 dpdklab
2023-12-05  3:50 dpdklab
2023-12-05  3:49 dpdklab
2023-12-05  3:36 dpdklab
2023-12-05  3:36 dpdklab
2023-12-05  3:35 dpdklab
2023-12-05  3:34 dpdklab
2023-12-05  3:34 dpdklab
2023-12-05  3:34 dpdklab
2023-12-05  3:34 dpdklab
2023-12-05  3:33 dpdklab
2023-12-05  3:33 dpdklab
2023-12-05  3:33 dpdklab
2023-12-05  3:32 dpdklab
2023-12-05  3:32 dpdklab
2023-12-05  3:32 dpdklab
2023-12-05  3:32 dpdklab
2023-12-05  3:31 dpdklab
2023-12-05  3:31 dpdklab
2023-12-05  3:31 dpdklab
2023-12-05  3:30 dpdklab
2023-12-05  3:30 dpdklab
2023-12-05  3:30 dpdklab
2023-12-05  3:30 dpdklab
2023-12-05  3:30 dpdklab
2023-12-05  3:29 dpdklab
2023-12-05  3:29 dpdklab
2023-12-05  3:29 dpdklab
2023-12-05  3:29 dpdklab
2023-12-05  3:25 dpdklab
2023-12-05  3:25 dpdklab
2023-12-05  3:25 dpdklab
2023-12-05  3:24 dpdklab
2023-12-05  3:22 dpdklab
2023-12-05  3:22 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=656e978c.170a0220.93fc1.c972SMTPIN_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).