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

uses sendmmsg in streamer (backport #23062) #23080

Merged
merged 2 commits into from
Feb 11, 2022
Merged

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 11, 2022

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

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

You are currently cherry-picking commit c078ca3fb.
  (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:   streamer/src/streamer.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 and removed automerge Merge this Pull Request automatically once CI passes labels Feb 11, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Feb 11, 2022

automerge label removed due to a CI failure

@behzadnouri behzadnouri force-pushed the mergify/bp/v1.9/pr-23062 branch from da8cbe5 to 0ab926a Compare February 11, 2022 13:49
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Feb 11, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Feb 11, 2022

automerge label removed due to a CI failure

@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 11, 2022
@mergify mergify bot merged commit 781609b into v1.9 Feb 11, 2022
@codecov
Copy link

codecov bot commented Feb 11, 2022

Codecov Report

Merging #23080 (0ab926a) into v1.9 (d05b5b0) will decrease coverage by 0.0%.
The diff coverage is 76.6%.

@@            Coverage Diff            @@
##             v1.9   #23080     +/-   ##
=========================================
- Coverage    81.1%    81.1%   -0.1%     
=========================================
  Files         531      531             
  Lines      147988   148044     +56     
=========================================
+ Hits       120155   120160      +5     
- Misses      27833    27884     +51     

@mergify mergify bot deleted the mergify/bp/v1.9/pr-23062 branch February 11, 2022 15:47
@github-actions
Copy link
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.

1 participant