Closed Bug 744481 Opened 12 years ago Closed 12 years ago

OS X 10.7 builds busted on the profiling branch

Categories

(Release Engineering :: General, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)

References

Details

(Whiteboard: [profiling])

Attachments

(1 file)

https://tbpl.mozilla.org/php/getParsedLog.php?id=10802053&tree=Profiling&full=1

This prevents people on Mac from getting Nightly updates from that branch.  :(

Is this the same problem as shark builds being broken on the new builders?  Can we use the older builders for this branch until that bug gets fixed?
(In reply to Ehsan Akhgari [:ehsan] from comment #0)
> https://tbpl.mozilla.org/php/getParsedLog.
> php?id=10802053&tree=Profiling&full=1
> 
> This prevents people on Mac from getting Nightly updates from that branch. 
> :(
> 
> Is this the same problem as shark builds being broken on the new builders? 
> Can we use the older builders for this branch until that bug gets fixed?

Yes, this is the same issue.  The code needed to switch you guys back is trivial, but those machines are going away sometime in the next two months.
This is the patch that we would need to have profiling builds back on 10.6
Attachment #614070 - Flags: review?(bhearsum)
What would it take to enable shark builds on 10.7?  Is that even possible?
Depends on: 723301
(In reply to Ehsan Akhgari [:ehsan] from comment #3)
> What would it take to enable shark builds on 10.7?  Is that even possible?

There isn't a known way to install CHUD (the required subsystem) on 10.7 and without it, we can't complete the builds.
Comment on attachment 614070 [details] [diff] [review]
move profilng branch back to 10.6 based machines

Review of attachment 614070 [details] [diff] [review]:
-----------------------------------------------------------------

i hate our configs
Attachment #614070 - Flags: review?(bhearsum) → review+
Has anyone looked at using Instruments instead of Shark? 

Using 10.6 builders should be considered a stop-gap measure at best. These are running on the oldest minis we currently have in service. They are out of warranty and are slowly dieing.
Assignee: nobody → jhford
Priority: -- → P2
Whiteboard: [profiling]
As far as I know, Boris is the only user of our shark builds ;)

So he should be in the loop here.
So some general comments:

1)  I'm _running_ on 10.6 right now, not 10.7.  One of the major reasons is that Shark
    works on 10.6, Shark does not work on 10.7, and there is no decent Instruments
    integration on 10.7 yet, so it's not a replacement for Shark.
2)  Using Instruments instead of Shark (probably with Peter's patches for Instruments
    integration) is the long-term way forward.
3)  For now, pending that, the right thing to do is to either keep the profiling builds on
    10.6 or to switch them from --enable-shark to --enable-profiling (which would take out
    the programmatic Shark hooks, but leave the stack-walking capabilities).
I ended up removing --enable-shark for 10.7 builders <https://hg.mozilla.org/projects/profiling/rev/574aad51da6b>, so this should be fixed now.
Assignee: jhford → ehsan
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: