automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, michaelba@nvidia.com
Subject: [dpdk-test-report] |WARNING| pw(122976) sid(26766) job(PER_PATCH_BUILD6197)[v2, 8/8] compress/mlx5: add support for LZ4 algorithm
Date: 02 Feb 2023 08:39:13 -0800	[thread overview]
Message-ID: <e661bc$iaqtb6@orsmga003-auth.jf.intel.com> (raw)

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


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

_apply issues_

Submitter: Michael Baum <michaelba@nvidia.com>
Date: 2023-02-02 16:25:37
Reply_mail: <20230202162537.1067595-9-michaelba@nvidia.com>

DPDK git baseline:
	Repo:dpdk, CommitID: 7e40372522c5a129da616d1420ff582968b81b46


* Repo: dpdk
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/compress/mlx5/mlx5_compress.c:70
error: drivers/compress/mlx5/mlx5_compress.c: patch does not apply
Applying: compress/mlx5: fix decompress xform validation
Applying: compress/mlx5: fix wrong output Adler-32 checksum offset
--
Applying: compress/mlx5: add xform validate function
Applying: common/mlx5: add LZ4 capabilities check
Applying: compress/mlx5: add support for LZ4 algorithm
Patch failed at 0008 compress/mlx5: add support for LZ4 algorithm
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-02-02 16:39 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='e661bc$iaqtb6@orsmga003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=michaelba@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).