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] a409653a123bf105970a25c594711a3cdc44d139
Date: Wed, 17 Jul 2024 07:56:39 -0700 (PDT)	[thread overview]
Message-ID: <6697dba7.050a0220.89785.2804SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v22.11

a409653a123bf105970a25c594711a3cdc44d139 --> testing issues

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | dpdk_fips_validation | compressdev_zlib_pmd |
+====================+======================+======================+
| Ubuntu 20.04       | WARN                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04       | SKIPPED              | PASS                 |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 (ARM) | SKIPPED              | PASS                 |
+--------------------+----------------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
[3521/3534] Linking target app/dpdk-test-pipeline.
[3522/3534] Linking target app/dpdk-dumpcap.
[3523/3534] Linking target app/dpdk-test-gpudev.
[3524/3534] Linking target app/dpdk-test-compress-perf.
[3525/3534] Linking target app/dpdk-test-flow-perf.
[3526/3534] Linking target app/dpdk-proc-info.
[3527/3534] Linking target app/dpdk-testpmd.
[3528/3534] Linking target app/dpdk-test-sad.
[3529/3534] Linking target app/dpdk-test-security-perf.
[3530/3534] Linking target app/dpdk-pdump.
[3531/3534] Linking target app/dpdk-test-eventdev.
[3532/3534] Linking target examples/dpdk-fips_validation.
[3533/3534] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring.c.o'.
[3534/3534] Linking target app/test/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... Done
Processing file ../out/acvp-aes-ctr-vectors.json...
==== End log output ====

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

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29653/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-17 14:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 14:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-17 14:33 dpdklab
2024-07-02 10:32 dpdklab
2024-07-01  6:42 dpdklab
2024-06-21 11:17 dpdklab
2024-06-21 11:13 dpdklab
2024-06-21 11:12 dpdklab
2024-06-14  9:44 dpdklab
2024-05-30  6:17 dpdklab
2024-05-30  6:06 dpdklab
2024-05-30  6:05 dpdklab
2024-05-30  6:05 dpdklab
2024-05-30  6:05 dpdklab
2024-05-30  6:04 dpdklab
2024-05-30  6:00 dpdklab
2024-05-30  5:59 dpdklab
2024-05-30  5:57 dpdklab
2024-05-30  5:56 dpdklab
2024-05-30  5:35 dpdklab
2024-05-30  5:34 dpdklab
2024-05-30  5:32 dpdklab
2024-05-30  5:25 dpdklab
2024-05-30  5: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=6697dba7.050a0220.89785.2804SMTPIN_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).