Skip to content

test(mempool): enhanced TestReactorNoBroadcastToSender (backport #4127)#4182

Merged
mergify[bot] merged 4 commits intov1.xfrom
mergify/bp/v1.x/pr-4127
Sep 27, 2024
Merged

test(mempool): enhanced TestReactorNoBroadcastToSender (backport #4127)#4182
mergify[bot] merged 4 commits intov1.xfrom
mergify/bp/v1.x/pr-4127

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Sep 26, 2024

The test should be able now to catch the error introduced by #3657.

FOR REVIEWERS: the 91ab7a7 commit was reverted in this backport, since mempool lanes is not implemented in v1.x.

PR checklist

  • Tests written/updated
  • Changelog entry added in .changelog (we use unclog to manage our changelog)
  • Updated relevant documentation (docs/ or spec/) and code comments

This is an automatic backport of pull request #4127 done by [Mergify](https://mergify.com).

The test should be able now to catch the error introduced by
#3657.

----

To see how it would break, please checkout the branch
`cason/test-nobroadcastsender`, then:

```
$ cd mempool
$ go test -v -run TestReactorNoBroadcastToSender
```

And wait it to fail, after 2 minutes. You are going to see the busy-loop
around, logs entries starting with `Skipping tx`, forever for the same
transaction.

Important: the test unit only works in the traditional mempool design,
without lanes. We should consider adding a variant of it that should
also pass when lanes are considered.

---

#### PR checklist

- [x] Tests written/updated
- [ ] 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

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit 9e25845)

# Conflicts:
#	mempool/reactor.go
#	mempool/reactor_test.go
@mergify mergify bot requested a review from a team as a code owner September 26, 2024 11:13
@mergify mergify bot requested a review from a team September 26, 2024 11:13
@mergify mergify bot added the conflicts label Sep 26, 2024
@mergify
Copy link
Contributor Author

mergify bot commented Sep 26, 2024

Cherry-pick of 9e25845 has failed:

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

You are currently cherry-picking commit 9e25845d4.
  (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:   mempool/reactor.go
	both modified:   mempool/reactor_test.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/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify bot assigned cason Sep 26, 2024
@cason cason removed the conflicts label Sep 26, 2024
@cason cason requested a review from hvanz September 26, 2024 15:16
@mergify mergify bot merged commit 130ff23 into v1.x Sep 27, 2024
@mergify mergify bot deleted the mergify/bp/v1.x/pr-4127 branch September 27, 2024 06:23
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.

2 participants