★ wanayoo — archive 1999 https://github.com/nodejs/node/pull/30785Nouvelle recherche | Portail wanayoo
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

fs: add synchronous retries to rimraf #30785

Closed
wants to merge 3 commits into from
Closed

Conversation

@cjihrig
Copy link
Contributor

cjihrig commented Dec 4, 2019

This PR builds on #30784 and #30783.

The third commit in this PR gives the synchronous version of rimraf the same linear retry logic as the asynchronous version. Prior to this commit, sync rimraf kept retrying the operation as soon as possible until maxRetries was reached.

Fixes: #30580
Refs: #30569

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
@cjihrig cjihrig mentioned this pull request Dec 4, 2019
4 of 4 tasks complete
@Trott
Trott approved these changes Dec 4, 2019
@addaleax addaleax added the blocked label Dec 4, 2019
@cjihrig cjihrig force-pushed the cjihrig:sync-retry branch Dec 7, 2019
@cjihrig cjihrig removed the blocked label Dec 7, 2019
@nodejs-github-bot

This comment was marked as outdated.

Copy link

nodejs-github-bot commented Dec 7, 2019

@Trott Trott added the author ready label Dec 7, 2019
@Trott Trott mentioned this pull request Dec 7, 2019
2 of 2 tasks complete
lib/internal/fs/rimraf.js Outdated Show resolved Hide resolved
cjihrig added 2 commits Dec 4, 2019
This commit gives the synchronous version of rimraf the same
linear retry logic as the asynchronous version. Prior to this
commit, sync rimraf kept retrying the operation as soon as
possible until maxRetries was reached.
@cjihrig cjihrig force-pushed the cjihrig:sync-retry branch to 8c2ca28 Dec 8, 2019
@nodejs-github-bot

This comment was marked as outdated.

rimraf should only retry if certain errors are encountered.
Additionally, there is no point sleeping if an error occurs
on the last try.
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment has been minimized.

@cjihrig

This comment has been minimized.

Copy link
Contributor Author

cjihrig commented Dec 8, 2019

@Trott I don't think the CI is going to succeed until the out of space error in the git-nodesource-update-reference job is addressed.

@Trott

This comment has been minimized.

Copy link
Member

Trott commented Dec 8, 2019

@Trott I don't think the CI is going to succeed until the out of space error in the git-nodesource-update-reference job is addressed.

Don't confuse me with logic or data. You can't stop me from indiscriminately pressing "Resume Build" over and over.

@cjihrig

This comment has been minimized.

Copy link
Contributor Author

cjihrig commented Dec 8, 2019

OK, maybe I was wrong. The latest CI run failed on ARM, but only because of the git-nodesource-update-reference job. Does that mean this can land or what?

@nodejs-github-bot

This comment has been minimized.

Copy link

nodejs-github-bot commented Dec 9, 2019

danbev added a commit that referenced this pull request Dec 9, 2019
This commit gives the synchronous version of rimraf the same
linear retry logic as the asynchronous version. Prior to this
commit, sync rimraf kept retrying the operation as soon as
possible until maxRetries was reached.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
danbev added a commit that referenced this pull request Dec 9, 2019
rimraf should only retry if certain errors are encountered.
Additionally, there is no point sleeping if an error occurs
on the last try.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
@danbev

This comment has been minimized.

Copy link
Member

danbev commented Dec 9, 2019

Landed in 26991d0, and d7b8ae7.

@danbev danbev closed this Dec 9, 2019
targos added a commit that referenced this pull request Dec 9, 2019
This commit gives the synchronous version of rimraf the same
linear retry logic as the asynchronous version. Prior to this
commit, sync rimraf kept retrying the operation as soon as
possible until maxRetries was reached.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
targos added a commit that referenced this pull request Dec 9, 2019
rimraf should only retry if certain errors are encountered.
Additionally, there is no point sleeping if an error occurs
on the last try.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
@cjihrig cjihrig deleted the cjihrig:sync-retry branch Dec 9, 2019
@MylesBorins MylesBorins mentioned this pull request Dec 13, 2019
targos added a commit that referenced this pull request Jan 14, 2020
This commit gives the synchronous version of rimraf the same
linear retry logic as the asynchronous version. Prior to this
commit, sync rimraf kept retrying the operation as soon as
possible until maxRetries was reached.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
targos added a commit that referenced this pull request Jan 14, 2020
rimraf should only retry if certain errors are encountered.
Additionally, there is no point sleeping if an error occurs
on the last try.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
BethGriggs added a commit that referenced this pull request Feb 6, 2020
This commit gives the synchronous version of rimraf the same
linear retry logic as the asynchronous version. Prior to this
commit, sync rimraf kept retrying the operation as soon as
possible until maxRetries was reached.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
BethGriggs added a commit that referenced this pull request Feb 6, 2020
rimraf should only retry if certain errors are encountered.
Additionally, there is no point sleeping if an error occurs
on the last try.

PR-URL: #30785
Fixes: #30580
Refs: #30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
@MylesBorins MylesBorins mentioned this pull request Feb 8, 2020
saitonakamura pushed a commit to saitonakamura/node that referenced this pull request Apr 7, 2020
This commit gives the synchronous version of rimraf the same
linear retry logic as the asynchronous version. Prior to this
commit, sync rimraf kept retrying the operation as soon as
possible until maxRetries was reached.

PR-URL: nodejs#30785
Fixes: nodejs#30580
Refs: nodejs#30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
saitonakamura pushed a commit to saitonakamura/node that referenced this pull request Apr 7, 2020
rimraf should only retry if certain errors are encountered.
Additionally, there is no point sleeping if an error occurs
on the last try.

PR-URL: nodejs#30785
Fixes: nodejs#30580
Refs: nodejs#30569
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

7 participants
You can’t perform that action at this time.