32-bit lion builds show up under the 64-bit lion debug build row



Tree Management Graveyard
6 years ago
3 years ago


(Reporter: jhford, Assigned: philor)


Mac OS X
Dependency tree / graph



(1 attachment)

Example builder names involved here:
OS X 10.7 32-bit build-system leak test build
OS X 10.7 64-bit build-system leak test build

Right now, this shows up as

OS X 10.7 opt   B
OS X 10.7 debug B B

Which is fine because tests haven't been run, so things aren't confusing yet.  Once tests are run, the tests that correspond to the 32-bit debug build show up in a different row than the tests that are run against them, like:

OS X opt        1 2 3 4 5 oth C J R X T c di dr n s
OS X debug      1 2 3 4 5 oth C J R X
OS X64 opt      1 2 3 4 5 oth C J R X T c di dr n s
OS X64 debug    1 2 3 4 5 oth C J R X
OS X 10.7 opt   B 3 4 C J R T c di dr n s
OS X 10.7 debug B B 4 J

We should move the 32-bit debug builds to the 'OS X debug row', especially since we only run 32-bit tests on the 32-bit builds.
Blocks: 720027
Worth noting, however, is that the OS X rows are traditionally the '10.5' rows.  This would continue to hold true for the tests, but the builds would still be done on 10.7.

Comment 2

6 years ago
Created attachment 613507 [details] [diff] [review]

I don't actually like this, but after I wrote a patch to do them as B32 and B64 on the 10.7 row, and rename "OS X" to 10.5 and "OS X64" to 10.6, and stared at it a while, I decided I liked this better than that. At least this gets obsolete nicely, and once we start running 10.8 (hidden and broken, no doubt) and drop 10.5, and nobody needs to know whether we're running our 32-bit Mac app because we aren't, we can do the renaming then.
Assignee: nobody → philringnalda
Attachment #613507 - Flags: review?(mstange)
Attachment #613507 - Flags: review?(mstange) → review+


6 years ago
Depends on: 743595


6 years ago
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.