timer: call list.start regardless new or not

[abbr]

Call start regardless whether list is new
or not to prevent incorrect active_handles
count.

Fixes nodejs/node-v0.x-archive#25831.
Ported from pr nodejs/node-v0.x-archive#25832.

[thefourtheye]

use strict should be the first line.

[thefourtheye]

The simple directory under test directory is specific to the old repository. Here you need to put this either in parallel or sequential directory.

[mscdex]

Is it possible to create a test that doesn't have to compile C++ code (while tests are running)? Maybe utilize process._getActiveHandles() to check the active handle count?

[abbr]

@mscdex, the c++ code is used to expose uv_run to js, not for reporting active handles.

[vkurchatkin]

Why do you need uv_run to test incorrect active handles count?

[Fishrock123]

Please move the tests into test/parallel/ :)

[abbr]

Just realized pr should be applied to master branch. I will close this pr and submit a new one.

@mscdex, in my updated test case of the new pr, I found process._getActiveHandles().length is reporting wrong # of count: 3, as opposed to c++ uv_default_loop()->active_handles of 0 which is used in the test case. Possibly another bug.

@vkurchatkin , uv_run is not used to test incorrect handles. It's how the problem occurs. Just nesting two setTimeout calls with same value won't cause the problem.