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
Subject: |WARNING| pw144785-144790 [PATCH] [v3,6/6] examples: use eventdev pr
Date: Tue, 01 Oct 2024 05:11:48 -0700 (PDT)	[thread overview]
Message-ID: <66fbe704.050a0220.2210f8.08aaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241001061411.2537-7-pbhagavatula@marvell.com>

Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/144790

_Testing issues_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, October 01 2024 06:14:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:52a4028e4c33df32c691aa88751a659534b9ef02

144785-144790 --> testing issues

Upstream job id: ACVP-FIPS-testing#7124

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04       | SKIPPED              | WARN                 |
+--------------------+----------------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[2491/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_opdl@sta/event_opdl_opdl_evdev.c.o'.
[2492/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dsw@sta/event_dsw_dsw_xstats.c.o'.
[2493/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dpaa@sta/event_dpaa_dpaa_eventdev.c.o'.
[2494/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dlb2@sta/event_dlb2_dlb2_selftest.c.o'.
[2495/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dsw@sta/event_dsw_dsw_evdev.c.o'.
[2496/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_opdl@sta/event_opdl_opdl_evdev_xstats.c.o'.
[2497/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_opdl@sta/event_opdl_opdl_evdev_init.c.o'.
[2498/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dlb2@sta/event_dlb2_dlb2.c.o'.
[2499/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_skeleton@sta/event_skeleton_skeleton_eventdev.c.o'.
[2500/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dpaa2@sta/event_dpaa2_dpaa2_eventdev_selftest.c.o'.
[2501/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_opdl@sta/event_opdl_opdl_test.c.o'.
[2502/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dpaa2@sta/event_dpaa2_dpaa2_eventdev.c.o'.
[2503/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dlb2@sta/event_dlb2_pf_base_dlb2_resource.c.o'.
[2504/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_opdl@sta/event_opdl_opdl_ring.c.o'.
[2505/2966] Compiling C object 'drivers/a715181@@tmp_rte_event_dsw@sta/event_dsw_dsw_event.c.o'.
[2506/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
[2507/2966] Compiling C object 'drivers/a715181@@tmp_rte_crypto_cnxk@sta/crypto_cnxk_cn10k_cryptodev_ops.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-01 12:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001061411.2537-7-pbhagavatula@marvell.com>
2024-10-01  5:47 ` |SUCCESS| pw144785-144790 [PATCH v3 6/6] examples: use eventdev pre-scheduling qemudev
2024-10-01  5:52 ` qemudev
2024-10-01  6:16 ` |SUCCESS| pw144790 " checkpatch
2024-10-01  7:04 ` |FAILURE| " 0-day Robot
2024-10-01 11:03 ` |SUCCESS| pw144785-144790 [PATCH] [v3,6/6] examples: use eventdev pr dpdklab
2024-10-01 11:11 ` dpdklab
2024-10-01 11:13 ` |PENDING| " dpdklab
2024-10-01 11:16 ` |SUCCESS| " dpdklab
2024-10-01 11:22 ` dpdklab
2024-10-01 11:33 ` dpdklab
2024-10-01 11:37 ` dpdklab
2024-10-01 11:48 ` |PENDING| " dpdklab
2024-10-01 11:56 ` dpdklab
2024-10-01 12:08 ` |SUCCESS| " dpdklab
2024-10-01 12:09 ` dpdklab
2024-10-01 12:11 ` dpdklab [this message]
2024-10-01 12:23 ` |FAILURE| " dpdklab
2024-10-01 12:24 ` dpdklab
2024-10-01 12:26 ` dpdklab
2024-10-01 12:28 ` dpdklab
2024-10-01 12:33 ` dpdklab
2024-10-01 12:36 ` |SUCCESS| " dpdklab
2024-10-01 12:36 ` |FAILURE| " dpdklab
2024-10-01 12:42 ` |PENDING| " dpdklab
2024-10-01 12:42 ` |FAILURE| " dpdklab
2024-10-01 12:44 ` |WARNING| " dpdklab
2024-10-01 12:45 ` |FAILURE| " dpdklab
2024-10-01 12:48 ` dpdklab
2024-10-01 12:49 ` dpdklab
2024-10-01 12:50 ` dpdklab
2024-10-01 12:51 ` dpdklab
2024-10-01 12:54 ` dpdklab
2024-10-01 12:56 ` |WARNING| " dpdklab
2024-10-01 13:10 ` |FAILURE| " dpdklab
2024-10-01 13:24 ` |SUCCESS| " dpdklab
2024-10-01 16:08 ` dpdklab
2024-10-01 16:24 ` 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=66fbe704.050a0220.2210f8.08aaSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).