-
Notifications
You must be signed in to change notification settings - Fork 0
Phase19e loopback integration test #101
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
base: feature/phase19c_embassy_net_socket_io
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -48,12 +48,21 @@ embassy-sync = "0.6" | |||||||
| heapless = "0.9" | ||||||||
|
|
||||||||
| [dev-dependencies] | ||||||||
| # Host-side tests use a tuntap-backed embassy-net stack to drive a | ||||||||
| # request/response roundtrip. The dev-dep is what gets us link-time | ||||||||
| # `critical-section` impls on the host. | ||||||||
| # Host-side tests run two embassy-net stacks bridged by a software | ||||||||
| # `LoopbackDriver` pair (no kernel TUN, no privilege requirement). | ||||||||
| # `critical-section/std` provides a host platform impl so embassy-sync | ||||||||
| # / embassy-net link on host; firmware supplies its own. | ||||||||
| critical-section = { version = "1", features = ["std"] } | ||||||||
| embassy-executor = { version = "0.6", features = [ | ||||||||
| "arch-std", | ||||||||
| "executor-thread", | ||||||||
| ] } | ||||||||
| embassy-time = { version = "0.3", features = ["std", "generic-queue-8"] } | ||||||||
| # Tokio drives the test harness — `#[tokio::test]` for setup, | ||||||||
| # `tokio::spawn` for the per-stack `Stack::run()` futures, and | ||||||||
| # `tokio::time::timeout` for bounded assertions. Same shape as the | ||||||||
| # parent crate's `tests/bare_metal_e2e.rs` harness. | ||||||||
| tokio = { version = "1", features = ["rt-multi-thread", "macros", "time", "sync"] } | ||||||||
| # `futures` brings `select_biased!` / `FusedFuture` / `pin_mut!` into | ||||||||
| # scope for the test driver. | ||||||||
| futures = "0.3" | ||||||||
|
Comment on lines
+66
to
+68
|
||||||||
| # `futures` brings `select_biased!` / `FusedFuture` / `pin_mut!` into | |
| # scope for the test driver. | |
| futures = "0.3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These comments say the harness uses
tokio::spawnfor the per-stackStack::run()tasks, but the test usestokio::task::spawn_local(required byLocalSet/current_thread). Updating the comment will avoid confusion about whyrt-multi-threadisn’t actually needed for the test.