From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(121771) sid(26457) job(DTS_AUTO_2318) [V1] tests/vf_offload: fix syntax errors
Date: 10 Jan 2023 00:08:29 -0800 [thread overview]
Message-ID: <0ff686$nq9o8g@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/121771
Subject: [V1] tests/vf_offload: fix syntax errors
_Testing issues_
Diff:
tests/TestSuite_vf_offload.py
DPDK:
commit fe2c18a0a8b22703dec3add385a371ad819d7872
Author: David Marchand <david.marchand@redhat.com>
Date: Mon Jan 9 11:03:37 2023 +0100
Comment: hash: fix GFNI implementation build with GCC 12
DTS:
commit f0eb201864786a632fa93e7215b1c789e7b9f7b9
Author: Wei Ling <weix.ling@intel.com>
Date: Wed Jan 4 13:32:57 2023 +0800
Comment: tests/virtio_user_for_container_networking: modify hard code
Test environment and result as below:
+------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+------------+----------+--------------------------------+---------------------------------+
| vf_offload | NIC VF | run | not run |
+------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/10432a2851c94b5fb7486e83c036c58e
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.5 LTS
Kernel: 5.4.0-135-generic
CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: NA
Status: FAILURE
Catogory: NIC VF
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 5/0/0/5/0
with_patch Total/Pass/Fail/Blocked/NA: 5/0/0/5/0
Detail test results:
+------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+------------------------------------------------+------------+---------------+
| vf_offload/test_checksum_offload_disable | blocked | blocked |
| vf_offload/test_tso_tunnel | blocked | blocked |
| vf_offload/test_checksum_offload_tunnel_enable | blocked | blocked |
| vf_offload/test_checksum_offload_enable | blocked | blocked |
| vf_offload/test_tso | blocked | blocked |
+------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2023-01-10 8:09 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='0ff686$nq9o8g@fmsmga001-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.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).