Skip to content

e2e: create client when sending transaction (backport #9814)#9816

Merged
williambanfield merged 3 commits intov0.34.xfrom
mergify/bp/v0.34.x/pr-9814
Dec 1, 2022
Merged

e2e: create client when sending transaction (backport #9814)#9816
williambanfield merged 3 commits intov0.34.xfrom
mergify/bp/v0.34.x/pr-9814

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Dec 1, 2022

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

On branch mergify/bp/v0.34.x/pr-9814
Your branch is up to date with 'origin/v0.34.x'.

You are currently cherry-picking commit d09f4f503.
  (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:   test/e2e/runner/load.go

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

Fixes the issue observed in an [e2e test run](https://github.com/tendermint/tendermint/actions/runs/3588927225). The issue arises when the e2e runner process cannot connect to the remote node. In the previous version of this code, the runner would simply skip the transaction if the client couldn't connect. This pull request resurrects that behavior.

---

#### PR checklist

- [ ] Tests written/updated, or no tests needed
- [ ] `CHANGELOG_PENDING.md` updated, or no changelog entry needed
- [ ] Updated relevant documentation (`docs/`) and code comments, or no
      documentation updates needed

(cherry picked from commit d09f4f5)

# Conflicts:
#	test/e2e/runner/load.go
@mergify mergify bot requested a review from ebuchman as a code owner December 1, 2022 16:21
@mergify mergify bot requested a review from a team December 1, 2022 16:21
@mergify mergify bot requested review from adizere and lasarojc as code owners December 1, 2022 16:21
@mergify mergify bot added the conflicts label Dec 1, 2022
@williambanfield williambanfield merged commit dadbf7d into v0.34.x Dec 1, 2022
@williambanfield williambanfield deleted the mergify/bp/v0.34.x/pr-9814 branch December 1, 2022 20:25
@moul moul mentioned this pull request Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant