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

Dig into potential issue with tokio start_paused #66

Open
sunshowers opened this issue Mar 23, 2023 · 0 comments
Open

Dig into potential issue with tokio start_paused #66

sunshowers opened this issue Mar 23, 2023 · 0 comments
Milestone

Comments

@sunshowers
Copy link
Contributor

In oxidecomputer/omicron#2654 we found that a test with tokio::test(start_paused = true) that consistently worked on Linux was flaky on illumos.

Note that start_paused = true runs tokio in a mode where timers are paused, and auto-advance. Since all this code uses Tokio, pausing and auto-advancing timers should work in theory -- there's no reason for any of these operations to be tied to system timers.

This could be any of the following:

  • an omicron code difference between Linux and illumos (though the test doesn't use any illumos-specific features and is completely OS-independent -- it uses MGS talking to sp-sim).
  • a scheduler difference on illumos compared to Linux
  • a Tokio difference between illumos on Linux
  • a bug in Tokio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants