test: reduce benchmark runs in tests by Trott · Pull Request #21032 · nodejs/node
added 2 commits
May 30, 2018 08:39
nodejs-github-bot
added
benchmark
labels
May 30, 2018
Trott
added
author ready
labels
May 30, 2018
Trott
mentioned this pull request
2 tasks
Trott added a commit to Trott/io.js that referenced this pull request
Jun 2, 2018Add option to test-benchmark-timers such that all benchmark files return only a single set of results. (This helps prevent benchmark tests from taking a long time to run.) Alphabetize options in the file. PR-URL: nodejs#21032 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Trott added a commit to Trott/io.js that referenced this pull request
Jun 2, 2018Prevent crypto benchmark files from running more than one benchmark during tests. PR-URL: nodejs#21032 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
MylesBorins pushed a commit that referenced this pull request
Jun 6, 2018Add option to test-benchmark-timers such that all benchmark files return only a single set of results. (This helps prevent benchmark tests from taking a long time to run.) Alphabetize options in the file. PR-URL: #21032 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
MylesBorins pushed a commit that referenced this pull request
Jun 6, 2018Prevent crypto benchmark files from running more than one benchmark during tests. PR-URL: #21032 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Trott
deleted the
keflavik-5
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters