Bug 1297894 - libndn-cxx-0.4.0 build failure on ppc64
Summary: libndn-cxx-0.4.0 build failure on ppc64
Status: CLOSED DUPLICATE of bug 1275619
Alias: None
Product: Fedora
Classification: Fedora
Component: libndn-cxx
Version: rawhide
Hardware: ppc64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susmit
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: PPCTracker
TreeView+ depends on / blocked
 
Reported: 2016-01-12 17:29 UTC by Ngo Than
Modified: 2016-01-19 13:06 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2016-01-19 13:06:09 UTC


Attachments (Terms of Use)

Description Ngo Than 2016-01-12 17:29:49 UTC
Description of problem:

+ build/unit-tests
Running 607 test cases...
../tests/unit-tests/interest.t.cpp(887): error: in "TestInterest/Decode": check i.getNonce() == 1U has failed [16777216 != 1]
../tests/unit-tests/interest.t.cpp(907): error: in "TestInterest/DecodeFromStream": check i.getNonce() == 1U has failed [16777216 != 1]
../tests/unit-tests/interest.t.cpp(931): error: in "TestInterest/Encode": check { Interest1, Interest1 + sizeof(Interest1) } == { wire.begin(), wire.end() } has failed. 
Mismatch at position 83: 0x1 != 0
Mismatch at position 0x56: 0 != 0x1
../tests/unit-tests/interest.t.cpp(940): error: in "TestInterest/Encode": check { Interest2, Interest2 + sizeof(Interest2) } == { wire.begin(), wire.end() } has failed. 
Mismatch at position 83: 0x2 != 0
Mismatch at position 0x56: 0 != 0x2
*** 4 failures are detected in the test module "ndn-cxx Unit Tests"
Version-Release number of selected component (if applicable):


How reproducible:
always


Steps to Reproduce:
1. ppc-koji build --scratch f24 ppc-koji build --scratch f24 libndn-cxx-0.4.0-1.fc24.src.rpm


Actual results:
http://ppc.koji.fedoraproject.org/kojifiles/work/tasks/9376/3049376/build.log

Expected results:
it should build fine

Comment 1 Susmit 2016-01-12 18:41:30 UTC
Thanks. We are already working on it.

Comment 2 Marcin Juszkiewicz 2016-01-19 13:06:09 UTC

*** This bug has been marked as a duplicate of bug 1275619 ***


Note You need to log in before you can comment on or make changes to this bug.