Pass --nologfile-per-isolate to d8 in plot-timer-events calibration code

Pass --nologfile-per-isolate to d8 in plot-timer-events calibration code

This was broken by the removal of the default isolate.

[adamk, 2014-05-09 21:15:17]

It's not clear to me if this is the right way to fix this, or if d8 --prof
should set --nologfile-per-isolate implicitly. Otherwise any user trying to use
--prof will have to look at a per-isolate file instead of plain old v8.log.

[Sven Panne, 2014-05-12 07:35:54]

On 2014/05/09 21:15:17, adamk wrote:
> It's not clear to me if this is the right way to fix this, or if d8 --prof
> should set --nologfile-per-isolate implicitly. Otherwise any user trying to
use
> --prof will have to look at a per-isolate file instead of plain old v8.log.

I am not totally sure, either: The current default of logfile_per_isolate is the
right thing for a multi-process multi-threaded thing like Chrome, but it's a
little bit uncomfortable for our happy small development world. Perhaps we
should have a small discussion offline...

[Sven Panne, 2014-05-12 07:35:55]

On 2014/05/09 21:15:17, adamk wrote:
> It's not clear to me if this is the right way to fix this, or if d8 --prof
> should set --nologfile-per-isolate implicitly. Otherwise any user trying to
use
> --prof will have to look at a per-isolate file instead of plain old v8.log.

I am not totally sure, either: The current default of logfile_per_isolate is the
right thing for a multi-process multi-threaded thing like Chrome, but it's a
little bit uncomfortable for our happy small development world. Perhaps we
should have a small discussion offline...

[Yang, 2014-05-12 07:37:35]

On 2014/05/12 07:35:55, Sven Panne wrote:
> On 2014/05/09 21:15:17, adamk wrote:
> > It's not clear to me if this is the right way to fix this, or if d8 --prof
> > should set --nologfile-per-isolate implicitly. Otherwise any user trying to
> use
> > --prof will have to look at a per-isolate file instead of plain old v8.log.
> 
> I am not totally sure, either: The current default of logfile_per_isolate is
the
> right thing for a multi-process multi-threaded thing like Chrome, but it's a
> little bit uncomfortable for our happy small development world. Perhaps we
> should have a small discussion offline...

I think as long as d8 has only one isolate, it should assume
--nologfile-per-isolate. I can prepare a CL.

[Yang, 2014-05-12 13:48:27]

On 2014/05/12 07:37:35, Yang wrote:
> On 2014/05/12 07:35:55, Sven Panne wrote:
> > On 2014/05/09 21:15:17, adamk wrote:
> > > It's not clear to me if this is the right way to fix this, or if d8 --prof
> > > should set --nologfile-per-isolate implicitly. Otherwise any user trying
to
> > use
> > > --prof will have to look at a per-isolate file instead of plain old
v8.log.
> > 
> > I am not totally sure, either: The current default of logfile_per_isolate is
> the
> > right thing for a multi-process multi-threaded thing like Chrome, but it's a
> > little bit uncomfortable for our happy small development world. Perhaps we
> > should have a small discussion offline...
> 
> I think as long as d8 has only one isolate, it should assume
> --nologfile-per-isolate. I can prepare a CL.

Fixed in https://codereview.chromium.org/276333002/