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

Run upgrade testing from git (bp #1129) #1131

Closed
wants to merge 4 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 25, 2021

This is an automatic backport of pull request #1129 done by Mergify.

Cherry-pick of c6757fe has failed:

On branch mergify/bp/stable/4.3/pr-1129
Your branch is up to date with 'origin/stable/4.3'.

You are currently cherry-picking commit c6757fe1.
  (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:   run-upgrade-tests.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   tox.ini

To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/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.io/

Don't upgrade between released versions but use tags
or branches instead. When dependencies breaks it's
easier to get jobs passing without having to release
instantly.

(cherry picked from commit c6757fe)

# Conflicts:
#	tox.ini
@mergify mergify bot added the conflicts label Mar 25, 2021
@mergify mergify bot mentioned this pull request Mar 25, 2021
Don't upgrade between released versions but use tags
or branches instead. When dependencies breaks it's
easier to get jobs passing without having to release
instantly.

(cherry picked from commit c6757fe)
@tobias-urdin
Copy link
Contributor

@Mergifyio rebase

@mergify
Copy link
Contributor Author

mergify bot commented Mar 29, 2021

Command rebase: failure

Base branch update has failed
Git reported the following error:

First, rewinding head to replay your work on top of it...
Applying: Run upgrade testing from git
Applying: Run upgrade testing from git
Using index info to reconstruct a base tree...
M	run-upgrade-tests.sh
M	tox.ini
Falling back to patching base and 3-way merge...
Auto-merging tox.ini
CONFLICT (content): Merge conflict in tox.ini
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch' to see the failed patch
Patch failed at 0002 Run upgrade testing from git
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".

err-code: 0FF27

@mergify mergify bot deleted the mergify/bp/stable/4.3/pr-1129 branch March 29, 2021 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant