-
Notifications
You must be signed in to change notification settings - Fork 587
HDDS-12288. Improve bootstrap logging to indicate progress #7861
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
bfef929
HDDS-12288. Improved the bootsrap logging to indcate the progress
4a810a5
HDDS-12288. Improved the bootsrap logging to indcate the progress
1dd90ac
HDDS-12288. Improved the bootsrap logging to indcate the progress
cf05f89
HDDS-12288. Improved the bootsrap logging to indcate the progress
9aa8c33
HDDS-12288. Improved the bootsrap logging to indcate the progress
2d8fe42
HDDS-12288. Improved the bootsrap logging to indcate the progress
d3576d4
HDDS-12288. Improved the bootsrap logging to indcate the progress
dd03f4f
HDDS-12288. Improve bootstrap logging to indicate progress
Gargi-jais11 e5f7a59
HDDS-12288. Improve bootstrap logging to indicate progress
Gargi-jais11 3cb99a2
HDDS-12288. Improve bootstrap logging to indicate progress
Gargi-jais11 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.
Please don't merge with outdated CI results. Last run, although triggered on Feb 21, was against code from Feb 13, because that's when the last commit was pushed to the PR:
https://github.com/apache/ozone/actions/runs/13305097960/job/37592785787#step:2:90
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.
Sure , will keep this in mind.
After how many days/commits b/w PR branch & master should one rebase and re-run? Ideally it should be after every new commit in master as any new commit can cause the CI to fail but do we actually follow this i.e re-running CI even if no conflicts reported in the PR
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.
I guess it depends on the kind of changes done on
masterin the meantime. With new checkstyle rules it can get broken in one commit. Sorry I didn't notice that this PR would fail despite having no conflicts.If in doubt, check out the PR locally, merge
masterinto it, then run some quick sanity checks: