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

TestSendCelo fails due to missing signer #1967

Open
piersy opened this issue Oct 7, 2022 · 4 comments
Open

TestSendCelo fails due to missing signer #1967

piersy opened this issue Oct 7, 2022 · 4 comments

Comments

@piersy
Copy link
Contributor

piersy commented Oct 7, 2022

Description

Occurred on master at fb462b6 in this build

=== RUN   TestSendCelo
Checking getExchangeSpenders. spenders = []
Checking medianRate. numerator = 1000000000000000000000000  denominator = 1000000000000000000000000 
Checking gas price minimum. cusdValue = 100000000
    e2e_test.go:54: 
        	Error Trace:	e2e_test.go:54
        	Error:      	Received unexpected error:
        	            	failed to build node for network: signer missing: unknown account
        	Test:       	TestSendCelo
--- FAIL: TestSendCelo (1.82s)

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:

require.NoError(t, err)

@carterqw2 carterqw2 added triage Issue needs triaging and removed blockchain labels Feb 9, 2023
@carterqw2 carterqw2 added good first issue and removed triage Issue needs triaging labels Feb 16, 2023
@karlb
Copy link
Contributor

karlb commented Mar 7, 2023

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?

@piersy
Copy link
Contributor Author

piersy commented Mar 7, 2023

@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 Backend.RefreshValPeers there is a race condition between that and the use of Network.GossipEnodeCertificatge where I think sometimes nodes refresh their validator peers after enode certificates have been gossiped, there's then a 5 minute delay till the announce protocol gossips the enode certificates again. So I think the timeout problem could be solved by making the timeout for this test about 7 minutes. A better solution would be to rework the announce protocol.

@piersy
Copy link
Contributor Author

piersy commented Mar 7, 2023

@karlb I've not seen this ticket's failure ever again, so it could be that some code change has inadvertently solved it.

@karlb
Copy link
Contributor

karlb commented Mar 13, 2023

I was able to reproduce the same error locally (after running the test many times):

--- FAIL: TestSendCelo (0.56s)
    e2e_test.go:42: 
        	Error Trace:	e2e_test.go:42
        	Error:      	Received unexpected error:
        	            	failed to build node for network: signer missing: unknown account
        	Test:       	TestSendCelo

So the issue still exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants