You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Christofer Dutz (JIRA)" <ji...@apache.org> on 2016/06/28 06:47:57 UTC

[jira] [Comment Edited] (INFRA-11706) Unable to run GUI tests on windows build agents

    [ https://issues.apache.org/jira/browse/INFRA-11706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352479#comment-15352479 ] 

Christofer Dutz edited comment on INFRA-11706 at 6/28/16 6:47 AM:
------------------------------------------------------------------

I did run the build a few days ago when the machine came up ... Unfortunately I couldn't run the build as it seemed that only Java 8 was installed. I just ran the job again and it's still the same problem:

{code}
Error: JAVA_HOME is set to an invalid directory. 
JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64" 
Please set the JAVA_HOME variable in your environment to match the 
location of your Java installation. 
{code}

However we need Java 1.7 as with 1.8 the resulting libs won't work in 1.6 and 1.7 :-(

Chris


was (Author: cdutz):
I did run the build a few days ago when the machine came up ... Unfortunately I couldn't run the build as it seemed that only Jaba 8 was installed:

{code}
Error: JAVA_HOME is set to an invalid directory. 
JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64" 
Please set the JAVA_HOME variable in your environment to match the 
location of your Java installation. 
{code}

However we need Java 1.7 as with 1.8 the resulting libs won't work in 1.6 and 1.7 :-(

Chris

> Unable to run GUI tests on windows build agents
> -----------------------------------------------
>
>                 Key: INFRA-11706
>                 URL: https://issues.apache.org/jira/browse/INFRA-11706
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Christofer Dutz
>            Assignee: Chris Lambertus
>
> It seems that when running the Jenkins agent as a windows service, builds are not able to start and communicate with the created GUI application. In our case our tests start the FlashPlayer for unit tests. Even if it's possible to execute the command manually on the machine, doing this in an automated was, does not seem to work. I keep on getting timeouts. 
> We had this problem on our project-private Jenkins and it seems the only option the guys came up with was to auto-login to the Jenkins account and start the agent using Java Webstart.
> If we want to come back to the ASF infra machines, we need to run the GUI tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)