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| pw148471-148473 [PATCH] [v2,3/3] bus/dpaa: enabling clang
Date: Sat, 16 Nov 2024 08:52:22 -0800 (PST)	[thread overview]
Message-ID: <6738cdc6.250a0220.2a7ff2.66b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241114074437.2943885-3-hemant.agrawal@nxp.com>

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

_Testing issues_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Thursday, November 14 2024 07:44:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:012b02bdbc95a5ec3b293f2d37d8955140fd8831

148471-148473 --> testing issues

Upstream job id: ACVP-FIPS-testing#7973

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
[2997/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_gcm.c.o
[2998/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_tdes.c.o
[2999/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_ccm.c.o
[3000/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_cmac.c.o
[3001/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation.c.o
[3002/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_sha.c.o
[3003/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_xts.c.o
[3004/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_eddsa.c.o
[3005/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_ecdsa.c.o
[3006/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o
[3007/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_fips_dev_self_test.c.o
[3008/3015] Compiling C object app/dpdk-test.p/test_test_table_combined.c.o
[3009/3015] Compiling C object examples/dpdk-fips_validation.p/fips_validation_main.c.o
[3010/3015] Compiling C object app/dpdk-test.p/test_virtual_pmd.c.o
[3011/3015] Linking target examples/dpdk-fips_validation
[3012/3015] Compiling C object app/dpdk-test.p/test_test_trace_perf.c.o
[3013/3015] Compiling C object app/dpdk-test.p/test_test_ring_perf.c.o
[3014/3015] Compiling C object app/dpdk-test.p/test_test_ring.c.o
[3015/3015] Linking target app/dpdk-test
Processing file ../out/acvp-aes-cbc-vectors.json... Processing file ../out/cmac-aes-vectors.json... Processing file ../out/acvp-aes-gmac-vectors.json... Processing file ../out/hmac-sha-1-vectors.json... Processing file ../out/acvp-tdes-cbc-vectors.json... Processing file ../out/acvp-aes-ctr-vectors.json...
==== 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 22.04
	Kernel: 5.15.0-100-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/31928/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-16 16:52 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241114074437.2943885-3-hemant.agrawal@nxp.com>
2024-11-14  7:13 ` |SUCCESS| pw148471-148473 [PATCH v2 3/3] bus/dpaa: enabling clang thread safety for locks qemudev
2024-11-14  7:17 ` qemudev
2024-11-14  7:45 ` |SUCCESS| pw148473 " checkpatch
2024-11-14  9:25 ` 0-day Robot
2024-11-14 10:37 ` |SUCCESS| pw148471-148473 [PATCH] [v2,3/3] bus/dpaa: enabling clang dpdklab
2024-11-14 10:52 ` dpdklab
2024-11-14 11:19 ` dpdklab
2024-11-14 11:19 ` dpdklab
2024-11-14 11:39 ` dpdklab
2024-11-14 11:48 ` dpdklab
2024-11-14 12:10 ` dpdklab
2024-11-14 12:14 ` dpdklab
2024-11-14 12:51 ` dpdklab
2024-11-14 16:02 ` |PENDING| " dpdklab
2024-11-14 16:04 ` dpdklab
2024-11-14 16:24 ` dpdklab
2024-11-14 16:27 ` |SUCCESS| " dpdklab
2024-11-14 16:36 ` |PENDING| " dpdklab
2024-11-14 17:00 ` |SUCCESS| " dpdklab
2024-11-14 17:58 ` |PENDING| " dpdklab
2024-11-14 18:18 ` dpdklab
2024-11-14 18:33 ` dpdklab
2024-11-14 18:41 ` dpdklab
2024-11-14 18:44 ` |SUCCESS| " dpdklab
2024-11-14 18:55 ` dpdklab
2024-11-14 18:57 ` dpdklab
2024-11-14 19:36 ` dpdklab
2024-11-14 20:05 ` dpdklab
2024-11-14 21:19 ` dpdklab
2024-11-14 22:28 ` dpdklab
2024-11-14 22:52 ` dpdklab
2024-11-14 23:02 ` dpdklab
2024-11-14 23:17 ` dpdklab
2024-11-14 23:28 ` dpdklab
2024-11-14 23:32 ` dpdklab
2024-11-14 23:52 ` dpdklab
2024-11-15  0:41 ` dpdklab
2024-11-15  1:41 ` dpdklab
2024-11-15  3:24 ` dpdklab
2024-11-16 14:15 ` dpdklab
2024-11-16 14:25 ` dpdklab
2024-11-16 16:22 ` dpdklab
2024-11-16 16:33 ` |WARNING| " dpdklab
2024-11-16 16:39 ` |SUCCESS| " dpdklab
2024-11-16 16:52 ` dpdklab [this message]
2024-11-16 16:56 ` dpdklab
2024-11-16 17:02 ` dpdklab
2024-11-16 17:12 ` dpdklab
2024-11-16 17:18 ` 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=6738cdc6.250a0220.2a7ff2.66b6SMTPIN_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).