oxidecomputer / oxidecomputer/netadm-sys
tests can fail in ways that leave lingering simnet interfaces
Open
Nobody has claimed this yet.
bug
test
- Dominant language
- Rust
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
running 1 test
test test_v6_local_lifecycle ... FAILED
failures:
---- test_v6_local_lifecycle stdout ----
thread 'test_v6_local_lifecycle' panicked at 'get info: Ioctl("socaddr to ipaddr conversion")', libnet/tests/ip.rs:107:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
deleting lnt_v6ls_sim3 failed: ioctl: ioctl @fd.as_raw_fd()=3 sys::SIMNET_IOC_DELETE: Device busy (os error 16)
We can bring in the falcon ztest machinery in to make this better.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with libnet/tests/ip.rs, especially test_v6_local_lifecycle and the cleanup path shown by the failure. Read the referenced falcon ztest machinery to understand how it handles failed tests and simnet resources. Done means test failures do not leave lingering simnet interfaces and cleanup can delete them successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100