Closed
Bug 529137
Opened 16 years ago
Closed 16 years ago
Update Talos to cleanup child processes
Categories
(Testing :: General, defect)
Testing
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgriffin, Assigned: anodelman)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
12.75 KB,
patch
|
anodelman
:
review+
|
Details | Diff | Splinter Review |
Currently, Talos cleans up browser-related process before and after a test. For e10s, this code needs to be updated to allow it to cleanup any orphaned child processes as well.
![]() |
Reporter | |
Comment 1•16 years ago
|
||
This patch causes Talos process management routines to be aware of the e10s child process ("mozilla-runtime") when cleaning up processes, and checking if any processes are running. It defaults to "mozilla-runtime" but can be overridden by adding a "child_process" setting to a .config file.
This patch does not update some dead code, e.g., RunProcessAndWaitForOutput() in ffprocess.py.
![]() |
Assignee | |
Comment 2•16 years ago
|
||
What platforms has this been tested on?
![]() |
Reporter | |
Comment 3•16 years ago
|
||
I've tested this on Windows 7 and Ubuntu 9.04; do you need it tested on other platforms?
![]() |
Assignee | |
Comment 4•16 years ago
|
||
We also run on mac 10.4/10.5 and windowsxp/vista. I think that you probably have windows pretty decently covered, but a mac run would increase confidence.
![]() |
Reporter | |
Comment 5•16 years ago
|
||
Electrolysis is currently not supported on the Mac, but I will test it on the Mac to make sure I haven't broken anything there.
![]() |
Reporter | |
Comment 6•16 years ago
|
||
I tested this on 10.6, which is the only mac OS I have easy access to, and it worked fine.
![]() |
Assignee | |
Updated•16 years ago
|
Attachment #412733 -
Flags: review?(anodelman) → review+
Comment 7•16 years ago
|
||
ping? I want to turn on OOPP by default on the electrolysis tree this week, but I don't want to kill the Talos slave pool.
Comment 8•16 years ago
|
||
(In reply to comment #7)
> ping? I want to turn on OOPP by default on the electrolysis tree this week, but
> I don't want to kill the Talos slave pool.
bsmedberg: 1) what testing is needed to verify that OOPP-on-by-default is Talos-safe ? and 2) who's doing that?
Comment 9•16 years ago
|
||
jgriffin wrote the patch and tested it, as the many comments above attest, I think.
![]() |
Assignee | |
Comment 10•16 years ago
|
||
Comment on attachment 412733 [details] [diff] [review]
[checked in]patch
Checking in bcontroller.py;
/cvsroot/mozilla/testing/performance/talos/bcontroller.py,v <-- bcontroller.py
new revision: 1.7; previous revision: 1.6
done
Checking in ffprocess.py;
/cvsroot/mozilla/testing/performance/talos/ffprocess.py,v <-- ffprocess.py
new revision: 1.15; previous revision: 1.14
done
Checking in run_tests.py;
/cvsroot/mozilla/testing/performance/talos/run_tests.py,v <-- run_tests.py
new revision: 1.57; previous revision: 1.56
done
Checking in ttest.py;
/cvsroot/mozilla/testing/performance/talos/ttest.py,v <-- ttest.py
new revision: 1.39; previous revision: 1.38
done
Attachment #412733 -
Attachment description: patch → [checked in]patch
Comment 11•16 years ago
|
||
Back to alice for downtime/deployment, right? Can we get this done soon?
Assignee: jgriffin → anodelman
![]() |
Assignee | |
Comment 12•16 years ago
|
||
Completed by comment #10, I didn't close the bug when it landed as it wasn't assigned to me.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 13•16 years ago
|
||
Hey thanks! I didn't realize that landing into CVS was the same as deployment.
Updated•8 years ago
|
Component: New Frameworks → General
You need to log in
before you can comment on or make changes to this bug.
Description
•