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,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: |FAILURE| pw130874-130875 [PATCH] [v2,2/2] dma/cnxk: rewrite DMA fas
Date: Wed, 30 Aug 2023 08:05:47 -0700 (PDT)	[thread overview]
Message-ID: <64ef5acb.170a0220.a7c8e.386cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130875

_Testing issues_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wednesday, August 30 2023 14:30:57 
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: master
  CommitID:3cadd086a2322a366f880e6c0b4a995313cc803e

130874-130875 --> testing fail

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+

==== 20 line log output for Ubuntu 20.04 ARM Clang Cross Compile (dpdk_meson_compile): ====

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

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-30 15:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 15:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-30 16:23 dpdklab
2023-08-30 16:21 dpdklab
2023-08-30 15:31 dpdklab
2023-08-30 15:27 dpdklab
2023-08-30 15:26 dpdklab
2023-08-30 15:25 dpdklab
2023-08-30 15:23 dpdklab
2023-08-30 15:22 dpdklab
2023-08-30 15:22 dpdklab
2023-08-30 15:21 dpdklab
2023-08-30 15:19 dpdklab
2023-08-30 15:16 dpdklab
2023-08-30 15:15 dpdklab
2023-08-30 15:11 dpdklab
2023-08-30 15:08 dpdklab
2023-08-30 15:07 dpdklab
2023-08-30 15:07 dpdklab
2023-08-30 15:06 dpdklab
2023-08-30 15:06 dpdklab
2023-08-30 15:06 dpdklab
2023-08-30 15:05 dpdklab
2023-08-30 15:05 dpdklab
2023-08-30 15:05 dpdklab
2023-08-30 15:05 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 dpdklab
2023-08-30 15:04 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=64ef5acb.170a0220.a7c8e.386cSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=pbhagavatula@marvell.com \
    --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).