automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw63940devtools: avoid config backup during test build setup
Date: 16 Dec 2019 08:48:56 -0800	[thread overview]
Message-ID: <ee68f5$8rupdh@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/63940

_apply issues_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: 2019-12-16 16:22:42
Reply_mail: 20191216162242.1898285-1-thomas@monjalon.net
DPDK git baseline:
	Repo:dpdk, CommitID: c3e89f69facbbfe131b6a6723665d48801ac943d

*Repo: dpdk
net/mlx: fix build with clang 9
    
    This rewrites the MKSTR macro appending an empty string to its arguments
    to resolve build failures similar to:
    
      drivers/net/mlx4/mlx4.c:461:14: fatal error: format string is not a
      string literal [-Wformat-nonliteral]
              MKSTR(path, "%s/device/uevent", device->ibdev_path);
    
      drivers/net/mlx4/mlx4_utils.h:82:30: note: expanded from macro 'MKSTR'
              char name[snprintf(NULL, 0, __VA_ARGS__) + 1]; \
    
      drivers/net/mlx5/mlx5_stats.c:144:15: fatal error: format string is not a
      string literal [-Wformat-nonliteral]
            MKSTR(path, "%s/ports/%d/hw_counters/%s",
    
      drivers/net/mlx5/mlx5_utils.h:149:30: note: expanded from macro 'MKSTR'
            char name[snprintf(NULL, 0, __VA_ARGS__) + 1]; \
--
				sed -ri="" "s,($pattern=)n,\1y," $1/.config
			fi
		done
	fi

error: patch failed: devtools/test-build.sh:141
error: devtools/test-build.sh: patch does not apply

DPDK STV team

                 reply	other threads:[~2019-12-16 16:49 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='ee68f5$8rupdh@orsmga001.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).