Skip to content

benchmark: fix next-tick-depth - #20461

Closed
apapirovski wants to merge 2 commits into
nodejs:masterfrom
apapirovski:fix-next-tick-depth-benchmark
Closed

benchmark: fix next-tick-depth#20461
apapirovski wants to merge 2 commits into
nodejs:masterfrom
apapirovski:fix-next-tick-depth-benchmark

Conversation

@apapirovski

Copy link
Copy Markdown
Contributor

A recent change made this benchmark fail by always finishing with 0 iterations. Restore a counter variable.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

A recent change made this benchmark fail by always finishing
with 0 iterations. Restore a counter variable.
@apapirovskiapapirovski added the benchmark Issues and PRs related to the benchmark subsystem. label May 2, 2018
@nodejs-github-botnodejs-github-bot added the process Issues and PRs related to the process subsystem. label May 2, 2018
@apapirovskiapapirovski added the fast-track PRs that do not need to wait for 48 hours to land. label May 2, 2018
@apapirovski

Copy link
Copy Markdown
ContributorAuthor

Please 👍 to approve fast-tracking.

@apapirovski

Copy link
Copy Markdown
ContributorAuthor

@BridgeARBridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 2, 2018
@apapirovski

apapirovski commented May 2, 2018

Copy link
Copy Markdown
ContributorAuthor

Missed that next-tick-depth-args had the same issues. Resolved.

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

@apapirovskiapapirovski removed the fast-track PRs that do not need to wait for 48 hours to land. label May 2, 2018
@apapirovski

Copy link
Copy Markdown
ContributorAuthor

@Trott would you be ok with fast-tracking? Looking to get these fixed so I can run these on the CI in #20468

@Trott

Trott commented May 2, 2018

Copy link
Copy Markdown
Member

@Trott would you be ok with fast-tracking?

Yes.

@apapirovskiapapirovski added the fast-track PRs that do not need to wait for 48 hours to land. label May 2, 2018
@apapirovski

Copy link
Copy Markdown
ContributorAuthor

Landed in a957f24

@apapirovski
apapirovski deleted the fix-next-tick-depth-benchmark branch May 3, 2018 05:15
apapirovski added a commit that referenced this pull request May 3, 2018
A recent change made these benchmarks fail by always finishing
with 0 iterations. Restore a counter variable.
PR-URL: #20461
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Rich Trott <rtrott@gmail.com>
MylesBorins pushed a commit that referenced this pull request May 4, 2018
A recent change made these benchmarks fail by always finishing
with 0 iterations. Restore a counter variable.
PR-URL: #20461
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request May 8, 2018
MylesBorins pushed a commit that referenced this pull request May 8, 2018
A recent change made these benchmarks fail by always finishing
with 0 iterations. Restore a counter variable.
PR-URL: #20461
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.benchmarkIssues and PRs related to the benchmark subsystem.fast-trackPRs that do not need to wait for 48 hours to land.processIssues and PRs related to the process subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@apapirovski@Trott@BridgeAR@nodejs-github-bot