-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
add vsock connection tests #846
base: main
Are you sure you want to change the base?
Conversation
We already have an automatically created pr for nix update and cargo.lock isn't really something that affects users. Please don't touch it directly. Bots take care of it. |
@zeenix any idea why tokio-vsock doesn't receive BEGIN.. or how to debug that.. I am bit stuck. (cargo test --features tokio-vsock,p2p connection::p2p_tests::vsock_connect) |
Seems to be only an issue for |
@elmarco do you see this PR going forward? |
This is backward since commit cf35fbd and triggers extra compilation warning (target_family vs target_os). Let's drop it.
Use local CID, and bind to any port. If vsock is enabled, assume the host is capable to run the tests.
The test fails with tokio-vsock, which doesn't seem to send or flush the BEGIN command. More investigation needed.