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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw137458 [PATCH] [v3] lib/hash: add siphash
Date: Sat, 02 Mar 2024 00:02:52 -0800 (PST)	[thread overview]
Message-ID: <65e2dd2c.1f0a0220.8649b.b6b7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229003201.186997-2-stephen@networkplumber.org>

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, February 29 2024 00:32:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137458 --> 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): ====
[2827/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_tables.c.o'.
[2828/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2829/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_thash.c.o'.
[2830/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_timer_secondary.c.o'.
[2831/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2832/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_cmac.c.o'.
[2833/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2834/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_gcm.c.o'.
[2835/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2836/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2837/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2838/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ccm.c.o'.
[2839/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation.c.o'.
[2840/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2841/2846] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2842/2846] Linking target examples/dpdk-fips_validation.
[2843/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2844/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2845/2846] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2846/2846] Linking target app/dpdk-test.
==== 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/patchsets/29324/

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-02  8:02 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229003201.186997-2-stephen@networkplumber.org>
2024-02-29  0:10 ` |SUCCESS| pw137458 [PATCH v3] " qemudev
2024-02-29  0:15 ` qemudev
2024-02-29  0:33 ` checkpatch
2024-02-29  1:08 ` |SUCCESS| pw137458 [PATCH] [v3] " dpdklab
2024-02-29  1:08 ` dpdklab
2024-02-29  1:08 ` dpdklab
2024-02-29  1:08 ` dpdklab
2024-02-29  1:08 ` dpdklab
2024-02-29  1:09 ` dpdklab
2024-02-29  1:09 ` dpdklab
2024-02-29  1:09 ` dpdklab
2024-02-29  1:10 ` dpdklab
2024-02-29  1:10 ` dpdklab
2024-02-29  1:10 ` dpdklab
2024-02-29  1:11 ` dpdklab
2024-02-29  1:11 ` dpdklab
2024-02-29  1:11 ` dpdklab
2024-02-29  1:12 ` dpdklab
2024-02-29  1:12 ` dpdklab
2024-02-29  1:12 ` dpdklab
2024-02-29  1:12 ` dpdklab
2024-02-29  1:13 ` dpdklab
2024-02-29  1:13 ` dpdklab
2024-02-29  1:13 ` dpdklab
2024-02-29  1:13 ` dpdklab
2024-02-29  1:14 ` dpdklab
2024-02-29  1:14 ` dpdklab
2024-02-29  1:15 ` dpdklab
2024-02-29  1:15 ` dpdklab
2024-02-29  1:15 ` dpdklab
2024-02-29  1:15 ` dpdklab
2024-02-29  1:16 ` dpdklab
2024-02-29  1:16 ` dpdklab
2024-02-29  1:17 ` dpdklab
2024-02-29  1:17 ` dpdklab
2024-02-29  1:23 ` dpdklab
2024-02-29  1:23 ` dpdklab
2024-02-29  1:25 ` |SUCCESS| pw137458 [PATCH v3] " 0-day Robot
2024-02-29  1:25 ` |SUCCESS| pw137458 [PATCH] [v3] " dpdklab
2024-02-29  1:26 ` dpdklab
2024-02-29  1:26 ` dpdklab
2024-02-29  1:26 ` dpdklab
2024-02-29  1:26 ` dpdklab
2024-02-29  1:26 ` dpdklab
2024-02-29  1:27 ` dpdklab
2024-02-29  1:28 ` dpdklab
2024-02-29  1:28 ` dpdklab
2024-02-29  1:28 ` dpdklab
2024-02-29  1:29 ` dpdklab
2024-02-29  1:29 ` dpdklab
2024-02-29  1:29 ` dpdklab
2024-02-29  1:30 ` dpdklab
2024-02-29  1:30 ` dpdklab
2024-02-29  1:34 ` dpdklab
2024-02-29  1:37 ` dpdklab
2024-02-29  1:44 ` dpdklab
2024-02-29  1:44 ` dpdklab
2024-02-29  1:44 ` dpdklab
2024-02-29  1:44 ` dpdklab
2024-02-29  1:44 ` dpdklab
2024-02-29  1:45 ` dpdklab
2024-02-29  1:50 ` dpdklab
2024-02-29  1:52 ` dpdklab
2024-02-29  1:52 ` dpdklab
2024-02-29  1:53 ` dpdklab
2024-02-29  1:53 ` dpdklab
2024-02-29  1:54 ` dpdklab
2024-02-29  2:40 ` dpdklab
2024-03-01  1:30 ` dpdklab
2024-03-01  1:32 ` dpdklab
2024-03-01  1:42 ` dpdklab
2024-03-01  1:45 ` dpdklab
2024-03-01 10:17 ` |WARNING| " dpdklab
2024-03-02  6:58 ` |SUCCESS| " dpdklab
2024-03-02  7:30 ` dpdklab
2024-03-02  8:02 ` dpdklab [this message]
2024-03-02 21:19 ` 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=65e2dd2c.1f0a0220.8649b.b6b7SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).