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, Josh Soref <jsoref@gmail.com>
Subject: |FAILURE| pw105747 [PATCH] [1/1] fix spelling in code
Date: Wed, 12 Jan 2022 09:04:01 +0000 (UTC)	[thread overview]
Message-ID: <20220112090401.1EAFC602B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/105747

_Testing issues_

Submitter: Josh Soref <jsoref@gmail.com>
Date: Wednesday, January 12 2022 07:28:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3f993907ee9d530bc595d973a5f764674fcaf509

105747 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS 8         | FAIL           |
+------------------+----------------+
| Fedora 32        | FAIL           |
+------------------+----------------+
| RHEL 7           | FAIL           |
+------------------+----------------+
| openSUSE Leap 15 | FAIL           |
+------------------+----------------+
| Fedora 31        | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | FAIL           |
+------------------+----------------+
| Ubuntu 18.04     | PASS           |
+------------------+----------------+
| Arch Linux       | FAIL           |
+------------------+----------------+
| RHEL8            | FAIL           |
+------------------+----------------+
| Fedora 34        | FAIL           |
+------------------+----------------+
| Fedora 33        | FAIL           |
+------------------+----------------+
| CentOS Stream 8  | FAIL           |
+------------------+----------------+
| Fedora 34 clang  | FAIL           |
+------------------+----------------+

==== 20 line log output for Fedora 34 clang (dpdk_unit_test): ====
^
3 errors generated.
[2306/2880] Generating rte_regex_octeontx2_mingw with a custom command.
[2307/2880] Compiling C object 'drivers/a715181@@rte_crypto_openssl@sta/meson-generated_.._rte_crypto_openssl.pmd.c.o'.
[2308/2880] Generating rte_vdpa_ifc_def with a custom command.
[2309/2880] Compiling C object 'drivers/a715181@@rte_crypto_openssl@sha/meson-generated_.._rte_crypto_openssl.pmd.c.o'.
[2310/2880] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev_mbox.c.o'.
[2311/2880] Compiling C object 'drivers/a715181@@tmp_rte_compress_octeontx@sta/compress_octeontx_otx_zip_pmd.c.o'.
[2312/2880] Generating rte_compress_mlx5.pmd.c with a custom command.
[2313/2880] Compiling C object 'drivers/a715181@@tmp_rte_compress_zlib@sta/compress_zlib_zlib_pmd.c.o'.
[2314/2880] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev_hw_access.c.o'.
[2315/2880] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev_compiler.c.o'.
[2316/2880] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev.c.o'.
[2317/2880] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa_sec@sta/crypto_dpaa_sec_dpaa_sec.c.o'.
[2318/2880] Compiling C object 'drivers/a715181@@tmp_rte_crypto_scheduler@sta/crypto_scheduler_scheduler_multicore.c.o'.
[2319/2880] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_ifc@sta/vdpa_ifc_ifcvf_vdpa.c.o'.
[2320/2880] Compiling C object 'drivers/a715181@@tmp_rte_crypto_dpaa2_sec@sta/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o'.
[2321/2880] Compiling C object 'drivers/a715181@@tmp_rte_crypto_octeontx2@sta/crypto_octeontx2_otx2_cryptodev_ops.c.o'.
[2322/2880] Compiling C object 'drivers/a715181@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

CentOS 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-01-12  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  9:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-12  8:55 dpdklab
2022-01-12  8:55 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=20220112090401.1EAFC602B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=jsoref@gmail.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).