From: "Yigit, Ferruh" <ferruh.yigit@intel.com>
To: sys_stv <sys_stv@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>
Subject: Re: [dpdk-test-report] |ERROR| pw 8767 mk: fix ABI versioning compile error for combined shared library
Date: Fri, 6 Nov 2015 15:32:27 +0000 [thread overview]
Message-ID: <9A3E4DCF947BAB4FBECB1FA88D4D67891E8208B0@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <edcf24$hnn6id@FMSMGA003.fm.intel.com>
This patches updates makefiles, related to the combined shared library. It should has no functional effect. And unless shared combined library compilation enabled, this should effect nothing at all.
Is it possible to double check failed test case?
Thanks,
ferruh
> -----Original Message-----
> From: sys_stv
> Sent: Friday, November 6, 2015 3:27 PM
> To: test-report@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>
> Subject: |ERROR| pw 8767 mk: fix ABI versioning compile error for combined
> shared library
>
> Test-Label: Intel Niantic on Fedora
> Test-Status: ERROR
> Patchwork: http://www.dpdk.org/dev/patchwork/patch/8767/
>
> DPDK git baseline: c4d404d7c1257465176deb5bb8c84e627d2d5eee
> Patchwork ID: 8767
> http://www.dpdk.org/dev/patchwork/patch/8767/
> Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
> Date: Fri, 6 Nov 2015 13:58:05 +0000
>
> Source Compilation:
> OS: fedora
> Nic: niantic
> i686-native-linuxapp-gcc: compile pass
> x86_64-native-linuxapp-gcc: compile pass
>
> DTS validation:
> OS: fedora
> Nic: Niantic
> TestType: auto
> GCC: 4
> x86_64-native-linuxapp-gcc: total 79, passed 78, failed 1.
> Failed Case List:
> Target: x86_64-native-linuxapp-gcc
> OS: fedora
> Failed DTS case:
> link_bonding:
> http://dpdk.org/browse/tools/dts/tree/test_plans/unit_tests_eal_test_plan.
> rst
>
> DTS Validation Error:
> ================================================================
> ========================================================
> ================================================================
> ========================================================
> TEST SUITE : TestUnitTestsEal
> [SUITE_DUT_CMD] make -j -C ./app/test/
>
> -------------------------------------------------------------------------------
> Begin: Test Casetest_link_bonding
> --------------------------------------------------
> FAILED 'Test failed'
> --------------------------------------------------
> [SUITE_DUT_CMD] ./app/test/test -n 1 -c ffff
> [SUITE_DUT_CMD] link_bonding_autotest
> [SUITE_DUT_CMD] quit
> End test_link_bonding
> -------------------------------------------------------------------------------
>
>
>
> DPDK STV team
prev parent reply other threads:[~2015-11-06 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:26 sys_stv
2015-11-06 15:32 ` Yigit, Ferruh [this message]
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=9A3E4DCF947BAB4FBECB1FA88D4D67891E8208B0@IRSMSX101.ger.corp.intel.com \
--to=ferruh.yigit@intel.com \
--cc=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).