Call for help - understanding how to debug sw module

[Chris Sherlock]

If it is at all helpful, these are the hardware specs (this machine is seriously overkill, I got it with redundancy money a year ago):

Hardware Overview:

  Model Name:	iMac
  Model Identifier:	iMac15,1
  Processor Name:	Intel Core i5
  Processor Speed:	3.5 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	6 MB
  Memory:	8 GB

AMD Radeon R9 M290X:

  Chipset Model:	AMD Radeon R9 M290X
  Type:	GPU
  Bus:	PCIe
  PCIe Lane Width:	x16
  VRAM (Total):	2048 MB
  Vendor:	ATI (0x1002)
  Device ID:	0x6810
  Revision ID:	0x0000
  ROM Revision:	113-C408A0-729
  EFI Driver Version:	01.00.729
  Displays:
iMac:
  Display Type:	Retina LCD
  Resolution:	5120 x 2880 Retina
  Retina:	Yes
  Pixel Depth:	30-Bit Color (ARGB2101010)
  Main Display:	Yes
  Mirror:	Off
  Online:	Yes
  Built-In:	Yes


At this point, I’m sort of wondering if the resolution of my screen might be part of the issue… another user sent me their specs and it seems that the other Retina displays are on laptops…

Chris



> On 28 Jan 2016, at 12:13 PM, Chris Sherlock <chris.sherlock79 at gmail.com> wrote:
> 
> Hey guys, 
> 
> I know a few people have built on a Retina based Mac and haven’t had this issue…
> 
> Any ideas why this might be occurring?
> 
> Chris
> 
>> On 22 Jan 2016, at 11:07 AM, Chris Sherlock <chris.sherlock79 at gmail.com> wrote:
>> 
>> Hi all, 
>> 
>> I’m getting an error that never appears to any of the OS X buildbots or tinderboxes. I suspect that it has something to do with the fact that I have a Retina iMac. 
>> 
>> Basically, the unit test that is failing is in CppunitTest_sw_ooxmlimport:
>> 
>> Test name: testGroupshapeChildRotation::Import
>> equality assertion failed
>> - Expected: 686
>> - Actual  : 688
>> 
>> Failures !!!
>> Run: 208   Failure total: 1   Failures: 1   Errors: 0
>> 
>> I’ve got an Ubuntu pastebin of the error here:
>> 
>> http://paste.ubuntu.com/14593673/
>> 
>> Can anyone give me any pointer on how I would even *start* to troubleshoot this? A good start is a pointer to the code that this actually runs, because whilst I can read the test code, I have no knowledge of sw whatsoever and I’d like to know where in the code the size is failing on my machine. 
>> 
>> Thanks in advance for any help!
>> 
>> Chris
>