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] 181fb849b5ab50011438cf507f7e84132b0a4fdb
Date: Sun, 21 Jan 2024 01:24:05 -0800 (PST)	[thread overview]
Message-ID: <65ace2b5.050a0220.55db6.0c92SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v21.11

181fb849b5ab50011438cf507f7e84132b0a4fdb --> 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): ====
[3079/3097] Linking target drivers/librte_event_octeontx2.so.22.0.
[3080/3097] Linking target app/dpdk-proc-info.
[3081/3097] Linking target app/dpdk-pdump.
[3082/3097] Linking target app/dpdk-test-bbdev.
[3083/3097] Linking target app/dpdk-test-fib.
[3084/3097] Linking target app/dpdk-test-acl.
[3085/3097] Linking target app/dpdk-test-pipeline.
[3086/3097] Linking target app/test/dpdk-test.
[3087/3097] Linking target app/dpdk-test-cmdline.
[3088/3097] Linking target app/dpdk-test-eventdev.
[3089/3097] Linking target app/dpdk-test-regex.
[3090/3097] Linking target app/dpdk-test-compress-perf.
[3091/3097] Linking target app/dpdk-test-crypto-perf.
[3092/3097] Linking target app/dpdk-test-flow-perf.
[3093/3097] Linking target examples/dpdk-fips_validation.
[3094/3097] Linking target app/dpdk-test-gpudev.
[3095/3097] Linking target app/dpdk-dumpcap.
[3096/3097] Linking target app/dpdk-test-sad.
[3097/3097] Linking target app/dpdk-testpmd.
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/27745/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-21  9:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  9:24 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-15  7:19 dpdklab
2024-02-15  6:54 dpdklab
2024-02-14 13:15 dpdklab
2024-02-14 11:39 dpdklab
2024-02-13  7:32 dpdklab
2024-02-13  6:44 dpdklab
2024-02-12  7:34 dpdklab
2024-02-12  7:11 dpdklab
2024-02-11  7:31 dpdklab
2024-02-11  7:16 dpdklab
2024-02-10  7:47 dpdklab
2024-02-10  6:53 dpdklab
2024-02-09  7:30 dpdklab
2024-02-09  7:05 dpdklab
2024-02-08  6:04 dpdklab
2024-02-07  5:44 dpdklab
2024-02-06  7:21 dpdklab
2024-02-05  6:49 dpdklab
2024-02-04  6:37 dpdklab
2024-02-03  6:20 dpdklab
2024-02-02 11:31 dpdklab
2024-02-01  7:14 dpdklab
2024-01-31  6:22 dpdklab
2024-01-30  9:41 dpdklab
2024-01-28  7:21 dpdklab
2024-01-27  7:06 dpdklab
2024-01-26  7:57 dpdklab
2024-01-25  9:09 dpdklab
2024-01-24  6:54 dpdklab
2024-01-23  6:29 dpdklab
2024-01-22  7:27 dpdklab
2024-01-20 14:16 dpdklab
2024-01-20  4:10 dpdklab
2024-01-20  3:48 dpdklab
2024-01-18 20:05 dpdklab
2024-01-17 20:03 dpdklab
2024-01-16 16:47 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=65ace2b5.050a0220.55db6.0c92SMTPIN_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).