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

fix(e2e): Increase timeout when waiting for new block #2606

Merged
merged 1 commit into from Mar 13, 2024

Conversation

hvanz
Copy link
Member

@hvanz hvanz commented Mar 13, 2024

Some nightly test scenarios are failing because the test that checks that new blocks are being created timeouts. This happens on larger networks with many perturbations, on a few heights. Currently the timeout is 5 seconds, but in some cases it takes the network more than 20 seconds to create a block, so this PR changes it to 30 seconds.


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
  • Title follows the Conventional Commits spec

@hvanz hvanz added e2e Related to our end-to-end tests backport-to-v1.x Tell Mergify to backport the PR to v1.x labels Mar 13, 2024
@hvanz hvanz requested review from a team as code owners March 13, 2024 10:28
Copy link
Contributor

@lasarojc lasarojc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change itself looks good, but will this not cause the testing framework to timeout?

@hvanz
Copy link
Member Author

hvanz commented Mar 13, 2024

Is there a timeout on the whole test that could expire before 30 seconds? If we see that the tests still timeouts after this fix, we can fix it in another PR.

@hvanz hvanz added this pull request to the merge queue Mar 13, 2024
Merged via the queue into main with commit 540231c Mar 13, 2024
21 checks passed
@hvanz hvanz deleted the e2e/increase-block-creation-timeout branch March 13, 2024 14:33
mergify bot pushed a commit that referenced this pull request Mar 13, 2024
Some nightly test scenarios are failing because the test that checks
that new blocks are being created timeouts. This happens on larger
networks with many perturbations, on a few heights. Currently the
timeout is 5 seconds, but in some cases it takes the network more than
20 seconds to create a block, so this PR changes it to 30 seconds.

---

#### PR checklist

- [ ] 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
- [ ] Title follows the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec

(cherry picked from commit 540231c)
@lasarojc
Copy link
Contributor

Cool. The CI relies on test-group action, in the root Makefile. The timeout there is set to 15 minutes
test-group-%:split-test-packages cat $(BUILDDIR)/packages.txt.$* | xargs go test -mod=readonly -timeout=15m -race -coverprofile=$(BUILDDIR)/$*.profile.out

Probably enough

hvanz added a commit that referenced this pull request Mar 13, 2024
#2609)

Some nightly test scenarios are failing because the test that checks
that new blocks are being created timeouts. This happens on larger
networks with many perturbations, on a few heights. Currently the
timeout is 5 seconds, but in some cases it takes the network more than
20 seconds to create a block, so this PR changes it to 30 seconds.

---

#### PR checklist

- [ ] 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
- [ ] Title follows the [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec
<hr>This is an automatic backport of pull request #2606 done by
[Mergify](https://mergify.com).

Co-authored-by: Hernán Vanzetto <15466498+hvanz@users.noreply.github.com>
@adizere adizere added this to the 2024-Q1 milestone Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-v1.x Tell Mergify to backport the PR to v1.x e2e Related to our end-to-end tests
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants