From 469ead43ce222411ed20d2390ce4167d8755e7f3 Mon Sep 17 00:00:00 2001 From: Ryan Goodfellow Date: Thu, 8 Jan 2026 22:53:21 +0000 Subject: [PATCH] disable test_port_settings_txn_sweep The implementation of the port settings apply function has moved beyond the original design intent. Due to that, this test is just causing pain in CI and is no longer meaningful. If we come back and revisit the port settings apply design design, as some of the comments in #108 suggest, this test can be re-enabled. --- dpd-client/tests/chaos_tests/port_settings.rs | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/dpd-client/tests/chaos_tests/port_settings.rs b/dpd-client/tests/chaos_tests/port_settings.rs index ff30ffa..0bbc7ae 100644 --- a/dpd-client/tests/chaos_tests/port_settings.rs +++ b/dpd-client/tests/chaos_tests/port_settings.rs @@ -364,6 +364,15 @@ const OPERATION_FAILURE_RATE: f64 = 0.1; // no meaningful consistency check to make. The important part in that case is // we know bad state exists. What to do about that is outside the context of // this test. +// +// NOTE +// Disabling this test due to +// - https://github.com/oxidecomputer/dendrite/issues/108 +// for the time being. The implementation of the port settings endpoint has +// moved beyond it's design intent, and this test suite is no longer valid +// and is just cauing CI pain. +// +#[ignore] #[tokio::test] async fn test_port_settings_txn_sweep() -> anyhow::Result<()> { let config = AsicConfig::uniform_set(TESTING_RADIX, OPERATION_FAILURE_RATE);