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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 7849366693a2a2cbc5279a6bfd39cbb457fe7c96
Date: Sat, 14 Oct 2023 22:37:44 -0700 (PDT)	[thread overview]
Message-ID: <652b7aa8.4a0a0220.b5741.ce84SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v22.11

7849366693a2a2cbc5279a6bfd39cbb457fe7c96 --> 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): ====
[3515/3533] Linking target app/dpdk-test-gpudev.
[3516/3533] Linking target app/dpdk-dumpcap.
[3517/3533] Linking target app/dpdk-test-fib.
[3518/3533] Linking target app/dpdk-test-acl.
[3519/3533] Linking target app/dpdk-test-bbdev.
[3520/3533] Linking target app/dpdk-test-pipeline.
[3521/3533] Linking target app/dpdk-test-compress-perf.
[3522/3533] Linking target app/dpdk-pdump.
[3523/3533] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_trace_perf.c.o'.
[3524/3533] Linking target app/dpdk-test-flow-perf.
[3525/3533] Linking target app/dpdk-test-eventdev.
[3526/3533] Linking target app/dpdk-test-sad.
[3527/3533] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring_perf.c.o'.
[3528/3533] Linking target app/dpdk-testpmd.
[3529/3533] Linking target app/dpdk-test-security-perf.
[3530/3533] Linking target app/dpdk-test-regex.
[3531/3533] Linking target examples/dpdk-fips_validation.
[3532/3533] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring.c.o'.
[3533/3533] Linking target app/test/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 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/tarballs/26478/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-15  5:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15  5:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-09  7:01 dpdklab
2023-11-28 20:06 dpdklab
2023-11-20  6:48 dpdklab
2023-11-20  6:46 dpdklab
2023-11-20  6:43 dpdklab
2023-11-20  6:40 dpdklab
2023-11-20  6:40 dpdklab
2023-11-20  6:38 dpdklab
2023-11-20  6:37 dpdklab
2023-11-20  6:34 dpdklab
2023-11-20  6:34 dpdklab
2023-11-20  6:21 dpdklab
2023-11-20  6:11 dpdklab
2023-11-20  6:06 dpdklab
2023-11-20  5:31 dpdklab
2023-11-20  5:30 dpdklab
2023-11-04  5:30 dpdklab
2023-10-16  5:46 dpdklab
2023-10-14  6:28 dpdklab
2023-10-14  6:18 dpdklab
2023-10-14  6:08 dpdklab
2023-10-14  6:00 dpdklab
2023-10-14  5:51 dpdklab
2023-10-14  5:46 dpdklab
2023-10-14  5:42 dpdklab
2023-10-14  5:41 dpdklab
2023-10-14  5:38 dpdklab
2023-10-14  5:22 dpdklab
2023-10-14  5:18 dpdklab
2023-10-14  5:17 dpdklab
2023-10-14  5:11 dpdklab
2023-10-14  4:28 dpdklab
2023-10-14  4:26 dpdklab
2023-09-27  7:38 dpdklab
2023-09-25  5:50 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=652b7aa8.4a0a0220.b5741.ce84SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).