[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24803:
---------------------------------------
I have a complaint:
When I get to the first page where I am asked to locate EAP 6.4, there is a warning at the top. I browse to EAP 6.4 and the warning is still there - shouldn't it disappear? OK, now I can click Next. But before I do, I remove the path to EAP 6.4 to see what happens - I can still click Next.
> Add JBoss DV 6.3 to Download Runtimes Wizard
> --------------------------------------------
>
> Key: JBIDE-24803
> URL: https://issues.jboss.org/browse/JBIDE-24803
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard.
> I've also created JDF-867.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-25010) Fix some issues in CDI tests
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-25010:
------------------------------------
Summary: Fix some issues in CDI tests
Key: JBIDE-25010
URL: https://issues.jboss.org/browse/JBIDE-25010
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests
Affects Versions: 4.5.1.AM2
Reporter: Lukáš Valach
Assignee: Lukáš Valach
Fix For: 4.5.1.AM2
CDI test should run arains AS 7.1 not against EAP 7. Some tests have to be fixed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24964) HUDSON_STATIC_ENV not defined for windows and osx slaves
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24964?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24964:
---------------------------------------
I am fixing this for mac slaves.
We have two mac machines physically co-located with our central ci infrastructure, so it makes sense to reuse the static_build_env mount there:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/computer/dev...
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/computer/dev...
What I did is:
echo "static_build_env -fstype=nfs,soft,rw nfs-int.rhev-ci.eng.rdu2.redhat.com:/dev-platform-jenkins/hudson/static_build_env" >> /etc/auto_qa
so it's mounted under /qa/static_build_env
Then I changed the jbossqa user UID to 600 because otherwise it would be problematic (uid 600 is used on all linux slaves) following this guide:
https://www.inteller.net/notes/change-user-id-on-snow-leopard
Finally, I added this env variable to the slave config:
HUDSON_STATIC_ENV=/qa/static_build_env
On the other three slaves (located in Brno) I simply created a local dir and set up the env var for that:
HUDSON_STATIC_ENV=/jenkins/static_build_env
Slaves:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/computer/big...
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/computer/zamek/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/computer/domek/
Windows still needs to be fixed.
> HUDSON_STATIC_ENV not defined for windows and osx slaves
> --------------------------------------------------------
>
> Key: JBIDE-24964
> URL: https://issues.jboss.org/browse/JBIDE-24964
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.5.x
>
>
> On windows and osx slaves, HUDSON_STATIC_ENV is not defined. On rhel7 slaves, it's defined as /home/hudson/static_build_env
> Could an equivalent path be set for other OSes, so we can benefit from this NFS-mounted shared space?
> Currently when we run itests on multiple OSes, we see stuff like this, when passing the path to -Ddownload.cache.directory=:
> {code:title=rhel7 - HUDSON_STATIC_ENV = /home/hudson/static_build_env}
> 16:05:48 [rhel7] $ /mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /tmp/settings2086504014812240990.xml -Djdk=openjdk-1.8 -Dlabel_exp=rhel7
> -Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache
> -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=rhel7 -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last -Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last -Djbosstools.test.jre.5=/qa/tools/opt/x86_64/jdk1.5.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum -DjgitDirtyWorkingTree=warning
> {code}
> {code:title=win81 - HUDSON_STATIC_ENV not defined}
> 16:05:51 [win81] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings7229513778735293013.xml -Djdk=openjdk-1.8 -Dlabel_exp=win81
> -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache
> -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win81" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum" -DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"
> {code}
> {code:title=win10 - HUDSON_STATIC_ENV not defined}
> 16:05:48 [win10] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings8339429706904285132.xml -Djdk=openjdk-1.8 -Dlabel_exp=win10
> -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache
> -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win10" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum" -DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"
> {code}
> {code:title=macosx - HUDSON_STATIC_ENV not defined}
> 16:05:46 [macosx] $ /jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /var/folders/tp/hcfshtz152n2t8y4jfl08w140000gp/T/settings6780477723089804684.xml -Djdk=jdk1.8 -Dlabel_exp=macosx
> -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache
> -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=jdk1.8,label_exp=macosx -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/osx/jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=/qa/tools/opt/osx/jdk1.7.0_last -Djbosstools.test.jre.6=/qa/tools/opt/osx/jdk1.8.0_last -Djbosstools.test.jre.5=/qa/tools/opt/osx/jdk1.8.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum -DjgitDirtyWorkingTree=warning
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24886) deprecate JDK5-dependent tests or enable a way to skip them on OSX (as no JDK5 is available there)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24886?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-24886.
-------------------------------
Resolution: Rejected
Seems none of the tests actually require java5
> deprecate JDK5-dependent tests or enable a way to skip them on OSX (as no JDK5 is available there)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24886
> URL: https://issues.jboss.org/browse/JBIDE-24886
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> In searching for */JRE_5_HOME\|jre.5\|jre5\|jdk5\|jdk.5/*, I've only found TWO files which make use of the JDK5/JRE5 constants, so this might be fairly simple.
> {code:title=as/plugins/org.jboss.ide.eclipse.as.wtp.core/src/org/jboss/ide/eclipse/as/core/util/IJBossRuntimeResourceConstants.java}
> 63: public static final String AOP_JDK5_DEPLOYER = "jboss-aop-jdk50.deployer"; //$NON-NLS-1$
> 65: public static final String JBOSS_AOP_JDK5_JAR = "jboss-aop-jdk50.jar"; //$NON-NLS-1$
> 93: public static final String JBOSS_ASPECT_LIBRARY_JDK5_0 = "jboss-aspect-library-jdk50.jar"; //$NON-NLS-1$
> {code}
> {code:title=as/tests/org.jboss.tools.as.test.core/src/org/jboss/tools/as/test/core/TestConstants.java}
> 45: public static final String JRE_5_HOME = System.getProperty("jbosstools.test.jre.5", "C:\\apps\\java\\jre5.0\\");
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24763:
------------------------------------
Deprecated job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... green too.
But I see a red ball for OSX, build #51, due to slave failure, so I've kicked it again using the Matrix Reloaded plugin:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> Some server itests are failing on Jenkins
> -----------------------------------------
>
> Key: JBIDE-24763
> URL: https://issues.jboss.org/browse/JBIDE-24763
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: server-itests.png
>
>
> Here's the job:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Currently we got around 30 failures:
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1
> org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1
> org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6
> org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6
> org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6
> org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6
> org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7
> {code}
> Nick already shared some details in JBIDE-22799
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24676:
---------------------------------------
To sum up again: There will be no fix on our part. The upstream fix in minishift/cdk is to display simple dots instead of fidget spinner - no special parameter.
CDK guys confirmed this was integrated into CDK and should be available in CDK nightly builds tomorrow (September 13, 2017).
So we should verify once more with CDK nightly builds and then close this JIRA.
> CDK3 server adapter's console view is using wrong coding on all platforms
> -------------------------------------------------------------------------
>
> Key: JBIDE-24676
> URL: https://issues.jboss.org/browse/JBIDE-24676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.5.0.AM2
> Environment: Windows, Linux, macOS
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: Console_output.png, cdk_console_coding.png, dot_spinner_error.png, no_progressbar.png, progress-win.PNG, progress.png
>
>
> Console view on all platforms show strange characters. See the pic.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months