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
Note: only the latest version is supported
I am using latest version available on github public repo qaf-blank-project-maven
I want to know whether headfull chrome option is supported or not.
Steps To Reproduce
1.Copy default repo in your own private repo
2.Create Run Automation Tests.yml file in workflow
3.Run the pipeline
Expected behavior
Run Test should pass
Actual behavior
Run Test is failing with following error
Unable to create driver instance in 1st attempt with retry timeout of 0 seconds. You can check/set value of 'driver.init.retry.timeout' appropriately to set retry timeout on driver initialization failure.Unable to Create Driver Instance for chrome: unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'fv-az190-893', ip: '10.1.1.72', os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-1023-azure', java.version: '1.8.0_352'
Driver info: driver.version: ChromeDriver
Is the issue reproducible on runner?
QAS
Maven
Gradle
Ant
Eclipse
Test case sample
Please, share the test case (as small as possible) which shows the issue
It is working with headless option but I want chrome to run without headless option
@cjayswal thank you for the response. Can you pls provide more detail on what can be changed so that test case in github action with headless-off run with success?
QAF Version
I want to know whether headfull chrome option is supported or not.
Steps To Reproduce
Expected behavior
Run Test should pass
Actual behavior
Run Test is failing with following error
Unable to create driver instance in 1st attempt with retry timeout of 0 seconds. You can check/set value of 'driver.init.retry.timeout' appropriately to set retry timeout on driver initialization failure.Unable to Create Driver Instance for chrome: unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'fv-az190-893', ip: '10.1.1.72', os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-1023-azure', java.version: '1.8.0_352'
Driver info: driver.version: ChromeDriver
Is the issue reproducible on runner?
Test case sample
here is Run Automation Test.yml file
on:
push:
pull_request:
jobs:
build:
The text was updated successfully, but these errors were encountered: