test: remove 1 second delay from test

[Trott]

Remove unnecessary 1-second delay from test. Confirmed that test (with changes to eliminate ES6-isms in common.js) still fails in v1.8.1 (which has the bug this test was written for) and passes in v2.3.4 (which contains the fix).

R=@sam-github

[Trott]

CI: https://ci.nodejs.org/job/node-test-pull-request/1188/

[Trott]

Booooo! Blowing up on SmartOS. Still think this is workable. Will revise. Closing for now. Might re-open.

[Trott]

OK, pushed a modification, and this is looking much better. https://ci.nodejs.org/job/node-test-commit/1684/

[Trott]

As a side note, this test is flaky, at least on FreeBSD.

• Failure in CI run: https://ci.nodejs.org/job/node-test-commit-freebsd/826/nodes=freebsd102-64/console
• Failure in stress test: https://ci.nodejs.org/job/node-stress-single-test/325/nodes=freebsd102-64/console

(One of the motivations for this is that one additional second per test run starts to add up when you're doing 10K test runs.)

I have a subsequent modification to tack on to this one that will hopefully fix the flakiness. Stress test currently running at https://ci.nodejs.org/job/node-stress-single-test/333/nodes=freebsd102-64/console. Assuming it works out, I can lump it in with this PR or keep it as a separate PR. Doesn't really matter either way to me.

[Trott]

Stress test for the additional change is looking great. Going to cherry-pick it into this PR...

[Trott]

Cherry-picked. New CI: https://ci.nodejs.org/job/node-test-pull-request/1190/

[Trott]

R=@jbergstroem (This is one of the tests that failed in one of the CI runs for the make-it-all-parallel PR you have open.)

[jbergstroem]

Cool. Looks green indeed. Lets wait for the last arm bot to finish (just got it back online) - but LGTM.

[jasnell]

LGTM if CI is green

[Trott]

Hmmm...the stress test failed, albeit with a bit less frequency than the previous version of the test. So, it's better, but it's still not there yet. More work to be done, alas.

[Trott]

OK, revised to get rid of flakiness (again).

• Stress test: https://ci.nodejs.org/job/node-stress-single-test/339/nodes=freebsd102-64/console

  Looking good so far...

• CI: https://ci.nodejs.org/job/node-test-commit/1712/

  Windows failures appear unrelated and have been happening in the last few CIs. Not sure if a regression has slipped in or if there is a problem with the build infra. /cc @nodejs/build

• Confirmed that (with ES6-isms replaced) it still fails as expected in Node.js v1.8.1 and passes in Node.js v2.3.4.

  \o/

[jbergstroem]

Afaik there are no known infra issues. That's too many fails to just have one bot act up as well.

[Trott]

@jbergstroem Yup. Looks like it's a result of #4575. Looks like it got merged even though there were test failures. At least, that's what I'm seeing. Maybe I'm missing something. (I've certainly been known to be wrong on my what-went-wrong diagnosis in these situations.)

[Trott]

Stress test came out green. Since I made some changes, can I get a reaffirmation of the LGTMs? @jasnell@jbergstroem

(Yes, I'll make sure to squash the four commits down to one before landing.)

[jbergstroem]

LGTM

[jasnell]

Still LGTM

[Trott]

Landed in e98bcfa