From 58ef00a36660de1701bd9d550897cdf891c82fcf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dar=C3=ADo=20Kondratiuk?= Date: Mon, 16 Feb 2026 19:34:02 -0300 Subject: [PATCH] Fix flaky ShouldProvideAccessToElements OOPIF test timeout Increase WithTimeout from 5s to 30s to match upstream behavior where no explicit timeout is set and the test framework default (~25-30s) applies. OOPIF frame creation can exceed 5s in resource-constrained CI. Co-Authored-By: Claude Opus 4.6 --- lib/PuppeteerSharp.Tests/OOPIFTests/OOPIFTests.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/PuppeteerSharp.Tests/OOPIFTests/OOPIFTests.cs b/lib/PuppeteerSharp.Tests/OOPIFTests/OOPIFTests.cs index 9d0f599a9..f57eded06 100644 --- a/lib/PuppeteerSharp.Tests/OOPIFTests/OOPIFTests.cs +++ b/lib/PuppeteerSharp.Tests/OOPIFTests/OOPIFTests.cs @@ -239,7 +239,7 @@ await FrameUtils.AttachFrameAsync( "frame1", TestConstants.CrossProcessHttpPrefix + "/empty.html" ); - var frame = await frameTask.WithTimeout(5_000); + var frame = await frameTask.WithTimeout(30_000); await frame.EvaluateFunctionAsync(@"() => { const button = document.createElement('button'); button.id = 'test-button';