You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL (localhost/redacted) timed out after 60 seconds.
---- System.Threading.Tasks.TaskCanceledException : The request was canceled due to the configured HttpClient.Timeout of 60 seconds elapsing.
-------- System.TimeoutException : The operation was canceled.
------------ System.Threading.Tasks.TaskCanceledException : The operation was canceled.
Stacktrace
Details
at OpenQA.Selenium.Remote.HttpCommandExecutor.ExecuteAsync(Command commandToExecute)
at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.ExecuteAsync(Command commandToExecute)
at OpenQA.Selenium.WebDriver.ExecuteAsync(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.WebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Window.get_Size()
at Microsoft.AspNetCore.E2ETesting.BrowserTestBase.InitializeBrowser(String...)
Logs
Details
The test failed with a Selenium WebDriver timeout during browser initialization (InitializeBrowser). The WebDriver server stopped responding during the window resize operation, indicating a flaky infrastructure-level failure in the browser/driver communication layer.
The test RedirectStreamingEnhancedGetToInternal is failing intermittently with a Selenium WebDriver timeout during browser initialization:
OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL
(localhost/redacted) timed out after 60 seconds.
---- System.Threading.Tasks.TaskCanceledException : The request was canceled due to the configured HttpClient.Timeout of 60 seconds elapsing.
The failure occurs in BrowserTestBase.InitializeBrowser during a Window.get_Size() call. This is an infrastructure-level flakiness where the WebDriver server (Selenium chromedriver/geckodriver process) becomes unresponsive during test setup.
Root cause: This is a known pattern in E2E tests on Helix agents where the browser or WebDriver process hangs or becomes slow to respond to requests. The test itself (which verifies streaming enhanced GET redirect to an internal URL) is not at fault — the failure happens before the test body executes. This is a transient infrastructure issue.
Suggested fix: No code change needed to the test logic itself. The quarantine is precautionary while we determine if this is an ongoing CI infrastructure issue or a one-off. If the pattern recurs, consider increasing Selenium command timeouts for the components E2E test suite.
Note
🔒 Integrity filter blocked 5 items
The following items were blocked because they don't meet the GitHub integrity level.
#66531search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#65815search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#65817search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#65827search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#65816search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
Activity
github-actions commentedon May 17, 2026
Investigation
The test
RedirectStreamingEnhancedGetToInternalis failing intermittently with a Selenium WebDriver timeout during browser initialization:The failure occurs in
BrowserTestBase.InitializeBrowserduring aWindow.get_Size()call. This is an infrastructure-level flakiness where the WebDriver server (Selenium chromedriver/geckodriver process) becomes unresponsive during test setup.Root cause: This is a known pattern in E2E tests on Helix agents where the browser or WebDriver process hangs or becomes slow to respond to requests. The test itself (which verifies streaming enhanced GET redirect to an internal URL) is not at fault — the failure happens before the test body executes. This is a transient infrastructure issue.
Suggested fix: No code change needed to the test logic itself. The quarantine is precautionary while we determine if this is an ongoing CI infrastructure issue or a one-off. If the pattern recurs, consider increasing Selenium command timeouts for the components E2E test suite.
Note
🔒 Integrity filter blocked 5 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:[test-quarantine] Unquarantine RedirectionTest.RedirectStreamingEnhan…
[test-quarantine] Unquarantine RedirectionTest.RedirectStreamingEnhan…