Closed
Bug 884617
Opened 11 years ago
Closed 11 years ago
Explicitly --disable-threadsafe for the SM(r) build on TBPL
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla28
People
(Reporter: terrence, Assigned: sfink)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
553 bytes,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
We have uncovered several issues recently that were not caught by the rooting analysis because it runs in a significantly different configuration. We should investigate allowing the root analysis to work in threadsafe builds so that we can catch more of these issues.
Reporter | ||
Comment 1•11 years ago
|
||
When we switch to --enable-threadsafe as the default, these builds will start silently succeeding.
Summary: Run the root analysis in threadsafe builds → Explicitly --disable-threadsafe for the SM(r) build on TBPL
Reporter | ||
Updated•11 years ago
|
Assignee: general → sphink
Assignee | ||
Comment 2•11 years ago
|
||
Ben: I know it's a little weird for you to be reviewing a configure flag change for a spidermonkey shell test build, but it's just preserving existing behavior in preparation for a change of defaults.
Attachment #815600 -
Flags: review?(bhearsum)
Comment 3•11 years ago
|
||
Comment on attachment 815600 [details] [diff] [review] Dynamic rooting analysis should disable threadsafe explicitly Review of attachment 815600 [details] [diff] [review]: ----------------------------------------------------------------- In the future, I think it's probably fine for you to get review from someone who understands what these builds need to be and/or what the flags do. But I'm also fine to rubberstamp them.
Attachment #815600 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Equivalent patch landed as part of bug 927204.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → mozilla28
Updated•10 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•