Rich Trott d10c59fc60 benchmark,test: remove output from readable-async-iterator benchmark ...

Extra output makes test-benchmark-streams fail. Change console.log() to
console.assert().

Fixes: https://github.com/nodejs/node/issues/34409

PR-URL: https://github.com/nodejs/node/pull/34411
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>

2020-07-17 08:41:15 -07:00

..

creation.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

pipe-object-mode.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

pipe.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

readable-async-iterator.js

benchmark,test: remove output from readable-async-iterator benchmark

2020-07-17 08:41:15 -07:00

readable-bigread.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

readable-bigunevenread.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

readable-boundaryread.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

readable-readall.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

readable-unevenread.js

benchmark: use let instead of var

2020-02-13 21:41:33 +01:00

writable-manywrites.js

stream: avoid drain for sync streams

2020-04-25 18:45:50 +02:00