fix: waku bridge test timing #1429
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
In my local tests, I used 5 seconds and the bug was still triggered. So probably the cause is somewhere else, but would be great that this helps in reducing the number of failure occurrences. |
|
@s1fr0 indeed, we'd have to monitor and perhaps disable this test. Note that I also removed one timer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR to partially address #1357.
This fix seems to at least make things better. If we still get intermittent failures, we can consider reworking this test or coming up with a different Future/Result mechanism that will circumvent the need for async sleeps. Let's monitor in conjunction with other CI tests.