Closed
Bug 500007
Opened 15 years ago
Closed 15 years ago
try server OSX builds should include symbols for Shark
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: vlad, Assigned: coop)
Details
Attachments
(1 file)
425 bytes,
patch
|
nthomas
:
review+
coop
:
checked-in+
|
Details | Diff | Splinter Review |
When these builds are created to test performance-related patches, it's helpful to be able to profile them. Can we include the same set of symbols that we do in the shark builds? (Function symbols only)
Assignee | ||
Comment 1•15 years ago
|
||
Vlad: is this a dupe of bug 495030? Armen's going to do some work in that bug today to try to generate symbols in a fashion similar to nightlies/releases.
Comment 2•15 years ago
|
||
This would be as simple as adding "ac_add_options --disable-install-strip" to the mozconfig: http://hg.mozilla.org/build/buildbot-configs/file/3bf03608f457/mozilla2/macosx/mozilla-central/shark/mozconfig#l19 (that instructs the packager not to strip out debug symbols).
Assignee | ||
Comment 3•15 years ago
|
||
Running a new mozconfig through the try server now.
Assignee: nobody → ccooper
Status: NEW → ASSIGNED
Priority: -- → P2
Comment 4•15 years ago
|
||
We'd should check if tests like Ts are affected at all. If so, someone would have to make a call about the utility of talos comparisons vs full symbols.
Assignee | ||
Comment 5•15 years ago
|
||
Vlad: can you check the build at http://build.mozilla.org/tryserver-builds/coop@mozilla.com-1245951407 for symbols? It was generated with this patched mozconfig.
Assignee | ||
Comment 6•15 years ago
|
||
I made another run (http://build.mozilla.org/tryserver-builds/coop@mozilla.com-1249419341) and verified that the symbols are present in shark. As for ts, looking at some comparative graphs: try run, tiger: 1052.89 m-c talos tiger (3, avg): ~1010, ~1010, ~1125 http://graphs-stage.mozilla.org/graph.html#tests=[{%22test%22:%2212%22,%22branch%22:%226%22,%22machine%22:%22126%22},{%22test%22:%2212%22,%22branch%22:%221%22,%22machine%22:%22278%22},{%22test%22:%2212%22,%22branch%22:%221%22,%22machine%22:%22277%22},{%22test%22:%2212%22,%22branch%22:%221%22,%22machine%22:%22276%22}] try run leopard (2): 1375.32, 1390.79 m-c leopard (avg): ~1535 http://graphs-stage.mozilla.org/graph.html#tests=[{%22test%22:%2212%22,%22branch%22:%226%22,%22machine%22:%22238%22},{%22test%22:%2212%22,%22branch%22:%226%22,%22machine%22:%22237%22},{%22test%22:%2212%22,%22branch%22:%221%22,%22machine%22:%22141%22}]
Assignee | ||
Comment 7•15 years ago
|
||
Bugzilla isn't marking up the links well, so I'll try again: Tiger graph: http://bit.ly/xl9yA Leopard graph: http://bit.ly/eW5cy
Assignee | ||
Comment 8•15 years ago
|
||
Comment on attachment 385199 [details] [diff] [review] Disable install strip for Mac try server builds Ts doesn't seem unduly affected IMO.
Attachment #385199 -
Flags: review?(nthomas)
Updated•15 years ago
|
Attachment #385199 -
Flags: review?(nthomas) → review+
Comment 9•15 years ago
|
||
Comment on attachment 385199 [details] [diff] [review] Disable install strip for Mac try server builds > Ts doesn't seem unduly affected IMO. Agreed. There's a Tp3 RSS spike - about 30M or 1% on Leopard, and something similar on Tiger, but that doesn't seem like the end of the world. Do you know why the mac unit test build bombed out ?
Assignee | ||
Comment 10•15 years ago
|
||
(In reply to comment #9) > Agreed. There's a Tp3 RSS spike - about 30M or 1% on Leopard, and something > similar on Tiger, but that doesn't seem like the end of the world. Do you know > why the mac unit test build bombed out ? Huh, I thought I had killed all the other builds I didn't care about. I'll run it again before pushing and make sure it's not something dangerous.
Assignee | ||
Comment 11•15 years ago
|
||
(In reply to comment #9) > Agreed. There's a Tp3 RSS spike - about 30M or 1% on Leopard, and something > similar on Tiger, but that doesn't seem like the end of the world. Do you know > why the mac unit test build bombed out ? The issue here is that unittests use their own configs. I provided a new mozconfig through the interface that had --disable-tests specified (the non-unittest default), but the new mozconfig gets used by all slaves regardless of platform or test payload. Supplying a proper unittest config with the stripping disabled works fine, i.e. shows same warnings as current trunk: http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1249653693.1249661307.17858.gz&fulltext=1 Going to carry-forward the review to land the strip change for the unittest config as well, if that's ok.
Assignee | ||
Comment 12•15 years ago
|
||
Comment on attachment 385199 [details] [diff] [review] Disable install strip for Mac try server builds http://hg.mozilla.org/build/buildbot-configs/rev/b9921f77d54b
Attachment #385199 -
Flags: checked-in+
Assignee | ||
Comment 13•15 years ago
|
||
Updated the buildbot-configs clones on the tryserver masters.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•