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, Harman Kalra <hkalra@marvell.com>
Subject: |WARNING| pw136255-136254 [PATCH] [v5,2/2] test/devargs: add eth dev
Date: Thu, 01 Feb 2024 08:22:42 -0800 (PST)	[thread overview]
Message-ID: <65bbc552.050a0220.f7cf8.e473SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Harman Kalra <hkalra@marvell.com>
Date: Thursday, February 01 2024 10:02:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3178e37c65a676366f33f0bc56f49d9b26a06448

136255-136254 --> testing fail

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN                 |
+--------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
[2803/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2804/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2805/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2806/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2807/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2808/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2809/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2810/2817] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2811/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2812/2817] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2813/2817] Linking target examples/dpdk-fips_validation.
[2814/2817] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2815/2817] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2816/2817] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2817/2817] Linking target app/dpdk-test.
Processing file ../out/acvp-aes-cbc-vectors.json... Done
Processing file ../out/cmac-aes-vectors.json... Done
Processing file ../out/acvp-aes-gmac-vectors.json... Done
Processing file ../out/hmac-sha-1-vectors.json... Done
Processing file ../out/acvp-tdes-cbc-vectors.json... Processing file ../out/acvp-aes-ctr-vectors.json... Done
==== End log output ====

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2024-02-01 16:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=65bbc552.050a0220.f7cf8.e473SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=hkalra@marvell.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).