-
Notifications
You must be signed in to change notification settings - Fork 202
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
TestSendCelo fails due to missing signer #1967
Comments
The test usually succeeds, but according to CircleCI, it is flaky with the most recent failure 7 days ago. If we can trust CircleCI's flakiness detection, we have a high level of flakiness with 76 tests being considered flaky. Maybe we have underlying issue that is causing many tests to become flaky? |
@karlb That failure you linked to is a timeout, so I think caused by something different to this failure. My suspicion is that the timeouts are caused by the announce protocol. When a node starts validating it chucks all its validator peers see |
@karlb I've not seen this ticket's failure ever again, so it could be that some code change has inadvertently solved it. |
I was able to reproduce the same error locally (after running the test many times):
So the issue still exists. |
Description
Occurred on master at fb462b6 in this build
I've not seen this before, and it doesn't look like a timeout issue since the test was running for only 1.82s
It failed at network start, here:
celo-blockchain/e2e_test/e2e_test.go
Line 54 in fb462b6
The text was updated successfully, but these errors were encountered: