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

abort a sequential merge after the first error or incomplete response #219

Merged
merged 1 commit into from Mar 15, 2019

Conversation

kpacha
Copy link
Member

@kpacha kpacha commented Mar 15, 2019

this PR fixes #218

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 97.055% when pulling 72fc268 on err_backend_sequential into f492762 on master.

@kpacha kpacha merged commit 54d192e into master Mar 15, 2019
@kpacha kpacha deleted the err_backend_sequential branch March 15, 2019 20:09
@github-actions
Copy link

github-actions bot commented Apr 7, 2022

This pull request was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Errored backends don't stop a sequential merge
2 participants