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,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: |WARNING| pw129447-129449 [PATCH] [v6,2/2] doc: add mlx5 datapath tr
Date: Tue, 11 Jul 2023 22:15:57 -0700 (PDT)	[thread overview]
Message-ID: <64ae370d.810a0220.bb2b2.8077SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/129449

_Testing issues_

Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, July 11 2023 15:15:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24

129447-129449 --> 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): ====
[2718/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2719/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2720/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2721/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_cmac.c.o'.
[2722/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2723/2732] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_pdcp.c.o'.
[2724/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2725/2732] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_link_bonding.c.o'.
[2726/2732] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_compressdev.c.o'.
[2727/2732] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2728/2732] Linking target examples/dpdk-fips_validation.
[2729/2732] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_trace_perf.c.o'.
[2730/2732] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring_perf.c.o'.
[2731/2732] Compiling C object 'app/test/3062f5d@@dpdk-test@exe/test_ring.c.o'.
[2732/2732] Linking target app/test/dpdk-test.
Processing file ../out/acvp-aes-cbc-vectors.json... 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... Done
==== End log output ====

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2023-07-12  5:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=64ae370d.810a0220.bb2b2.8077SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=viacheslavo@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).