Thanks for the explanation. IIRC content process is closed by SIGKILL in
Gecko. Looks like we'll have to tweak the timing.
Best Regards,
Shih-Chiang Chien
Mozilla Taiwan
On Wed, May 27, 2015 at 10:10 AM, Joshua Cranmer pidgeo...@gmail.com
wrote:
On 5/26/2015 8:54 PM, Shih-Chiang Chien wrote:
On 5/26/2015 10:20 PM, Shih-Chiang Chien wrote:
Thanks for the explanation. IIRC content process is closed by SIGKILL in
Gecko. Looks like we'll have to tweak the timing.
A SIGKILL would definitely not trigger the information to be dumped.
--
Joshua Cranmer
Thunderbird and DXR developer
Does this coverage info also include gtests? From a quick glance it looks like
not.
On Tuesday, May 26, 2015 at 2:59:16 PM UTC-4, Joshua Cranmer wrote:
I've posted updated code coverage information for mozilla-central to
https://www.tjhsst.edu/~jcranmer/m-ccov/. This data is accurate as of
I've posted updated code coverage information for mozilla-central to
https://www.tjhsst.edu/~jcranmer/m-ccov/. This data is accurate as of
yesterday. For those of you who are unaware, I periodically run these
code coverage statistics by use of the try server and instrumented runs.
This has
On 5/26/2015 3:21 PM, kgu...@mozilla.com wrote:
Does this coverage info also include gtests? From a quick glance it looks like
not.
The code coverage includes all tests run on Linux opt or Linux-64 opt
excluding those run under check, marionette, web-platform tests, or
luciddream. If gtests
On Tue, May 26, 2015 at 03:48:06PM -0500, Joshua Cranmer ? wrote:
On 5/26/2015 3:21 PM, kgu...@mozilla.com wrote:
Does this coverage info also include gtests? From a quick glance it looks
like not.
The code coverage includes all tests run on Linux opt or Linux-64 opt
excluding those run
6 matches
Mail list logo
