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

test: restore unstable network tests #5197

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

0x009922
Copy link
Contributor

Context

Close #5153

Solution

Implement a TCP relay as described in #5164 (comment). This allows to suspend packages being sent to and from specific peers.

Checklist

  • I've read CONTRIBUTING.md.
  • (optional) I've written unit tests for the code changes.
  • All review comments have been resolved.
  • All CI checks pass.

@0x009922 0x009922 added the Tests label Oct 29, 2024
@0x009922 0x009922 self-assigned this Oct 29, 2024
@0x009922 0x009922 marked this pull request as draft October 29, 2024 08:12
@0x009922 0x009922 changed the title test: restory unstable network peers test: restore unstable network peers Oct 29, 2024
@0x009922 0x009922 changed the title test: restore unstable network peers test: restore unstable network tests Oct 29, 2024
@0x009922 0x009922 force-pushed the restore-faulty-peers-tests branch from d627cf7 to 1c5fe2b Compare November 5, 2024 07:03
@0x009922
Copy link
Contributor Author

0x009922 commented Nov 5, 2024

Relay somewhat works, but weird network behaviour continues happening. Specifically:

  • "Suspended" peers still find way to broadcast transactions?
  • Network synchronizes for a long time for no clear reason
  • Flaky. Sync sometimes doesn't happen. Not sure if something is wrong with the relay or with Iroha itself

@mversic
Copy link
Contributor

mversic commented Nov 5, 2024

Relay somewhat works, but weird network behaviour continues happening. Specifically:

  • "Suspended" peers still find way to broadcast transactions?
  • Network synchronizes for a long time for no clear reason
  • Flaky. Sync sometimes doesn't happen. Not sure if something is wrong with the relay or with Iroha itself

I think it's good enough to merge. Then we'll have to backtrack and compare to last known working iroha build

@0x009922
Copy link
Contributor Author

0x009922 commented Nov 5, 2024

I think it's good enough to merge. Then we'll have to backtrack and compare to last known working iroha build

I have some doubts that there might be something wrong with the relay.

Anyway, let me rehearse the code and I will undraft it.

Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about renaming "faulty peers" to "fault tolerance", which sounds to me like a clearer expression of what this test should guarantee

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sounds good to me.

@0x009922
Copy link
Contributor Author

Status of this PR

The introduced tests are flaky, and something not clear is going on with the tested networks. It requires a deeper investigation.

I am personally now focusing on updating hyperledger-iroha/iroha-javascript, and postponed work on this PR until better times.

The relay is probably working correctly. However, I wouldn't merge this PR as it is now, as it will make CI flaky. Maybe it would make sense to merge this PR with the flaky tests being ignored, but I don't see a good reason to make this semi-step.

@SamHSmith SamHSmith self-assigned this Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Re-implement integration tests with faulty peers
4 participants