Closed
Bug 274136
Opened 21 years ago
Closed 7 years ago
add method to set xpcshell's exit code
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: shaver, Unassigned)
Details
Attachments
(1 file)
|
1.02 KB,
patch
|
dmosedale
:
review+
|
Details | Diff | Splinter Review |
This will make it easier to write test scripts that run in an automated way.
Patch in a trice.
| Reporter | ||
Comment 1•21 years ago
|
||
What could be simpler?
Comment 2•21 years ago
|
||
Comment on attachment 168458 [details] [diff] [review]
setExitCode(n) sets gExitCode to n (if omitted, 0)
r=dmose
Attachment #168458 -
Flags: review+
Comment 3•21 years ago
|
||
I thought Quit took a parameter that was to be the return value of XPCShell?
this breaks the windows build, see creature (and my depend build ;-))
I backed out, I tried to contact shaver via IRC, bugzilla, and email. This patch
burns the firefox tb for 2h with no sign of a fix.
| Reporter | ||
Comment 6•21 years ago
|
||
Pretending for a moment that the patch didn't break the tree, yes, I suppose
Quit does. We were looking for a way to set the exit code as well as return it
from an inner test function, so that tests run interactively wouldn't exit the
shell, but when run non-interactively would set the exit code appropriately.
Clearly, I was going too fast here on several counts. Apologies!
Updated•21 years ago
|
OS: Linux → All
Hardware: PC → All
Updated•19 years ago
|
QA Contact: pschwartau → xpconnect
Comment 8•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•