From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
"liufengjiang.0426" <liufengjiang.0426@bytedance.com>
Subject: |WARNING| pw132424 [PATCH] net/virtio: fixed missing next flag when
Date: Mon, 09 Oct 2023 14:27:22 -0700 (PDT) [thread overview]
Message-ID: <6524703a.630a0220.5cef8.e248SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/132424
_Testing issues_
Submitter: liufengjiang.0426 <liufengjiang.0426@bytedance.com>
Date: Monday, October 09 2023 13:06:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132424 --> 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): ====
[2720/2735] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_memcpy_perf.c.o'.
[2721/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_hmac.c.o'.
[2722/2735] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_table_combined.c.o'.
[2723/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_cmac.c.o'.
[2724/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_xts.c.o'.
[2725/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_tdes.c.o'.
[2726/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_sha.c.o'.
[2727/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_rsa.c.o'.
[2728/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_validation_ecdsa.c.o'.
[2729/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_main.c.o'.
[2730/2735] Compiling C object 'examples/c590b3c@@dpdk-fips_validation@exe/fips_validation_fips_dev_self_test.c.o'.
[2731/2735] Linking target examples/dpdk-fips_validation.
[2732/2735] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_trace_perf.c.o'.
[2733/2735] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring_perf.c.o'.
[2734/2735] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ring.c.o'.
[2735/2735] Linking target app/dpdk-test.
Processing file ../out/acvp-aes-cbc-vectors.json... Done
Processing file ../out/acvp-aes-gmac-vectors.json... 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: 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/27861/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2023-10-09 21:27 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=6524703a.630a0220.5cef8.e248SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=liufengjiang.0426@bytedance.com \
--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).