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, Gregory Etelson <getelson@nvidia.com>
Subject: |WARNING| pw138481 [PATCH] [v2] net/mlx5: fix sync meter action
Date: Wed, 20 Mar 2024 07:34:47 -0700 (PDT)	[thread overview]
Message-ID: <65faf407.b00a0220.e362d.c6deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240319112455.329350-1-getelson@nvidia.com>

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

_Testing issues_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, March 19 2024 11:24:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138481 --> 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): ====
[2874/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace.c.o'.
[2875/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_register.c.o'.
[2876/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2877/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_timer_secondary.c.o'.
[2878/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_cmac.c.o'.
[2879/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2880/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2881/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2882/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2883/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2884/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2885/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2886/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2887/2892] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2888/2892] Linking target examples/dpdk-fips_validation.
[2889/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2890/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2891/2892] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2892/2892] Linking target app/dpdk-test.
Processing file ../out/cmac-aes-vectors.json... Processing file ../out/acvp-aes-gmac-vectors.json...
==== 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/29594/

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 14:34 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240319112455.329350-1-getelson@nvidia.com>
2024-03-19 11:15 ` |SUCCESS| pw138481 [PATCH v2] " qemudev
2024-03-19 11:19 ` qemudev
2024-03-19 11:26 ` checkpatch
2024-03-19 12:23 ` 0-day Robot
2024-03-19 18:17 ` |SUCCESS| pw138481 [PATCH] [v2] " dpdklab
2024-03-19 18:17 ` dpdklab
2024-03-19 18:20 ` dpdklab
2024-03-19 18:21 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:23 ` dpdklab
2024-03-19 18:24 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:36 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:56 ` dpdklab
2024-03-19 18:58 ` dpdklab
2024-03-19 18:58 ` dpdklab
2024-03-19 18:59 ` dpdklab
2024-03-19 19:00 ` dpdklab
2024-03-19 19:01 ` dpdklab
2024-03-19 19:02 ` dpdklab
2024-03-19 19:04 ` dpdklab
2024-03-19 19:04 ` dpdklab
2024-03-19 19:57 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 20:00 ` dpdklab
2024-03-19 20:01 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:07 ` dpdklab
2024-03-19 20:08 ` dpdklab
2024-03-19 20:08 ` dpdklab
2024-03-19 20:09 ` dpdklab
2024-03-19 20:10 ` dpdklab
2024-03-19 20:11 ` dpdklab
2024-03-19 20:13 ` dpdklab
2024-03-19 20:13 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:14 ` dpdklab
2024-03-19 20:15 ` dpdklab
2024-03-19 20:16 ` dpdklab
2024-03-19 20:23 ` dpdklab
2024-03-19 20:35 ` dpdklab
2024-03-19 21:06 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:20 ` dpdklab
2024-03-19 21:34 ` dpdklab
2024-03-20 14:34 ` dpdklab [this message]
2024-03-21  9:19 ` dpdklab
2024-03-21 10:08 ` 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=65faf407.b00a0220.e362d.c6deSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=getelson@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).