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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 49b2102bf9fea000d36860353016a5c6ddf993a9
Date: Mon, 20 May 2024 22:59:09 -0700 (PDT)	[thread overview]
Message-ID: <664c382d.050a0220.77587.902fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v21.11

49b2102bf9fea000d36860353016a5c6ddf993a9 --> testing fail

Test environment and result as below:

+-----------------------------+----------------+--------------+
|         Environment         | dpdk_unit_test | lpm_autotest |
+=============================+================+==============+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | FAIL         |
+-----------------------------+----------------+--------------+

==== 20 line log output for Ubuntu 20.04 ARM SVE (lpm_autotest): ====

32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29150/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-05-21  5:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21  5:59 dpdklab [this message]
2024-05-21  6:04 dpdklab
2024-07-01  4:48 dpdklab
2024-07-01  5:01 dpdklab
2024-08-16  7:59 dpdklab
2024-08-26  9:26 dpdklab
2024-08-27  9:58 dpdklab
2024-08-28  9:57 dpdklab
2024-09-01  9:12 dpdklab
2024-09-02  8:12 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=664c382d.050a0220.77587.902fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).