automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw26783 [PATCH 1/8] crypto/dpaa2_sec: remove GCC 7.1 compilation error
Date: 11 Jul 2017 10:13:16 -0700	[thread overview]
Message-ID: <e81775$12sufpc@fmsmga001.fm.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE

http://dpdk.org/patch/26783

_Compilation issues_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Tue, 11 Jul 2017 20:25:59 +0530
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:441ea8899e9e4c253737f316891815b07df4c83f

Patch26783-26783 --> compile error
Build Summary: 21 Builds Done, 20 Successful, 1 Failures

Test environment and configuration as below:
OS: RHEL7.2_64
    Kernel Version:3.10.0-514.10.2.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-4)
    Clang Version:3.4.2
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-shared
OS: UB1610_64
    Kernel Version:4.8.0-22-generic
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005
    Clang Version:NA
    x86_64-native-linuxapp-icc
OS: RHEL7.3_64
    Kernel Version:3.10.0-514.16.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-11)
    Clang Version:NA
    x86_64-native-linuxapp-icc
OS: FC25_64
    Kernel Version:4.8.6-300.fc25.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    GCC Version:gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
    Clang Version:NA
    x86_64-native-linuxapp-icc
OS: FreeBSD10.3_64
    Kernel Version:10.3-RELEASE
    CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.98-MHz K8-class CPU)
    GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
    Clang Version:3.4.1
    x86_64-native-bsdapp-clang
    x86_64-native-bsdapp-gcc
OS: CentOS7_64
    Kernel Version:3.10.0-514.10.2.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
    Clang Version:3.4.2
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-clang
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc
OS: FC24_64
    Kernel Version:4.9.13-100.fc24.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
    Clang Version:3.8.0
    x86_64-native-linuxapp-clang
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc-debug
OS: UB1604_64
    Kernel Version:4.4.0-78-generic
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
    GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
    Clang Version:3.8.0
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-clang
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc

Failed Build #1:
OS: RHEL7.3_64
Target: x86_64-native-linuxapp-icc
^
compilation aborted for /home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c (code 2)


DPDK STV team

                 reply	other threads:[~2017-07-11 17:13 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='e81775$12sufpc@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=hemant.agrawal@nxp.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).