NW V2.0.X not working on AWS code build with ubrantu image

[suraj007118]

Describe the bug

Started child process for:  specs/home-page/whatsNewTest.js 

 specs/home-page/whatsNewTest.js  Initializing with Webdriver 
 specs/home-page/whatsNewTest.js  [Home Page/Whats New Test] Test Suite 
 specs/home-page/whatsNewTest.js  ────────────────────────────────────────────────────────────────────────── 
 specs/home-page/whatsNewTest.js  - Starting ChromeDriver on port 9515... 
 specs/home-page/whatsNewTest.js  ⚠ Failed to connect to ChromeDriver on localhost with port 9515. 

┌ ────────────────── ✔  specs/home-page/whatsNewTest.js  ┐
│                                                        │
│                                                        │
│                                                        │
└────────────────────────────────────────────────────────┘

 specs/client-portal/footerTest.js  Response 500 POST /session (1093ms) 
 specs/client-portal/footerTest.js  { 
 specs/client-portal/footerTest.js       value: { 
 specs/client-portal/footerTest.js         error: 'unknown error', 
 specs/client-portal/footerTest.js         message: 'unknown error: Chrome failed to start: exited abnormally.\n' + 
 specs/client-portal/footerTest.js           "  (unknown error: DevToolsActivePort file doesn't exist)\n" + 
 specs/client-portal/footerTest.js           '  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)', 
 specs/client-portal/footerTest.js         stacktrace: '' 
 specs/client-portal/footerTest.js       } 
 specs/client-portal/footerTest.js    } 
 specs/client-portal/footerTest.js  ⚠ Failed to connect to ChromeDriver on localhost with port 9515. 

Sample test

sampleTest.js

// Please add the sample test here

module.exports = {
  sampleTest: function(browser) {

  }
}

Run with command

"npm run $DeploymentEnvironment-contentStack"
e.g
npm run UAT-contentStack.

Verbose output

debug.log

<!-- Include the verbose output, if possible (run nightwatch with `--verbose` argument) -->

Configuration

nightwatch.json

const env = process.env.npm_lifecycle_event;

const userData = require(`./configs/users/usersConfig${env.split("-")[0]
}.json`);
const testData = require("./testData/proposal/proposalProcessData.json");
const otherTestData = require("./testData/otherTestData.json");
const envData = require(`./configs/environments/${env.split("-")[0]}.json`);
const chromedriver = require("chromedriver");
const apiKeys = require(`./configs/apiKeys/${env.split("-")[0]}.json`);

const chrome_webdriver = {
  start_process: true,
  server_path: chromedriver.path,
  port: 9515,
  cli_args: {
    trustAllSSLCertificates: true
  }
};

const settings = {
  src_folders: ["specs"],
  page_objects_path: ["page-objects"],
  custom_commands_path: ["custom-commands","./node_modules/nightwatch-xhr/es5/commands"],
  custom_assertions_path: ["./node_modules/nightwatch-xhr/es5/assertions"],
  output_folder: "./reports",

  parallel_process_delay: 30,
  test_workers: {
    enabled: true,
    workers: 6
  },
  live_output: true,

  test_settings: {
    default: {
      globals: {
        userConfig: userData,
        testDataConfig: testData,
        otherDataConfig: otherTestData,
        envDataConfig: envData,
        environment: env.split("-")[0],
        apiKey: apiKeys
      },
      abortOnAssertionFailure: false,
      waitForConditionPollInterval: 300,
      waitForConditionTimeout: 10000,
      retryAssertionTimeout: 5000,
      end_session_on_fail: true,
      skip_testcases_on_fail: false
    },
    chromeHeadless: {
      desiredCapabilities: {
        browserName: "chrome",
        javascriptEnabled: true,
        acceptSslCerts: true,
        chromeOptions: {
          args: [
            "--no-sandbox",
            "--ignore-certificate-errors",
            "--headless",
            "--disable-gpu",
            "--accept-alerts",
            "window-size=2000,3000"
          ],
           binary: "/usr/bin/google-chrome-stable"
        },
        w3c: false
      },
      screenshots: {
        enabled: true,
        path: "./reports"
      }
    },
    chromeBrowser: {
      desiredCapabilities: {
        browserName: "chrome",
        javascriptEnabled: true,
        acceptSslCerts: true,
        acceptInsecureCerts: true,
        chromeOptions: {
          args: [
            "--no-sandbox",
            "--ignore-certificate-errors",
            "--disable-gpu",
            "--accept-alerts"
          ]
        },
        w3c: false
      },
      screenshots: {
        enabled: true,
        path: "./reports"
      }
    }
  }
};
console.log("Initializing with Webdriver");
settings.webdriver = chrome_webdriver;
module.exports = settings;

Your Environment

Executable	Version
nightwatch --version	2.0.10
npm --version	VERSION
node --version	12.22.2
14.17.2
Browser driver	Version
---	---
NAME	VERSION
chromedriver	94

OS	Version
NAME	VERSION

| Ubuntu | 20.04 |

[beatfactor]

Can you please format the settings code properly?

[suraj007118]

@beatfactor Not sure what you mean by 'format settings code property'.
Can you please elaborate?
Are you referrring to lines of code in my nightwatch.conf.js under attribute "test_settings"?

[swrdfish]

@suraj007118 in the issue description, the configuration part came as plain text, and is very hard to read.
Can you please edit your description and format that part as code?

[suraj007118]

@swrdfish Hi,
How can I format that part as code?
I tried attachnig nightwatch.conf.js file but that type is not supported.

[swrdfish]

It has been fixed.

Here are the formatting rules for reference: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax

[vaibhavsingh97]

@suraj007118 Looks like the Chrome driver failed to spawn the Chrome instance due to the 'Unknown error: DevToolsActivePort file does not exist, it's unrelated to Nightwatch. On a google search, stumble upon this answer which might a fix for your issue

[suraj007118]

Hi Vaibhav,
Please refer my reply here #3130
The issue occurs only with NW V2.0, for 1.7.11 v it works well in AWS code build.
Somthing is not right with v2.0 when it comes to execution over aws code build linux boxes

[hongdeyuan]

@suraj007118 Looks like the Chrome driver failed to spawn the Chrome instance due to the 'Unknown error: DevToolsActivePort file does not exist, it's unrelated to Nightwatch. On a google search, stumble upon this answer which might a fix for your issue

Maybe this is a situation：

According to chromedriver source code the message is created in ParseDevToolsActivePortFile method. This method is called from the loop after launching chrome process.

In the loop the driver check if the chrome process is still running and if the ParseDevToolsActivePortFile file was already created by chrome. There is a hardcoded 60s timeout for this loop.

[suraj007118]

It is related to Nightwatch only because same code works well with AWS when NW version is 1.7.11.
When I change version to 2.x.x it start to give below error:

Why the error does not occur with nightwatch v 1.7.11, rest all configurations remains same.

Can you please help here, we are not able to leverage benefit of V2.0 with AWS code build execution
Can you try running NW V2.x over aws code build?

Looks like the NW V2 has different behavior when it comes to chrime, looking at error below

---

Starting ChromeDriver on port 9515...
| Response 500 POST /session (56ms)
| {
| value: {
| error: 'unknown error',
| message: 'unknown error: Chrome failed to start: exited abnormally.\n' +
| " (unknown error: DevToolsActivePort file doesn't exist)\n" +
| ' (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)',
| stacktrace: ''
| }
| }
| Failed to connect to ChromeDriver on localhost with port 9515.

---

[swrdfish]

Looking into it, will update soon.

[suraj007118]

Thank you Binayak [swrdfish], eagerly waiting to hear from you on the issue.

[suraj007118]

@swrdfish Do you have any update on this?
We really want to leverage v2.x.x.

[suraj007118]

Hey @swrdfish ,
Any luck so far? Is it working fine? Are you getting error "Connected to ChromeDriver on port undefined"
Looks like it is a port issue.

[swrdfish]

With the bug fixe I am not getting the error anymore.. have you tried with the fix form the PR #3258 ?

[suraj007118]

I checked the PR but did not understand what changes do I need to make at my end to make it work.
Your fix is not yet released as a part of a new released version, how can I leverage it?
Can you please help?

[swrdfish]

A release planned for next week, the fix will ship with that, so maybe wait for that.

Also there is discord channel, you can join that.. members of the team might be able to better help you there.

[suraj007118]

Ok, but with next release what changes do I need to make -
1 . user workers and --parallel flag both
2. only user -parallel flag and do not use workers
?

[suraj007118]

@swrdfish I am using NW v 2.2.3 and still getting failure "Connected to ChromeDriver on port undefined" , it also says "Starting ChromeDriver on auto-generated port..."

I have removed lines of code mentioning test workers from night.conf.js file
Added --parallel flag
tried with both chromeOptions and 'goog:chromeOptions' - getting same error

Also, if I keep workers and remove --parallel flag then also tests fail