From 320b788a50584ecbb72ef916af42dd884606d776 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=94=90=E5=B0=8F=E9=B8=AD?= Date: Mon, 10 Aug 2026 22:20:34 +0800 Subject: [PATCH] test(admin): relax object-lambda SNI test timeout under full-suite load (#5923) The SNI preservation test is the only object-lambda test doing a real TLS handshake; the shared helper's 2s whole-request timeout turns concurrent fsync-heavy TestECStoreEnv neighbors into a deterministic TimedOut when the per-build nextest schedule overlaps them. The test verifies SNI, not latency, so widen its budget to a still-bounded 30s. --- rustfs/src/admin/router.rs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/rustfs/src/admin/router.rs b/rustfs/src/admin/router.rs index e6756b7fa..d7249404d 100644 --- a/rustfs/src/admin/router.rs +++ b/rustfs/src/admin/router.rs @@ -4671,6 +4671,11 @@ mod tests { Url::parse(&format!("https://object-lambda.test:{}/transform", address.port())).expect("object lambda TLS endpoint"); let mut config = object_lambda_test_config(endpoint.clone()); config.client_ca = ca_path.to_string_lossy().into_owned(); + // This is the only object-lambda test that performs a real TLS + // handshake; under a full-suite nextest run the CPU contention from + // neighboring tests pushes it past the helper's tight 2s request + // deadline. SNI preservation, not latency, is under test here. + config.response_header_timeout = Some(Duration::from_secs(30)); let response = build_object_lambda_http_client_with_resolver(&config, StaticResolver(address.ip())) .expect("object lambda TLS client should build")