Coverage remained the same at 97.739% when pulling 31eb1cb7a56c0cc394271d6a843b50e1ada5aa06 on killmenot:examples into 257d87cb0961c02b11f1bb12dc06ae1026228f6f on robtweed:master.
Coverage remained the same at 97.739% when pulling 31eb1cb7a56c0cc394271d6a843b50e1ada5aa06 on killmenot:examples into 257d87cb0961c02b11f1bb12dc06ae1026228f6f on robtweed:master.
Coverage remained the same at 97.739% when pulling 31eb1cb7a56c0cc394271d6a843b50e1ada5aa06 on killmenot:examples into 257d87cb0961c02b11f1bb12dc06ae1026228f6f on robtweed:master.
Hi @robtweed,
start
event is emitted before checkWorkerPool logic is initiated (to be able to configure checkWorkerPoolDelay)benchmarks
folder and tested ($ node benchmarks/benchmark.js
)