[JBoss JIRA] (JBIDE-23674) Move org.jboss.tools.jsf.reddeer to jbosstools-javaee/jsf/test-framework
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23674?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23674:
------------------------------------
Looks like your latest commit [1] has caused a problem w/ source feature generation.
[1] https://github.com/jbosstools/jbosstools-javaee/commit/682bb1246112d9594b...
{code}
16:37:56 [WARNING] Mirror tool: Problems resolving provisioning plan.: [
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.batch.feature.feature.group [1.8.1.v20160823-0452].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.feature.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.seam.test.feature.feature.group [3.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.batch.test.feature.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.test.feature.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.jsf.test.feature.feature.group [3.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.runtime.seam.detector.feature.feature.group [3.8.2.v20161110-1300].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.test.feature.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.richfaces.feature.feature.group [3.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.test.feature.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.batch.feature.feature.group [1.8.2.v20161103-1552].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.test.feature.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.feature.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.test.feature.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.seam.feature.feature.group [3.8.1.v20160829-2307].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.jsf.feature.feature.group [3.8.1.v20160829-2307].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.batch.test.feature.feature.group [1.8.1.v20160615-1816].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.jsf.test.feature.feature.group [3.8.1.v20160901-0020].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.seam.test.feature.feature.group [3.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.richfaces.feature.feature.group [3.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.seam.feature.feature.group [3.8.2.v20161115-1308].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.feature.feature.group [1.8.2.v20161019-0001].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.test.feature.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.jsf.feature.feature.group [3.8.2.v20160921-1352].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.feature.feature.group [1.8.1.v20160823-0452].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.feature.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.runtime.seam.detector.feature.feature.group [3.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllFeatures 1.0.0.9RE9U9ccKlLE6FCpBe1PEEtPLA43H to org.jboss.tools.cdi.feature.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.seam.feature.source.feature.group [3.8.2.v20161115-1308].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.test.feature.source.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.jsf.test.feature.source.feature.group [3.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.feature.source.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.test.feature.source.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.feature.source.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.test.feature.source.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.jsf.feature.source.feature.group [3.8.2.v20160921-1352].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.jsf.test.feature.source.feature.group [3.8.1.v20160901-0020].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.seam.test.feature.source.feature.group [3.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.batch.test.feature.source.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.feature.source.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.richfaces.feature.source.feature.group [3.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.test.feature.source.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.feature.source.feature.group [1.8.1.v20160823-0452].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.feature.source.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.jsf.feature.source.feature.group [3.8.1.v20160829-2307].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.deltaspike.feature.source.feature.group [1.8.2.v20161019-0001].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.seam.feature.source.feature.group [3.8.1.v20160829-2307].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.runtime.seam.detector.feature.source.feature.group [3.8.2.v20161110-1300].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.richfaces.feature.source.feature.group [3.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.batch.feature.source.feature.group [1.8.2.v20161103-1552].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.seam.test.feature.source.feature.group [1.8.2.v20160913-1839].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.seam.test.feature.source.feature.group [3.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.runtime.seam.detector.feature.source.feature.group [3.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.batch.feature.source.feature.group [1.8.1.v20160823-0452].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.cdi.test.feature.source.feature.group [1.8.1.v20160607-2131].;
Unable to satisfy dependency from v20170126-1731.AllSources 1.0.0.9RE9U9ccKlXYUFCpBe1PEEtPLA43H to org.jboss.tools.batch.test.feature.source.feature.group [1.8.1.v20160615-1816].]{code}
-- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
To fix this, check your build.properties, plugin.properties, etc. as per this guide: https://wiki.eclipse.org/Minerva#Source
> Move org.jboss.tools.jsf.reddeer to jbosstools-javaee/jsf/test-framework
> ------------------------------------------------------------------------
>
> Key: JBIDE-23674
> URL: https://issues.jboss.org/browse/JBIDE-23674
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: integration-tests, jsf
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Fix For: 4.4.3.AM2
>
>
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
> https://github.com/jbosstools/jbosstools-javaee/tree/master/jsf
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-20426) JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20426?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20426:
-------------------------------------
https://github.com/jbosstools/jbosstools-server/pull/466
We will still get two threads trying to stop the server, potentially at different times. We had a check present to verify the 'shared process' (ie the process for the currently launched server) was identical to the one we're responding to terminating. However, this check was too early. It was possible for our check on the 'shared process' to return the old process for the server that was just terminated.
Meanwhile, in other threads, our poller has marked the server as stopped, and a new process has been launched. Then, our 'process terminated' listener tries to stop it again, without re-checking that the process is the same yet again.
I've traced through this extensively and tried a bunch of various paths in selectively progressing individual threads to see if it's possible to break, and my tests indicate the PR fixes the issue. What's more, if the 'process terminated' listener gets execution before the 2nd start of the server, it will prevent the 2nd start of the server until it finishes its checks. So that's safe.
If on the other hand the process terminated listener gets execution after the 2nd start of the server, the check that the processes are identical will fail, so no redundant (or broken) setServerStopped() call will be made.
This one feels good to fix.
> JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20426
> URL: https://issues.jboss.org/browse/JBIDE-20426
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: The Alchemist
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> This usually happens when I have a few big EARs attached, so I think the "checker" doesn't wait long enough to see if WF actually restarted.
> The result is this weird situation where the "Servers" view says that it's "Stopped", but the Console view has the red square to terminate the process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-20426) JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20426?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20426:
-------------------------------------
I can replicate this with enough breakpoints and custom control-flow. :(
Problem is we have 2 different pieces of logic setting server to stopped. One sets it to stopped (which triggers the next start), and the second sets it to stopped 'after' the 2nd start.
> JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20426
> URL: https://issues.jboss.org/browse/JBIDE-20426
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: The Alchemist
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> This usually happens when I have a few big EARs attached, so I think the "checker" doesn't wait long enough to see if WF actually restarted.
> The result is this weird situation where the "Servers" view says that it's "Stopped", but the Console view has the red square to terminate the process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23734) dedupe vpe unit test jobs / migrate vpe builds to CCI
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23734:
------------------------------------
For unit tests, we already run those as part of the builds, eg., in these jobs:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
All we need are PR check jobs (which run unit tests) and integration test jobs (which run integration tests). I don't think we need PR check jobs that run integration tests, as that will make PR checks really long.
By the way, I've started migrating jobs on Bos MW to CCI... they'll appear here:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
We could move your jobs into nested views too, if we want to contain all the devstudio stuff under a single top-level view (rather than the many views we have today). WDYT?
> dedupe vpe unit test jobs / migrate vpe builds to CCI
> -----------------------------------------------------
>
> Key: JBIDE-23734
> URL: https://issues.jboss.org/browse/JBIDE-23734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> There are four VPE unit test jobs. We probably only need 2 of those.
> These both run on multiple OSes:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> These probably run the same unit tests, but against master or 4.4.x branches, and are called from the VPE build jobs [1], [2] on Boston MW Jenkins (because the tests were failing to run in Boston):
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_4.4.neon/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-20426) JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20426?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20426:
-------------------------------------
I believe this can be fixed by using the "Process Terminated" shutdown poller. In fact, we may wish to make this one the default for all local server launches, because it is the best way to get the timing correct. I guess further investigation needs to be made.
> JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20426
> URL: https://issues.jboss.org/browse/JBIDE-20426
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: The Alchemist
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> This usually happens when I have a few big EARs attached, so I think the "checker" doesn't wait long enough to see if WF actually restarted.
> The result is this weird situation where the "Servers" view says that it's "Stopped", but the Console view has the red square to terminate the process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months