automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: |FAILURE| pw114867-114878 [PATCH] [v6, 12/12] net/nfp: add flower PF rxtx logic
Date: Mon, 15 Aug 2022 22:54:58 +0000 (UTC)	[thread overview]
Message-ID: <20220815225458.60FAC6043F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4403 bytes --]

Test-Label: iol-aarch64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/114878

_Testing issues_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, August 12 2022 09:22:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:72206323a5dd3182b13f61b25a64abdddfee595c

114867-114878 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 ARM Clang Native (dpdk_meson_compile): ====
[2135/3510] Generating drivers/rte_net_ring.sym_chk with a custom command (wrapped by meson to capture output)
[2136/3510] Generating drivers/rte_net_ice.sym_chk with a custom command (wrapped by meson to capture output)
[2137/3510] Generating drivers/rte_net_qede.sym_chk with a custom command (wrapped by meson to capture output)
[2138/3510] Generating drivers/rte_net_vdev_netvsc.sym_chk with a custom command (wrapped by meson to capture output)
[2139/3510] Generating drivers/rte_net_thunderx.sym_chk with a custom command (wrapped by meson to capture output)
[2140/3510] Generating drivers/rte_net_tap.sym_chk with a custom command (wrapped by meson to capture output)
[2141/3510] Generating drivers/rte_net_vhost.sym_chk with a custom command (wrapped by meson to capture output)
[2142/3510] Generating drivers/rte_net_softnic.sym_chk with a custom command (wrapped by meson to capture output)
[2143/3510] Generating drivers/rte_net_i40e.sym_chk with a custom command (wrapped by meson to capture output)
[2144/3510] Generating drivers/rte_net_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[2145/3510] Generating lib/pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[2146/3510] Generating drivers/rte_net_ixgbe.sym_chk with a custom command (wrapped by meson to capture output)
[2147/3510] Generating drivers/rte_bus_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[2148/3510] Generating drivers/rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[2149/3510] Generating drivers/rte_common_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[2150/3510] Generating lib/ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[2151/3510] Generating drivers/rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[2152/3510] Generating lib/eal.sym_chk with a custom command (wrapped by meson to capture output)
[2153/3510] Generating drivers/rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

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

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

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/23212/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-08-15 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 22:54 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-15 20:39 dpdklab
2022-08-15 18:54 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=20220815225458.60FAC6043F@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=chaoyong.he@corigine.com \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).