automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw50813[v4] drivers: fix possible overflow with strcat
Date: 06 Mar 2019 00:30:51 -0800	[thread overview]
Message-ID: <e75792$4sn6vq@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/50813

_Compilation OK_

Submitter: Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com>
Date: 2019-03-05 13:14:26
Reply_mail: 1551791666-26746-1-git-send-email-tallurix.chaitanya.babu@intel.com
DPDK git baseline: Repo:dpdk-master, CommitID: e892fa595e19b5cce315045444b3b7e31130ef19

Build Summary: 24 Builds Done, 24 Successful, 0 Failures

Test environment and configuration as below:

OS: SUSE15
	Kernel Version: 4.12.14-lp150.12.22-default
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
	Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
	x86_64-native-linuxapp-gcc

OS: CENTOS76
	Kernel Version: 3.10.0-957.5.1.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
	Clang Version: NA
	x86_64-native-linuxapp-gcc

OS: UBT144-32
	Kernel Version: 3.13.0-161-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
	Clang Version: NA
	i686-native-linuxapp-gcc

OS: SUSE12
	Kernel Version: 4.4.73-5-default
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (SUSE Linux) 7.1.1 20170607 [gcc-7-branch revision 248970]
	Clang Version: NA
	x86_64-native-linuxapp-gcc

OS: FreeBSD12.0
	Kernel Version: 12.0-RC3
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.76-MHz K8-class CPU)
	GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
	Clang Version: 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc

OS: UBT144-64
	Kernel Version: 4.2.0-27-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
	Clang Version: NA
	x86_64-native-linuxapp-gcc

OS: CENTOS75
	Kernel Version: 3.10.0-957.5.1.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc

OS: UBT1804
	Kernel Version: 4.15.0-20-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
	Clang Version: NA
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-icc

OS: UBT1810
	Kernel Version: 4.18.0-10-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 8.2.0-7ubuntu1) 8.2.0
	Clang Version: NA
	x86_64-native-linuxapp-gcc

OS: RHEL74
	Kernel Version: 3.10.0-693.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
	Clang Version: NA
	x86_64-native-linuxapp-gcc

OS: CENTOS74
	Kernel Version: 3.10.0-862.14.4.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc

OS: FreeBSD11.2
	Kernel Version: 11.2-RELEASE
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.73-MHz K8-class CPU)
	GCC Version: gcc (FreeBSD Ports Collection) 6.4.0
	Clang Version: 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc

OS: UBT164-64
	Kernel Version: 4.4.0-47-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
	Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
	x86_64-native-linuxapp-gcc

OS: FC28
	Kernel Version: 4.16.3-301.fc28.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.1.1 20180712 (Red Hat 8.1.1-5)
	Clang Version: NA
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-icc

OS: RHEL76
	Kernel Version: 3.10.0-957.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
	Clang Version: NA
	x86_64-native-linuxapp-gcc

OS: FC29
	Kernel Version: 4.18.16-300.fc29.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.2.1 20181215 (Red Hat 8.2.1-6)
	Clang Version: NA
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-icc

OS: RHEL75
	Kernel Version: 3.10.0-862.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)
	Clang Version: NA
	x86_64-native-linuxapp-gcc


DPDK STV team

             reply	other threads:[~2019-03-06  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  8:30 sys_stv [this message]
     [not found] <1551791666-26746-1-git-send-email-tallurix.chaitanya.babu@intel.com>
2019-03-05 13:16 ` [dpdk-test-report] |SUCCESS| pw50813 [v4] " checkpatch

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='e75792$4sn6vq@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).