-
Notifications
You must be signed in to change notification settings - Fork 62
Don't loop forever on errors writing installinator slots #9471
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
Open
labbott
wants to merge
1
commit into
main
Choose a base branch
from
installinator_stop_loop
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Hmm, this is a pretty significant behavior change to the real installinator, right? I think the intent was to loop forever if we're not having success, because there's no way to restart this on failure other than aborting the entire mupdate and starting over.
That's pretty terrible for tests, though. I wonder if we should have a cap on the number of attempts (which this code implicitly has, I think, with the cap set to "2"), and allow prod to pass a cap of "loop forever" while tests can pass something much smaller?
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.
yeah we're getting into "timeouts timeouts always wrong" territory here. I don't actually mind looping forever for tests because that is a sign I need to fix something because tests should finish. Looping forever in production actually seems worse though if there's some kind of permanent error we'll just be stuck which seems bad. Maybe wicket will give more information than tests though? If we're actually okay with the current behavior I can also just close this.