Katalon + Docker .. test execution hangs

Hi,
We are testing CI/CD pipeline that deploys Katalon Studio docker image to our target machine in AWS.
When we try to execute sample tests (GitHub - katalon-studio-samples/ci-samples: Sample configurations for various CI systems.) it looks like test start execution but no progress is made.
Any suggestions on how to resolve this issue? On 2nd run (directly from the target machine) reports folder was generated (content is attached) but no error is available.

Here is some output from the execution

 ./docker-images-samples/katalon/run_chrome.sh++ pwd+ current_dir=/home/gecloud+++ dirname ./docker-images-samples/katalon/run_chrome.sh++ cd ./docker-images-samples/katalon++ pwd+ project_dir=/home/gecloud/docker-images-samples/katalon+++ dirname ./docker-images-samples/katalon/run_chrome.sh++ cd ./docker-images-samples/katalon/..++ pwd+ reports_dir=/home/gecloud/docker-images-samples/reports/chrome+ rm -rfv /home/gecloud/docker-images-samples/reports/chrome+ mkdir -p /home/gecloud/docker-images-samples/reports/chrome+ katalon_opts='-browserType="Chrome" -retry=0 -statusDelay=15 -testSuitePath="Test Suites/TS_RegressionTest"'+ docker run --rm -v /home/gecloud/docker-images-samples/katalon:/katalon/katalon/source:ro -v /home/gecloud/docker-images-samples/reports/chrome:/katalon/katalon/report -e 'KATALON_OPTS=-browserType="Chrome" -retry=0 -statusDelay=15 -testSuitePath="Test Suites/TS_RegressionTest"' katalonstudio/katalonGoogle Chrome 64.0.3282.186 Mozilla Firefox 58.0.2Katalon Studio 5.3.1Starting Katalon Studio+ echo 'Starting Katalon Studio'++ pwd+ current_dir=/+ tmp_dir=/katalon/katalon/tmp+ mkdir -p /katalon/katalon/tmp+ chmod -R 777 /katalon/katalon/tmp+ project_dir=/katalon/katalon/project+ mkdir -p /katalon/katalon/project+ cp -r /katalon/katalon/source/. /katalon/katalon/project+ touch /katalon/katalon/project/.classpath+ chmod -R 777 /katalon/katalon/project+ report_dir=/katalon/katalon/report+ mkdir -p /katalon/katalon/report+ chmod -R 777 /katalon/katalon/report++ find /katalon/katalon/project -maxdepth 1 -type f -name '*.prj'+ project_file=/katalon/katalon/project/test.prj+ cmd='/opt/katalonstudio/katalon -runMode=console -reportFolder=/katalon/katalon/report -projectPath=/katalon/katalon/project/test.prj -browserType="Chrome" -retry=0 -statusDelay=15 -testSuitePath="Test Suites/TS_RegressionTest"'+ /katalon/base/scripts/xvfb.sh startStarting virtual X frame buffer :99 1024x768x24+ XVFB=/usr/bin/Xvfb+ XVFBARGS=':99 -screen 0 1024x768x24 -fbdir /var/run -ac'+ PIDFILE=/var/run/xvfb.pid+ case "$1" in+ echo -n 'Starting virtual X frame buffer :99 1024x768x24'+ start-stop-daemon --start --quiet --pidfile /var/run/xvfb.pid --make-pidfile --background --exec /usr/bin/Xvfb -- :99 -screen 0 1024x768x24 -fbdir /var/run -ac.+ echo .+ exit 0+ cd /katalon/katalon/tmp+ eval '/opt/katalonstudio/katalon -runMode=console -reportFolder=/katalon/katalon/report -projectPath=/katalon/katalon/project/test.prj -browserType="Chrome" -retry=0 -statusDelay=15 -testSuitePath="Test Suites/TS_RegressionTest"'++ /opt/katalonstudio/katalon -runMode=console -reportFolder=/katalon/katalon/report -projectPath=/katalon/katalon/project/test.prj -browserType=Chrome -retry=0 -statusDelay=15 '-testSuitePath=Test Suites/TS_RegressionTest'Starting Groovy-Eclipse compiler resolver.  Specified compiler level: unspecified131 2.4.7.xx-201611170128-e46 = ACTIVE--------------------------------------------------------------------------------Test Suites/TS_RegressionTest - Chrome - 20180302_151539.................0/2(0%)----------------------------------------------------------------------------------------------------------------------------------------------------------------Test Suites/TS_RegressionTest - Chrome - 20180302_151539.................0/2(0%)----------------------------------------------------------------------------------------------------------------------------------------------------------------Test Suites/TS_RegressionTest - Chrome - 20180302_151539.................0/2(0%)----------------------------------------------------------------------------------------------------------------------------------------------------------------Test Suites/TS_RegressionTest - Chrome - 20180302_151539.................0/2(0%)--------------------------------------------------------------------------------

and it continues like this…

We run these tests again (directly from the target machine) and similarly test execution seams to be hanging but reports were generated (attached).

Any suggestions?

Thanks,
Rasko

reports.zip

Do you have special settings in your Project Settings such as capturing videos?

I am using official Katalon example code from https://github.com/katalon-studio/docker-images-samples … and yes it looks like video recording option is enabled.
Also, it looks like the latest version 5.3.1 (pulled from docker registry) requires proxy settings to be set? What if there is no proxy? (like in our case)

I was able to get it to work with our sample code. Thanks!

HI I am also facing similar issue, How did you make it work ?
For me below keeps on coming indefinitely

Request sent successfully.

06-01-2018 10:59:21 AM - [START] - Start Test Suite : Test Suites/fundingReturnTestSuite

06-01-2018 10:59:21 AM - [RUN_DATA] - Logging run data ‘hostName’ with value ‘root - e26600ef3642’

06-01-2018 10:59:21 AM - [RUN_DATA] - Logging run data ‘os’ with value ‘Linux 64bit’

06-01-2018 10:59:21 AM - [RUN_DATA] - Logging run data ‘hostAddress’ with value ‘172.17.0.2’

06-01-2018 10:59:21 AM - [RUN_DATA] - Logging run data ‘katalonVersion’ with value ‘5.4.1.1’

06-01-2018 10:59:22 AM - [START] - Start Test Case : Test Cases/AdminLogin

06-01-2018 10:59:22 AM - [INFO] - Evaluating variables for test case

Start recording video for test case ‘Test Cases/AdminLogin’.

06-01-2018 10:59:24 AM - [START] - Start action : openBrowser

06-01-2018 10:59:25 AM - [INFO] - Opening browser

06-01-2018 10:59:25 AM - [INFO] - Starting ‘Chrome’ driver

06-01-2018 10:59:25 AM - [INFO] - Action delay is set to 0 seconds

Starting ChromeDriver 2.35.528139 (47ead77cb35ad2a9a83248b292151462a66cd881) on port 20971

Only local connections are allowed.

--------------------------------------------------------------------------------

Test Suites/fundingReturnTestSuite - Chrome - 20180601_105917…0/1(0%)

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Test Suites/fundingReturnTestSuite - Chrome - 20180601_105917…0/1(0%)

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Test Suites/fundingReturnTestSuite - Chrome - 20180601_105917…0/1(0%)

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Test Suites/fundingReturnTestSuite - Chrome - 20180601_105917…0/1(0%)

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Test Suites/fundingReturnTestSuite - Chrome - 20180601_105917…0/1(0%)

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Test Suites/fundingReturnTestSuite - Chrome - 20180601_105917…0/1(0%)

--------------------------------------------------------------------------------

Hi All,

I found the root cause of issue after 2 days research.

Root cause for my case was - we were using AWS t2.micro instance which has RAM of 1GB.
When we run the test Docker Image when initialised creates a container which requires lots of memory to initialise. In addition when headless chrome is launched it consumes memory further and that causes Out of memory issue as RAM was only 1 GB. So Please make sure you have sufficient RAM to run this test successfully. It was causing whole EC2 instance to hung.

Cheers!!
Rishabh