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, Suanming Mou <suanmingm@nvidia.com>
Subject: |WARNING| pw138482 [PATCH] [v2] app/test-crypto-perf: add throughput
Date: Wed, 20 Mar 2024 00:04:29 -0700 (PDT)	[thread overview]
Message-ID: <65fa8a7d.050a0220.fe13c.9f69SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240319114623.1137757-1-suanmingm@nvidia.com>

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

_Testing issues_

Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Tuesday, March 19 2024 11:46:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7f82e9c89f3514715533feb34f46ff1ea95c6f98

138482 --> 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): ====
[2872/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2873/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_timer_racecond.c.o'.
[2874/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2875/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_register.c.o'.
[2876/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace.c.o'.
[2877/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_cmac.c.o'.
[2878/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2879/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2880/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2881/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_timer_secondary.c.o'.
[2882/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2883/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2884/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2885/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2886/2891] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2887/2891] Linking target examples/dpdk-fips_validation.
[2888/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2889/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2890/2891] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2891/2891] Linking target app/dpdk-test.
==== End log output ====

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-20  7:04 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240319114623.1137757-1-suanmingm@nvidia.com>
2024-03-19 11:24 ` |SUCCESS| pw138482 [PATCH v2] app/test-crypto-perf: add throughput OOP decryption qemudev
2024-03-19 11:29 ` qemudev
2024-03-19 11:47 ` checkpatch
2024-03-19 12:44 ` 0-day Robot
2024-03-19 18:02 ` |SUCCESS| pw138482 [PATCH] [v2] app/test-crypto-perf: add throughput dpdklab
2024-03-19 18:06 ` dpdklab
2024-03-19 18:07 ` dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:12 ` dpdklab
2024-03-19 18:12 ` dpdklab
2024-03-19 18:13 ` dpdklab
2024-03-19 18:16 ` dpdklab
2024-03-19 18:17 ` dpdklab
2024-03-19 18:18 ` dpdklab
2024-03-19 18:19 ` dpdklab
2024-03-19 18:21 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:23 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:33 ` dpdklab
2024-03-19 18:38 ` dpdklab
2024-03-19 18:46 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 19:20 ` dpdklab
2024-03-19 19:25 ` dpdklab
2024-03-19 19:30 ` dpdklab
2024-03-19 19:31 ` dpdklab
2024-03-19 19:32 ` dpdklab
2024-03-19 19:32 ` dpdklab
2024-03-19 19:33 ` dpdklab
2024-03-19 19:35 ` dpdklab
2024-03-19 19:35 ` dpdklab
2024-03-19 19:36 ` dpdklab
2024-03-19 19:37 ` dpdklab
2024-03-19 19:39 ` dpdklab
2024-03-19 19:42 ` dpdklab
2024-03-19 19:43 ` dpdklab
2024-03-19 19:44 ` dpdklab
2024-03-19 19:45 ` dpdklab
2024-03-19 19:45 ` dpdklab
2024-03-19 19:46 ` dpdklab
2024-03-19 19:47 ` dpdklab
2024-03-19 19:47 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:51 ` dpdklab
2024-03-19 19:51 ` dpdklab
2024-03-19 19:51 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 19:53 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 20:00 ` dpdklab
2024-03-19 20:00 ` dpdklab
2024-03-19 20:01 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:04 ` dpdklab
2024-03-19 20:04 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:08 ` dpdklab
2024-03-19 20:17 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:55 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-20  7:04 ` dpdklab [this message]
2024-03-21  7:55 ` dpdklab
2024-03-21  8:49 ` 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=65fa8a7d.050a0220.fe13c.9f69SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=suanmingm@nvidia.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).