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

Executor cache count primer (backport #22333) #22374

Merged
merged 1 commit into from Jan 8, 2022
Merged

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 8, 2022

This is an automatic backport of pull request #22333 done by Mergify.
Cherry-pick of 4ce4830 has failed:

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

You are currently cherry-picking commit 4ce48307b.
  (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)

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

no changes added to commit (use "git add" and/or "git commit -a")

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

@mergify mergify bot added conflicts automerge Merge this Pull Request automatically once CI passes labels Jan 8, 2022
@solana-grimes
Copy link
Collaborator

😱 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 Jan 8, 2022
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Jan 8, 2022
@codecov
Copy link

codecov bot commented Jan 8, 2022

Codecov Report

Merging #22374 (f7704d0) into v1.8 (6130466) will increase coverage by 0.0%.
The diff coverage is 98.5%.

@@           Coverage Diff           @@
##             v1.8   #22374   +/-   ##
=======================================
  Coverage    81.5%    81.5%           
=======================================
  Files         459      459           
  Lines      131010   131063   +53     
=======================================
+ Hits       106848   106900   +52     
- Misses      24162    24163    +1     

@mergify mergify bot merged commit 8c6df1f into v1.8 Jan 8, 2022
@mergify mergify bot deleted the mergify/bp/v1.8/pr-22333 branch January 8, 2022 10:14
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2022

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 Apr 1, 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.

None yet

2 participants