Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

benchmark: fix next-tick-depth #20461

Closed

Conversation

apapirovski
Copy link
Member

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.
@apapirovski apapirovski added the benchmark Issues and PRs related to the benchmark subsystem. label May 2, 2018
@nodejs-github-bot nodejs-github-bot added the process Issues and PRs related to the process subsystem. label May 2, 2018
@apapirovski apapirovski added the fast-track PRs that do not need to wait for 48 hours to land. label May 2, 2018
@apapirovski
Copy link
Member Author

Please 👍 to approve fast-tracking.

@apapirovski
Copy link
Member Author

@BridgeAR BridgeAR 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
Copy link
Member Author

apapirovski commented May 2, 2018

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

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

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

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

@Trott
Copy link
Member

Trott commented May 2, 2018

@Trott would you be ok with fast-tracking?

Yes.

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

Landed in a957f24

@apapirovski apapirovski closed this May 3, 2018
@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>
@MylesBorins MylesBorins 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 free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. benchmark Issues and PRs related to the benchmark subsystem. fast-track PRs that do not need to wait for 48 hours to land. process Issues and PRs related to the process subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants