fritzo / googlemock

Automatically exported from code.google.com/p/googlemock
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Tests for the pretty-printer don't work properly on big-endian architectures #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. make check on a big-endian architecture.

What is the expected output? What do you see instead?
I'm seeing a failure in the unit tests of googlemock on OSX 10.4 on PowerPC

../test/gmock-printers_test.cc:800: Failure
Value of: Print(UnprintableTemplateInGlobal<bool>())
 Actual: "4-byte object <0000 0000>"
Expected: "1-byte object <00>"
[  FAILED  ] PrintUnprintableTypeTest.InGlobalNamespace
[...]
../test/gmock-printers_test.cc:806: Failure
Value of: Print(::foo::UnprintableInFoo())
 Actual: "16-byte object <0000 12EF 0000 AB34 0000 0000 0000 0000>"
Expected: "16-byte object <EF12 0000 34AB 0000 0000 0000 0000 0000>"
[  FAILED  ] PrintUnprintableTypeTest.InUserNamespace
[...]
../test/gmock-printers_test.cc:888: Failure
Value of: PrintByRef(x)
 Actual: "@0xbffff07c 16-byte object <0000 12EF 0000 AB34 0000 0000 0000 0000>"
Expected: "@" + PrintPointer(&x) + " 16-byte object " "<EF12 0000 34AB
0000 0000 0000 0000 0000>"
Which is: "@0xbffff07c 16-byte object <EF12 0000 34AB 0000 0000 0000 0000
0000>"
[  FAILED  ] PrintReferenceTest.PrintsAddressAndValue
[...]
[  FAILED  ] 3 tests, listed below:
[  FAILED  ] PrintUnprintableTypeTest.InGlobalNamespace
[  FAILED  ] PrintUnprintableTypeTest.InUserNamespace
[  FAILED  ] PrintReferenceTest.PrintsAddressAndValue

 3 FAILED TESTS
FAIL: test/gmock-printers_test

Note that this only affects pretty-printing of values on big-endian
machines, so it's not a big deal.

Please use labels and text to provide additional information.
Darwin 8.8.0 Darwin Kernel Version 8.8.0: Fri Sep  8 17:18:57 PDT
2006; root:xnu-792.12.6.obj~1/RELEASE_PPC Power Macintosh powerpc
powerpc-apple-darwin8-g++-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367)

Original issue reported on code.google.com by tsuna...@gmail.com on 11 Dec 2008 at 11:21

GoogleCodeExporter commented 9 years ago

Original comment by shiq...@gmail.com on 16 Dec 2008 at 4:27

GoogleCodeExporter commented 9 years ago

Original comment by shiq...@gmail.com on 22 Dec 2008 at 8:04

GoogleCodeExporter commented 9 years ago

Original comment by zhanyong...@gmail.com on 4 Mar 2009 at 7:11

GoogleCodeExporter commented 9 years ago
Not worth it.  If someone submits a patch, we may take it.

Original comment by w...@google.com on 6 Mar 2010 at 5:47