node-report flaky on v4

[MylesBorins]

We should figure out why, and if necessary set the flag

[richardlau]

@MylesBorins Do you have an example failure?

nodejs/node-report#58 might be related (landed in node-report master ~14hrs ago).

[MylesBorins]

https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/588/

…

On Tue, Feb 21, 2017 at 8:53 PM, Richard Lau ***@***.***> wrote: @MylesBorins <https://github.com/MylesBorins> Do you have an example failure? nodejs/node-report#58 <nodejs/node-report#58> might be related (landed in node-report master ~14hrs ago). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#356 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecVyHOKEG2thvTtXrAg65p7oKUDDXgks5re5UMgaJpZM4MIFpV> .

[richardlau]

https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/588/

Can confirm the node-report failures are the same ones that will be fixed by nodejs/node-report#58.

Cc. @rnchamberlain

[gdams]

@richardlau is this fixed now?

[richardlau]

Should be fixed in node-report 2.1.1.

[gdams]

Fixed