Skip to content
This repository was archived by the owner on Jan 22, 2025. It is now read-only.

adds more sanity checks to shreds (backport #21675)#22869

Merged
mergify[bot] merged 2 commits intov1.8from
mergify/bp/v1.8/pr-21675
Feb 1, 2022
Merged

adds more sanity checks to shreds (backport #21675)#22869
mergify[bot] merged 2 commits intov1.8from
mergify/bp/v1.8/pr-21675

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Feb 1, 2022

This is an automatic backport of pull request #21675 done by Mergify.
Cherry-pick of 8063273 has failed:

On branch mergify/bp/v1.8/pr-21675
Your branch is up to date with 'origin/v1.8'.

You are currently cherry-picking commit 8063273d0.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   core/src/broadcast_stage/standard_broadcast_run.rs
	modified:   core/src/window_service.rs
	modified:   ledger/src/shred.rs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   ledger/src/blockstore.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

(cherry picked from commit 8063273)

# Conflicts:
#	ledger/src/blockstore.rs
@mergify mergify Bot added conflicts automerge Merge this Pull Request automatically once CI passes labels Feb 1, 2022
@solana-grimes
Copy link
Copy Markdown
Contributor

😱 New commits were pushed while the automerge label was present.

@solana-grimes solana-grimes removed the automerge Merge this Pull Request automatically once CI passes label Feb 1, 2022
@mergify mergify Bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Feb 1, 2022
@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Feb 1, 2022

automerge label removed due to a CI failure

@behzadnouri behzadnouri force-pushed the mergify/bp/v1.8/pr-21675 branch from d075979 to 72a0cf6 Compare February 1, 2022 16:20
@mergify mergify Bot added the automerge Merge this Pull Request automatically once CI passes label Feb 1, 2022
@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 1, 2022

Codecov Report

Merging #22869 (72a0cf6) into v1.8 (add26be) will decrease coverage by 0.0%.
The diff coverage is 89.3%.

@@            Coverage Diff            @@
##             v1.8   #22869     +/-   ##
=========================================
- Coverage    81.6%    81.6%   -0.1%     
=========================================
  Files         464      464             
  Lines      131709   131731     +22     
=========================================
+ Hits       107555   107567     +12     
- Misses      24154    24164     +10     

@mergify mergify Bot merged commit 6837d76 into v1.8 Feb 1, 2022
@mergify mergify Bot deleted the mergify/bp/v1.8/pr-21675 branch February 1, 2022 18:16
@github-actions
Copy link
Copy Markdown
Contributor

This PR has been automatically locked since there has not been any activity in past 14 days after it was merged.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

automerge Merge this Pull Request automatically once CI passes conflicts locked PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants