Closed kasunbg closed 6 years ago
@kasunbg I've added two more solutions (scenarios) and tried the above. Solution 01-> removed run-scenario.sh Solution 02, 03 --> kept run-scenario.sh as it is
The flow doesn't fail at solution 01, it gave the warning as "WARN org.wso2.testgrid.core.ScenarioExecutor - Couldn't find any tests for the scenario " and moved to other solutions.
Hope this was observed as a failing since there were only one solution left in the repo. :) WDYT?
Please find the log below:
[pool-2-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - CARBON cannot execute java
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + x=0
[pool-2-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - Wait for the server start up
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + retry_count=60
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo 'Wait for the server start up'
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + nc -z localhost 9763
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo 'Successfully started the server!!'
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo 'Generating the deployment_ep file with the endpoints'
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo https://localhost:9443/carbon
[pool-2-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - Successfully started the server!!
[pool-2-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - Generating the deployment_ep file with the endpoints
[pool-2-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo 'Deployment has finished, test execution will commence next'
[pool-2-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - Deployment has finished, test execution will commence next
[main] WARN org.wso2.testgrid.deployment.DeploymentUtil - The deployment.json file was not found at: /home/pasindu/Developments/qgrid/temp/local-is-deployment/IS/01-local-is-deployment/bdfe164d-492d-3473-a947-ba07c1e9ff61/7/deployment.json. This is where the deployment creation outputs are stored. Continuing without the deployment outputs.
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - Executing Tests for Solution Pattern : Test scenario 01
[main] WARN org.wso2.testgrid.core.ScenarioExecutor - Couldn't find any tests for the scenario TestScenario{id='73f18e7a-015c-4aea-bd61-aee2772ffa90', name='Test scenario 01', status='RUNNING', createdTimestamp='2018-05-22 16:37:35.0', modifiedTimestamp='2018-05-23 10:07:06.0', testPlan='TestPlan{id='56a12089-4a9c-4442-9540-02b81a9fff7f', status='RUNNING', testRunNumber='7', createdTimestamp='', modifiedTimestamp='', deploymentPattern='DeploymentPattern{id='af7c62b1-33b7-42f2-bde8-30d1030827ea', name='01-local-is-deployment', createdTimestamp='2018-05-22 10:40:24.0', modifiedTimestamp='2018-05-22 10:40:24.0', product='Product{id='b5e905bc-97b4-4487-8e57-a0512bceba12', name='IS', createdTimestamp='2018-05-22 10:40:24.0', modifiedTimestamp='2018-05-22 10:40:24.0'}'}', infrastructureRepository='/home/pasindu/Developments/qgrid/temp/local-is-deployment/Infrastructure', deploymentRepository='/home/pasindu/Developments/qgrid/temp/local-is-deployment/Deployment', scenarioTestsRepository='/home/pasindu/Developments/qgrid/temp/local-is-deployment/Solutions'}'} At location /home/pasindu/Developments/qgrid/temp/local-is-deployment/Solutions/solution01
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - Executing Tests for Solution Pattern : Test scenario 03
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - Executing Test scenario 03 Test
[main] INFO org.wso2.testgrid.common.util.TestGridUtil - Execution result : This is a Dummy Scenario execution scripts
Created the tree successfully using jmeter/01-TestIS540.jmx
Starting the test @ Wed May 23 10:08:07 IST 2018 (1527050287541)
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
Tidying up ... @ Wed May 23 10:08:09 IST 2018 (1527050289090)
... end of run
after
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - ---------------------------------------
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - Executing Tests for Solution Pattern : Test scenario 02
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - Executing Test scenario 02 Test
[main] INFO org.wso2.testgrid.common.util.TestGridUtil - Execution result : This is a Dummy Scenario execution scripts
Created the tree successfully using jmeter/01-TestIS540.jmx
Starting the test @ Wed May 23 10:08:10 IST 2018 (1527050290665)
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
Tidying up ... @ Wed May 23 10:08:12 IST 2018 (1527050292253)
... end of run
after
[main] INFO org.wso2.testgrid.core.ScenarioExecutor - ---------------------------------------
[main] INFO org.wso2.testgrid.infrastructure.providers.ShellScriptProvider - Destroying test environment...
[pool-3-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - This is a Dummy Infrastructure destroy scripts!!
[pool-3-thread-1] INFO org.wso2.testgrid.common.ShellExecutor - Stopping and cleaning the IS server
[pool-3-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo 'This is a Dummy Infrastructure destroy scripts!!'
[pool-3-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + echo 'Stopping and cleaning the IS server'
[pool-3-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + bash ./wso2is-5.4.0/bin/wso2server.sh stop
[pool-3-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - bash: ./wso2is-5.4.0/bin/wso2server.sh: No such file or directory
[pool-3-thread-2] ERROR org.wso2.testgrid.common.ShellExecutor - + rm -rf wso2is-5.4.0
Process finished with exit code 0
@pasindujw I think we should print a log that says scenario.sh is missing. And, the report/dashboard UI should mention this fact as an error. wdyt?
+1, Will check on that. Thanks.
Description: Currently, the run-testplan fails silently if the run-scenario.sh script is not found. It is not clear how to solve the issue.
See the below log I got for
test-scripts/local-is-deployment/
sample.Affected Product Version: 0.9.0-m25
OS, DB, other environment details and versions:
Steps to reproduce: Execute run-testplan for test-scripts/local-is-deployment
Related Issues: