-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ChromeDriver service fails to start on Azure when Chrome Options are present #10085
Comments
Hi @RedBlack-DevOps , We're looking into your issue , we will get back to you ASAP. |
Thankyou for your quick response to this. Please keep us updated. Thankyou, Ian |
HI @RedBlack-DevOps , We have roll-out to new version , Could you please try to reproduce with the new release. Thankyou ! |
Thanks for the release but we don't seem to have permission to access that link. Can you advise? |
Hi @RedBlack-DevOps ,
|
OK no worries we will try that and let you know. |
HI @RedBlack-DevOps , Could you please provide your comments ? Thank you ! |
Hi, Sorry we (coincidentally) had downtime on our host this morning so we won't know the results until tomorrow morning. |
HI, We were able to run this morning. The image version is 20240618.1.0 can you confirm this is correct? We are still seeing the same exception when the service is started. |
Yes, Correct. |
Ok this has not resolved the issue then unfortunately. |
Kindly try to re run the pipeline now . Yesterday it got deployed to all SUs. if you're facing the same issue, please share the logs to further investigate. |
HI @RedBlack-DevOps , Could you please post your comments ? |
We still have the same issue. Passing in chrome options causes the driver service to fail: Bake.Web.CyBake.Test.Ui.SpecFlow.Features.Administration.AdministrationPageFeature.EnsureTheAdministrationAreaManagersStructureIsCorrect EnsureTheAdministrationAreaManagersStructureIsCorrect |
we started investigation on the same, we will respond to you asap. Thankyou ! |
Thanks |
Description
Hi,
We are having some issues with ChromeDriver on Azure which we can't replicate locally (on Windows 11). The issue seems to be that whenever chrome options are added to chrome driver the driver service fails to start.
As an example the following will work without any issues:
However the following will cause the driver service to fail to start:
This will result in a failure like this:
It seems now that whenever the chrome options parameter is passed the service fails to start on Azure. This wasn't the case in the past as they were used without issue.
Our Azure config is https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md
Thanks,
Ian
Platforms affected
Runner images affected
Image version and build link
20240610.1.0
Is it regression?
yes
Expected behavior
The chromedriver service starts as normal when chrome options are added
Actual behavior
the chromedriver fails to start
Repro steps
var chromeOptions = new ChromeOptions(); chromeOptions.SetLoggingPreference(LogType.Browser, LogLevel.All); chromeOptions.AddArgument("no-sandbox"); chromeOptions.AddUserProfilePreference("profile.default_content_setting_values.automatic_downloads",1); driverPath = Environment.GetEnvironmentVariable("ChromeWebDriver") ?? AppDomain.CurrentDomain.BaseDirectory; webDriver = new ChromeDriver(ChromeDriverService.CreateDefaultService(driverPath),chromeOptions);
The text was updated successfully, but these errors were encountered: