-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
test: fix inconsistency write size in test-fs-readfile-tostring-fail
#51141
Merged
Conversation
This file contains 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
test-fs-readfile-tostring-fail
d90fc7d
to
adecf4d
Compare
test-fs-readfile-tostring-fail
test-fs-readfile-tostring-fail
adecf4d
to
7c5a47c
Compare
test-fs-readfile-tostring-fail
test-fs-readfile-tostring-fail
1499cb9
to
be0fb37
Compare
lpinca
approved these changes
Dec 13, 2023
@@ -9,13 +9,15 @@ const assert = require('assert'); | |||
const fs = require('fs'); | |||
const cp = require('child_process'); | |||
const kStringMaxLength = require('buffer').constants.MAX_STRING_LENGTH; | |||
const size = kStringMaxLength / 200; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
const size = kStringMaxLength / 200; | |
const size = Math.floor(kStringMaxLength / 200); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your review. I fixed it. 😄
Commit Queue failed- Loading data for nodejs/node/pull/51141 ✔ Done loading data for nodejs/node/pull/51141 ----------------------------------- PR info ------------------------------------ Title test: fix inconsistency write size in `test-fs-readfile-tostring-fail` (#51141) Author Jungku Lee (@pluris) Branch pluris:fix/test_fs_readfile -> nodejs:main Labels test, needs-ci Commits 2 - test: fix inconsistency write size in `test-fs-readfile-tostring-fail` - fixup! test: fix inconsistency write size in test-fs-readfile-tostrin… Committers 1 - pluris PR-URL: https://github.com/nodejs/node/pull/51141 Refs: https://github.com/nodejs/node/issues/51133 Reviewed-By: Luigi Pinca ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/51141 Refs: https://github.com/nodejs/node/issues/51133 Reviewed-By: Luigi Pinca -------------------------------------------------------------------------------- ⚠ Commits were pushed since the last approving review: ⚠ - fixup! test: fix inconsistency write size in test-fs-readfile-tostrin… ℹ This PR was created on Wed, 13 Dec 2023 06:03:46 GMT ✔ Approvals: 1 ✔ - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/51141#pullrequestreview-1780419297 ✔ Last GitHub CI successful ℹ Last Full PR CI on 2023-12-14T20:38:30Z: https://ci.nodejs.org/job/node-test-pull-request/56294/ - Querying data for job/node-test-pull-request/56294/ ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/7316742704 |
deokjinkim
approved these changes
Dec 25, 2023
Landed in 26d39e8 |
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.
commit-queue-squash
Add this label to instruct the Commit Queue to squash all the PR commits into the first one.
needs-ci
PRs that need a full CI run.
test
Issues and PRs related to the tests.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this test, more space is being used than the space being checked.
It's actually using more capacity in
stream.write()
than is written tokStringMaxLength
.There are
201
buffers used in the for loop.Even if this code is fixed, I'm not sure if the unstable tests are resolved.
node/test/pummel/test-fs-readfile-tostring-fail.js
Lines 18 to 20 in 1b60054
node/test/pummel/test-fs-readfile-tostring-fail.js
Lines 29 to 36 in 1b60054
Refs: #51133