automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, rongweil@nvidia.com
Subject: [dpdk-test-report] |WARNING| pw(122693) sid(26693) job(PER_PATCH_BUILD6129)[v3, 11/11] app/testpmd: adjust cleanup sequence when quitting
Date: 30 Jan 2023 05:28:27 -0800	[thread overview]
Message-ID: <e98db8$j3qej1@orsmga006-auth.jf.intel.com> (raw)

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


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/122693

_apply issues_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: 2023-01-30 13:20:00
Reply_mail: <20230130132000.1715473-12-rongweil@nvidia.com>

DPDK git baseline:
	Repo:dpdk-next-net, CommitID: 02ae4c526efd88d858d8f04fc0ef339238ef5d99
	Repo:dpdk, CommitID: 2a211079a92e962bbd0ec81e425a6ffc32890e67


* Repo: dpdk-next-net
app/testpmd: fix interactive mode with no ports
    
    Testpmd terminated unconditionally if it failed to start all ports.
    
    The patch allows testpmd to get into the command line,
    if the interactive mode was requested.
--
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: drivers/common/mlx5/mlx5_prm.h:760
error: drivers/common/mlx5/mlx5_prm.h: patch does not apply
Applying: ethdev: add flex item modify field support
Applying: app/testpmd: pass flex handle into matching mask
--
Applying: net/mlx5: adopt new flex item prm definition
Applying: net/mlx5/hws: add hws flex item matching support
Applying: net/mlx5: add flex item modify field implementation
Patch failed at 0007 net/mlx5: add flex item modify field implementation
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".

* Repo: dpdk
When building QAT PMD, the following issue comes up:
    
    intel-ipsec-mb.h:333: error: "AES_BLOCK_SIZE" redefined
      333 | #define AES_BLOCK_SIZE          IMB_AES_BLOCK_SIZE
    In file included from drivers/crypto/qat/qat_sym_session.c:8:
    /usr/include/openssl/aes.h:26: previous definition
--
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: drivers/common/mlx5/mlx5_prm.h:760
error: drivers/common/mlx5/mlx5_prm.h: patch does not apply
Applying: ethdev: add flex item modify field support
Applying: app/testpmd: pass flex handle into matching mask
--
Applying: net/mlx5: adopt new flex item prm definition
Applying: net/mlx5/hws: add hws flex item matching support
Applying: net/mlx5: add flex item modify field implementation
Patch failed at 0007 net/mlx5: add flex item modify field implementation
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:[~2023-01-30 13:28 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='e98db8$j3qej1@orsmga006-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=rongweil@nvidia.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).