[jbosstools-issues] [JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12824936#comment-12824936 ] 

Mickael Istria commented on JBIDE-15612:
----------------------------------------

Actually, SWTBot timeout is configured to 15 minutes and the error in log appears 15 minutes after starting installation from Central. Then the confirm Exit dialog shows up and gets stucked (because the Test Thread has finished there), and waits for the job timeout, which is 840 minutes.
I'll have a look at having the workbench actually close on test failure instead of getting the exit pop-up, but it's not the source of the error. The cause is that installation from Central takes more than 15 minutes, which seems a bit too long. Does installation from Central contact other p2 sites?
                
> install-grinder gets stuck after installing JBDS
> ------------------------------------------------
>
>                 Key: JBIDE-15612
>                 URL: https://issues.jboss.org/browse/JBIDE-15612
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: qa
>    Affects Versions: 4.1.1.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Pavol Srna
>             Fix For: 4.1.1.Beta1, 4.1.1.CR1
>
>         Attachments: install-grinder-gets-stuck.png
>
>
> Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out). 
> Steps to reproduce locally:
> {code}
>   # as root, install these if not already installed
>   yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
>   exit
>   # in a terminal, run this:
>   vncserver
>   # then launch vinagre to connect to the VNC session:
>   vinagre localhost:1
>   # within the VNC session, run this:
>     git clone https://github.com/jbosstools/jbosstools-install-grinder/
>     cd jbosstools-install-grinder
>     mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
>     -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
>     cd scripts/target/scripts-*-delivery/
>     SCRIPTDIR=`pwd`
>     WORKSPACE=/tmp/jbtcentraltarget-verify
>     rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
>     # must be lowercase kepler
>     eclipseBundleVersion=kepler.R
>     # or
>     eclipseBundleVersion=kepler.SR1
>     # path to where you store eclipse tar.gz files
>     eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles
>     groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
>     eclipseCacheDirectory=${eclipseCacheDirectory} \
>     eclipseBundleVersion=${eclipseBundleVersion}
>     INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbosstools-directory.xml"
>     # or 
>     INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/devstudio-directory.xml"
>     groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
> {code}
> Here's a screenshot:
> !install-grinder-gets-stuck.png!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira