automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, ke1.xu@intel.com
Subject: [dts-test-report] |FAILURE| pw(121286-121290) sid(26247) job(DTS_AUTO_2155) [V4, 5/5] tests/vf_offload: add new method to anayse tunnel packets.
Date: 22 Dec 2022 18:47:29 -0800	[thread overview]
Message-ID: <649fab$la7es7@fmsmga008-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/121290
Subject: [V4,5/5] tests/vf_offload: add new method to anayse tunnel packets.

_Apply issues_

Diff:
	tests/TestSuite_vf_offload.py

DPDK:
	commit 373f4c7de8ff350548cacc3d56e788461677f2c7
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Tue Dec 13 16:07:10 2022 +0100
	Comment: ci: drop Travis configuration

DTS:
	commit 6640ecb3ebc5347139df2530bdfd2fa5421b6a47
	Author: Lingli Chen <linglix.chen@intel.com>
	Date:   Thu Dec 15 01:42:04 2022 -0500
	Comment: tests/rss_to_rte_flow: remove --pkt-filter-mode sync dpdk change

DTS git baseline:
	Repo:dts, CommitID: 6640ecb3ebc5347139df2530bdfd2fa5421b6a47



* Repo: dts
Applying: tests/vf_offload: dts adaptation DPDK checksum function changes
error: sha1 information is lacking or useless (tests/TestSuite_vf_offload.py).
error: could not build fake ancestor
Patch failed at 0004 tests/vf_offload: dts adaptation DPDK checksum function changes
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team

                 reply	other threads:[~2022-12-23  2:47 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='649fab$la7es7@fmsmga008-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=ke1.xu@intel.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).