Leadfoot_command test failing when running yarn test:ui

[_princesscode (Emily Garcia)]

Hi,

I've managed to get through most test cases, but when running yarn test:ui my suite continues to fail.

Running "run:testUIServer" (run) task
  log   [02:23:19.794] [info][optimize] Optimizing and caching bundles for stateSessionStorageRedirect, status_page, timelion, sense-tests and kibana. This may take a few minutes
  log   [02:23:45.531] [info][optimize] Optimization of bundles for stateSessionStorageRedirect, status_page, timelion, sense-tests and kibana complete in 25.73 seconds
  log   [02:23:45.636] [info][status][plugin:kibana@6.2.3] Status changed from uninitialized to green - Ready
  log   [02:23:45.686] [info][status][plugin:elasticsearch@6.2.3] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [02:23:47.320] [info][status][plugin:timelion@6.2.3] Status changed from uninitialized to green - Ready
  log   [02:23:47.337] [info][status][plugin:console@6.2.3] Status changed from uninitialized to green - Ready
  log   [02:23:47.342] [info][status][plugin:metrics@6.2.3] Status changed from uninitialized to green - Ready
  log   [02:23:47.371] [info][listening] Server running at http://localhost:5620

Running "functional_test_runner:functional" (functional_test_runner) task
 debg  Loading config file from "/home/ansible/kibana/test/functional/config.js"
 debg  Loading config file from "/home/ansible/kibana/test/common/config.js"
 info  Config loaded
  log   [02:23:47.420] [warning] You're running Kibana 6.2.3 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v6.3.0 @ 127.0.0.1:9220 (127.0.0.1)
  log   [02:23:47.440] [info][status][plugin:elasticsearch@6.2.3] Status changed from yellow to green - Ready
 info  Starting local chromedriver at port 9515
 debg  [chromedriver:ping] attempting to reach chromedriver at "http://localhost:9515"
 debg  [chromedriver:ping] failure
 debg  [chromedriver:ping] waiting for 500 before next ping
 debg  [chromedriver:stdout] Starting ChromeDriver 2.33.506092 (733a02544d189eeb751fe0d7ddca79a0ee28cce4) on port 9515
   Only local connections are allowed.
 debg  [chromedriver:ping] attempting to reach chromedriver at "http://localhost:9515"
 debg  [chromedriver:ping] success
 debg  [leadfoot:command] Creating session
 debg  [leadfoot:command] Creating session
 debg  [leadfoot:command] Creating session
 debg  [leadfoot:command] Creating session
 warn  Failure loading service "remote"
ERROR  Error: remote failed to start within 2 minutes
       at /home/ansible/kibana/test/functional/services/remote/leadfoot_command.js:41:13
       at undefined.next (native)
       at step (/home/ansible/kibana/test/functional/services/remote/leadfoot_command.js:93:191)
       at /home/ansible/kibana/test/functional/services/remote/leadfoot_command.js:93:361

 debg  [leadfoot:command] Creating session
Warning: Error: Failure initializing 1 service(s)
at /home/ansible/kibana/src/functional_test_runner/lib/providers/provider_collection.js:61:15
at undefined.next (native)
at step (/home/ansible/kibana/src/functional_test_runner/lib/providers/provider_collection.js:12:191)
at /home/ansible/kibana/src/functional_test_runner/lib/providers/provider_collection.js:12:361
 Use --force to continue.

Aborted due to warnings.
error An unexpected error occurred: "Command failed.
Exit code: 6
Command: sh
Arguments: -c grunt test:ui
Directory: /home/ansible/kibana
Output:
".
info If you think this is a bug, please open a bug report with the information provided in "/home/ansible/kibana/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

My environment is Debian 9.4 and this is my server setup

# dependencies before doing anything
sudo apt update && sudo apt upgrade -y
sudo apt install git default-jdk build-essential ruby-dev rpm -y
java -version
sudo gem install fpm -v 1.5.0
sudo gem install pleaserun -v 0.0.24

# NVM + yarn
wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh | bash
nvm install 6.12.2
nvm use 6.12.2
npm install -g yarn

# download google-chrome
sudo dpkg -i <chrome>
sudo apt --fix-broken install
sudo apt-get install python-pip
sudo pip install selenium

# kibana
git clone https://github.com/elastic/kibana.git
cd kibana
git fetch --tags
git checkout tags/v6.2.3 -b v6.2.3
yarn
yarn test:ui

Is there anywhere I can find all actual dependencies that are needed for running the kibana suite, because I've comb through the contribution.md file over and over and I seem to keep getting errors on un-modified kibana repos on the latest tagged version 6.2.3

By dependencies, I mean packages from an OS level to npm package level to chrome browser need, etc...

[LeeDr (Lee Drengenberg)]

Hi Emily,

Did you do yarn kbn bootstrap ? That sets up all (or almost all) of the dependencies.

There is a small problem in https://github.com/elastic/kibana/blob/6.2/package.json#L15 which is causing you to get Elasticsearch 6.3.0. In general, having Elasticsearch 1 minor version ahead of Kibana should work (just logs a warning). But you should probably go ahead and change that 6.x to 6.2 in your local copy of that file just to be in sync.

You could also try running yarn test:ui:server instead of yard test:ui. This will start Elasticsearch, Kibana, and the chromedriver and leave them running. In this way you can open Elasticsearch at http://localhost:9220 and/or Kibana at http://localhost:5620 to make sure they're up OK.

Then with test:ui:server running, you can try starting the tests with node scripts/functional_test_runner over and over without having to wait for all the server parts to come up.

Also, what version of java are you running? Elasticsearch should run with either 8 or 9, but to build it requires 9. I think the way we're starting it with test:ui or test:ui:server 8 would be OK.

For now I would just do the yarn kbn bootstrap and change that 6.x to 6.2 and then start yarn test:ui:server and let us know how that works.

Regards,
Lee