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, "Zhang,
	Roy Fan" <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |FAILURE| pw101648-101657 [PATCH] [v3, 10/10] common/qat: unify naming conventions in qat functions
Date: Thu, 14 Oct 2021 13:39:11 -0400 (EDT)	[thread overview]
Message-ID: <20211014173911.DC0C860524@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/101657

_Testing issues_

Submitter: Zhang, Roy Fan <roy.fan.zhang@intel.com>
Date: Thursday, October 14 2021 16:11:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d75eed0fbe4b942bc6df2e2908a8b5c2c30c99aa

101648-101657 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | FAIL           |
+------------------+----------------+

==== 20 line log output for Ubuntu 20.04 ARM (dpdk_unit_test): ====
[815/2915] Generating rte_bus_auxiliary.sym_chk with a custom command (wrapped by meson to capture output)
[816/2915] Generating rte_common_octeontx.sym_chk with a custom command (wrapped by meson to capture output)
[817/2915] Generating rte_common_iavf.sym_chk with a custom command (wrapped by meson to capture output)
[818/2915] Generating rte_bus_vdev.sym_chk with a custom command (wrapped by meson to capture output)
[819/2915] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_hw_dp.c.o
[820/2915] Generating rte_bus_ifpga.sym_chk with a custom command (wrapped by meson to capture output)
[821/2915] Generating vhost.sym_chk with a custom command (wrapped by meson to capture output)
[822/2915] Generating rte_bus_pci.sym_chk with a custom command (wrapped by meson to capture output)
[823/2915] Generating rte_common_dpaax.sym_chk with a custom command (wrapped by meson to capture output)
[824/2915] Generating graph.sym_chk with a custom command (wrapped by meson to capture output)
[825/2915] Generating rte_bus_vmbus.sym_chk with a custom command (wrapped by meson to capture output)
[826/2915] Generating eventdev.sym_chk with a custom command (wrapped by meson to capture output)
[827/2915] Generating cryptodev.sym_chk with a custom command (wrapped by meson to capture output)
[828/2915] Generating rte_common_octeontx2.sym_chk with a custom command (wrapped by meson to capture output)
[829/2915] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[830/2915] Generating rte_bus_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[831/2915] Generating rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[832/2915] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[833/2915] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-14 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 17:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-15 15:37 dpdklab
2021-10-14 17:33 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=20211014173911.DC0C860524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=roy.fan.zhang@intel.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).