From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Selwin Sebastian <selwin.sebastian@amd.com>
Subject: |FAILURE| pw130984 [PATCH] [v1] net/axgbe: use CPUID to identify cpu
Date: Thu, 31 Aug 2023 09:49:39 -0700 (PDT) [thread overview]
Message-ID: <64f0c4a3.170a0220.ac271.0fc9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130984
_Testing issues_
Submitter: Selwin Sebastian <selwin.sebastian@amd.com>
Date: Thursday, August 31 2023 12:31:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b7b8de26f34d39c8aaded44d8a468da5e68f19da
130984 --> testing fail
Test environment and result as below:
+-----------------------------+----------------+
| Environment | dpdk_unit_test |
+=============================+================+
| 32-bit Ubuntu 20.04.4 (ARM) | FAIL |
+-----------------------------+----------------+
==== 20 line log output for 32-bit Ubuntu 20.04.4 (ARM) (dpdk_unit_test): ====
[853/1971] Generating lib/port.sym_chk with a custom command (wrapped by meson to capture output)
[854/1971] Generating lib/rawdev.sym_chk with a custom command (wrapped by meson to capture output)
[855/1971] Generating lib/mempool.sym_chk with a custom command (wrapped by meson to capture output)
[856/1971] Generating lib/bbdev.sym_chk with a custom command (wrapped by meson to capture output)
[857/1971] Generating lib/table.sym_chk with a custom command (wrapped by meson to capture output)
[858/1971] Generating lib/regexdev.sym_chk with a custom command (wrapped by meson to capture output)
[859/1971] Generating lib/gpudev.sym_chk with a custom command (wrapped by meson to capture output)
[860/1971] Generating lib/power.sym_chk with a custom command (wrapped by meson to capture output)
[861/1971] Generating lib/compressdev.sym_chk with a custom command (wrapped by meson to capture output)
[862/1971] Generating lib/hash.sym_chk with a custom command (wrapped by meson to capture output)
[863/1971] Generating lib/cmdline.sym_chk with a custom command (wrapped by meson to capture output)
[864/1971] Generating lib/graph.sym_chk with a custom command (wrapped by meson to capture output)
[865/1971] Generating lib/vhost.sym_chk with a custom command (wrapped by meson to capture output)
[866/1971] Generating lib/mldev.sym_chk with a custom command (wrapped by meson to capture output)
[867/1971] Generating lib/cryptodev.sym_chk with a custom command (wrapped by meson to capture output)
[868/1971] Generating lib/eventdev.sym_chk with a custom command (wrapped by meson to capture output)
[869/1971] Generating lib/pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[870/1971] Generating lib/ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[871/1971] Generating lib/eal.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27491/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-31 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 16:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-31 16:23 dpdklab
2023-08-31 16:20 dpdklab
2023-08-31 16:20 dpdklab
2023-08-31 16:20 dpdklab
2023-08-31 16:20 dpdklab
2023-08-31 16:20 dpdklab
2023-08-31 16:19 dpdklab
2023-08-31 16:19 dpdklab
2023-08-31 16:18 dpdklab
[not found] <20230831123131.4787-1-selwin.sebastian@amd.com>
2023-08-31 12:30 ` |FAILURE| pw130984 [PATCH v1] " qemudev
2023-08-31 13:19 ` 0-day Robot
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=64f0c4a3.170a0220.ac271.0fc9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=selwin.sebastian@amd.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).