Test flake in `chaos_tests::port_settings::test_port_settings_txn_sweep`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- networking, testing-qa
Research direction
Start with chaos_tests::port_settings::test_port_settings_txn_sweep and reproduce the failure using the linked Buildomat output for additional detail. Investigate why the current PortSettings still contains link 0 when the desired settings are empty; done means the test no longer flakes and the transaction reaches the expected settings consistently.
Written by the indexing model from the issue text.
Description
Seen on #106, here. The full error is below, but the buildomat output has much more detail:
3911 2025-08-29T00:39:18.570Z Error: operation failed: desired settings: PortSettings {
3912 2025-08-29T00:39:18.570Z links: {},
3913 2025-08-29T00:39:18.570Z }
3914 2025-08-29T00:39:18.570Z current settings: PortSettings {
3915 2025-08-29T00:39:18.570Z links: {
3916 2025-08-29T00:39:18.570Z "0": LinkSettings {
3917 2025-08-29T00:39:18.570Z addrs: [],
3918 2025-08-29T00:39:18.570Z params: LinkCreate {
3919 2025-08-29T00:39:18.570Z autoneg: true,
3920 2025-08-29T00:39:18.570Z fec: Some(
3921 2025-08-29T00:39:18.570Z None,
3922 2025-08-29T00:39:18.570Z ),
3923 2025-08-29T00:39:18.570Z kr: false,
3924 2025-08-29T00:39:18.571Z lane: Some(
3925 2025-08-29T00:39:18.571Z LinkId(
3926 2025-08-29T00:39:18.571Z 0,
3927 2025-08-29T00:39:18.571Z ),
3928 2025-08-29T00:39:18.571Z ),
3929 2025-08-29T00:39:18.571Z speed: Speed100G,
3930 2025-08-29T00:39:18.571Z tx_eq: None,
3931 2025-08-29T00:39:18.571Z },
3932 2025-08-29T00:39:18.571Z },
3933 2025-08-29T00:39:18.571Z },
3934 2025-08-29T00:39:18.571Z }
- Dominant language
- Rust
- Stars
- 21
- Forks
- 3
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from oxidecomputer/dendrite
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/dendrite#380 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
oxidecomputer/dendrite#375 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
oxidecomputer/dendrite#369 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
oxidecomputer/dendrite#368 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
oxidecomputer/dendrite#359 · 1 comment ·
Maintainers usually reply within 1 day
All issues in oxidecomputer/dendrite
Similar issues
-
backend::vllm diffusion multimodal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lambdaclass/ethrex#7329 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
shadowsocks/shadowsocks-rust#2186 · 1 comment ·
-
C-bug S-awaiting-triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
juspay/hyperswitch#14479 ·
Maintainers usually reply within 1 day