Skip to content

feat(e2e): Log number of sent txs (success and failed) (backport #2328)#2332

Merged
hvanz merged 1 commit intov1.xfrom
mergify/bp/v1.x/pr-2328
Feb 14, 2024
Merged

feat(e2e): Log number of sent txs (success and failed) (backport #2328)#2332
hvanz merged 1 commit intov1.xfrom
mergify/bp/v1.x/pr-2328

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Feb 14, 2024

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


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

When we run e2e's `load` command there is no message telling if the txs
were sent or not, and if not, for what reason (eg. mempool is full, txs
is too large, wrong endpoint, etc.). This PR will log a message every ~1
second with the number of successfully sent and failed transactions.

---

#### PR checklist

- [ ] Tests written/updated
- [x] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [ ] Updated relevant documentation (`docs/` or `spec/`) and code
comments
- [x] Title follows the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec

(cherry picked from commit 01a3ad4)
@mergify mergify bot requested a review from a team as a code owner February 14, 2024 08:24
@mergify mergify bot requested a review from a team February 14, 2024 08:24
@hvanz hvanz merged commit 32162de into v1.x Feb 14, 2024
@hvanz hvanz deleted the mergify/bp/v1.x/pr-2328 branch February 14, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant