-
Notifications
You must be signed in to change notification settings - Fork 234
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
Flaky e2e-p2p test #3654
Comments
benesjan
added a commit
that referenced
this issue
Jan 4, 2024
Fixes #3654 **Note**: Lasse had a good hunch that it's most likely caused by different nodes using the same l1 publisher private key. This PR changes this and uses different accounts for different nodes. I am quite confident that that is the culprit so I will close the issue.
Maddiaa0
pushed a commit
that referenced
this issue
Jan 8, 2024
Fixes #3654 **Note**: Lasse had a good hunch that it's most likely caused by different nodes using the same l1 publisher private key. This PR changes this and uses different accounts for different nodes. I am quite confident that that is the culprit so I will close the issue.
michaelelliot
pushed a commit
to Swoir/noir_rs
that referenced
this issue
Feb 28, 2024
Fixes AztecProtocol#3654 **Note**: Lasse had a good hunch that it's most likely caused by different nodes using the same l1 publisher private key. This PR changes this and uses different accounts for different nodes. I am quite confident that that is the culprit so I will close the issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Plenty of the times the test randomly fails with:
This should be fixed.
E.g.:
https://app.circleci.com/pipelines/github/AztecProtocol/aztec-packages/18626/workflows/583cce6d-44c4-494a-9667-57b26a93d169/jobs/828692
https://app.circleci.com/pipelines/github/AztecProtocol/aztec-packages/19715/workflows/86a890a8-e0c9-4b1f-9779-6b656577e116/jobs/885167/parallel-runs/0/steps/0-103
The text was updated successfully, but these errors were encountered: