From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(88691) [5/5] compress/mlx5: add timestamp format support
Date: 07 Mar 2021 02:06:11 -0800 [thread overview]
Message-ID: <9fae05$c605p3@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/88691
_apply issues_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: 2021-03-07 10:02:51
Reply_mail: 20210307100251.22538-6-viacheslavo@nvidia.com
DPDK git baseline:
Repo:dpdk, CommitID: 2a2ebeab9e3309ab332baefdbcc1caa7e62ecc82
* Repo: dpdk
fbarray: fix log message on truncation error
When file truncation fails, the log message attempts to print a path of
file we failed to truncate, but this path was never set to anything and,
what's worse, was uninitialized. Fix it by passing path from the caller.
Coverity issue: 366122
--
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: drivers/net/mlx5/mlx5_devx.c:440
error: drivers/net/mlx5/mlx5_devx.c: patch does not apply
Applying: common/mlx5: add timestamp format support to DevX
Applying: net/mlx5: add timestamp format support
Patch failed at 0002 net/mlx5: add timestamp format support
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:[~2021-03-07 10:06 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='9fae05$c605p3@orsmga008-auth.jf.intel.com' \
--to=sys_stv@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).