[JBoss JIRA] (JBIDE-14977) JBoss Central tests fail
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14977?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14977:
---------------------------------------
There are several issues in the central tests:
1) ProxyWizardManagerTest.testLoadProxyWizardsFromRemote fails because the waitForDownload method runs in the UI thread.
Since the ProxyWizardUpdateJob job also uses the UI thread to notify listeners, we get a timeout error.
2) The cheat sheet test creates a cheatsheet
Because PROMPT is the default cheatsheet action, the test opens a dialog and freezes.
The PR fixes the issue.
> JBoss Central tests fail
> ------------------------
>
> Key: JBIDE-14977
> URL: https://issues.jboss.org/browse/JBIDE-14977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Central
> Affects Versions: 4.1.0.Beta2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.CR1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/82/testReport/org.jboss.tools.cdi.core.test/TypeTest/testType/}
> Failed
> org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManagerTest.testLoadProxyWizardsFromRemote
> Failing for the past 3 builds (Since Unstable#48 )
> Took 10 sec.
> add description
> Error Message
> Timeout while waiting for completion of job: Update project wizard list(34)
> Stacktrace
> java.lang.AssertionError: Timeout while waiting for completion of job: Update project wizard list(34)
> {code}
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-14977) JBoss Central tests fail
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14977?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-14977:
----------------------------------
Summary: JBoss Central tests fail (was: Invalid connectorDescriptor/@siteUrl / Timeout while waiting for completion of job: Update project wizard list(34) in org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManagerTest.testLoadProxyWizardsFromRemote)
> JBoss Central tests fail
> ------------------------
>
> Key: JBIDE-14977
> URL: https://issues.jboss.org/browse/JBIDE-14977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Central
> Affects Versions: 4.1.0.Beta2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.CR1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/82/testReport/org.jboss.tools.cdi.core.test/TypeTest/testType/}
> Failed
> org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManagerTest.testLoadProxyWizardsFromRemote
> Failing for the past 3 builds (Since Unstable#48 )
> Took 10 sec.
> add description
> Error Message
> Timeout while waiting for completion of job: Update project wizard list(34)
> Stacktrace
> java.lang.AssertionError: Timeout while waiting for completion of job: Update project wizard list(34)
> {code}
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15060) Eclipse Kepler running jboss eap takes a long time to run (open browser)
by Marcelo Sales (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15060?page=com.atlassian.jira.plugi... ]
Marcelo Sales resolved JBIDE-15060.
-----------------------------------
Release Notes Text: Sorry! It's my mistake. I've configured in eclipse the startup poller like timeout, so, the timeout of my server was configured with 450 seconds (7,5 minutes). I do not knew that this parameter make the server wait to timeout. Well, I've changed the startup poller to Web port then the problem is gone.
Fix Version/s: 4.1.0.Beta2
Resolution: Rejected
This is not a bug, it's just a configuration problem
> Eclipse Kepler running jboss eap takes a long time to run (open browser)
> ------------------------------------------------------------------------
>
> Key: JBIDE-15060
> URL: https://issues.jboss.org/browse/JBIDE-15060
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Environment: Windows 64 java 1.7.25 x86 eclipse kepler x86.
> Reporter: Marcelo Sales
> Labels: eclipse, jboss, jbossas, jbossas7, jbosseap, kepler
> Fix For: 4.1.0.Beta2
>
>
> When follow the path: project -> run as -> run on server and select jboss eap 6.1 the message "starting jboss..." in the right bottom corner of the eclipse takes a long time to hide and I can see in the logs that the project already has deployed. The problem is that for eclipse the server is still starting and the browser do not open with my application like it does with another jboss server like 7.1.1.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15060) Eclipse Kepler running jboss eap takes a long time to run (open browser)
by Marcelo Sales (JIRA)
Marcelo Sales created JBIDE-15060:
-------------------------------------
Summary: Eclipse Kepler running jboss eap takes a long time to run (open browser)
Key: JBIDE-15060
URL: https://issues.jboss.org/browse/JBIDE-15060
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.0.Beta2
Environment: Windows 64 java 1.7.25 x86 eclipse kepler x86.
Reporter: Marcelo Sales
When follow the path: project -> run as -> run on server and select jboss eap 6.1 the message "starting jboss..." in the right bottom corner of the eclipse takes a long time to hide and I can see in the logs that the project already has deployed. The problem is that for eclipse the server is still starting and the browser do not open with my application like it does with another jboss server like 7.1.1.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15059:
-------------------------------------
Description:
1. EXEC: launch OpenShift Application wizard
2. EXEC: create a new application and have it imported to your workspace
3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
!committed-changes-to-publish.png!
4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of origin by 1)
!is-ahead-1.png! (*wrong!* since we pushed)
5. EXEC: Pick your server adapter and tell it to publish to OpenShift
Result:
The adapter tells you that you that there are local commits that you may push. (*wrong!*)
!committed-changes-to-publish.png!
Expected:
We just pushed there cannot be local commits that were not pushed yet
6. EXEC: Confirm the dialog and tell it to publish
Result:
It tells you that OpenShift is already up-to-date (which is true!)
!already-up-to-date.png!
7. EXEC: pick Team->Fetch from Upstream
8 ASSERT:
The remote "is ahead of" state of the current branch compared to origin is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
!is-ahead-0.png!
If you now publish via adapter it'll tell you that there are no local changes that you can push.
was:
1. EXEC: launch OpenShift Application wizard
2. EXEC: create a new application and have it imported to your workspace
3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
!committed-changes-to-publish.png!
4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of remote by 1)
!is-ahead-1.png! (*wrong!* since we pushed)
5. EXEC: Pick your server adapter and tell it to publish to OpenShift
Result:
The adapter tells you that you that there are local commits that you may push. (*wrong!*)
!committed-changes-to-publish.png!
Expected:
We just pushed there cannot be local commits that were not pushed yet
6. EXEC: Confirm the dialog and tell it to publish
Result:
It tells you that OpenShift is already up-to-date (which is true!)
!already-up-to-date.png!
7. EXEC: pick Team->Fetch from Upstream
8 ASSERT:
The remote "is ahead of" state of the current branch compared to the remote repo is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
!is-ahead-0.png!
If you now publish via adapter it'll tell you that there are no local changes that you can push.
> Server adapter: tells me that there are local commits that I can publish even though there are none
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15059
> URL: https://issues.jboss.org/browse/JBIDE-15059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
> Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png
>
>
> 1. EXEC: launch OpenShift Application wizard
> 2. EXEC: create a new application and have it imported to your workspace
> 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
> !committed-changes-to-publish.png!
> 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of origin by 1)
> !is-ahead-1.png! (*wrong!* since we pushed)
> 5. EXEC: Pick your server adapter and tell it to publish to OpenShift
> Result:
> The adapter tells you that you that there are local commits that you may push. (*wrong!*)
> !committed-changes-to-publish.png!
> Expected:
> We just pushed there cannot be local commits that were not pushed yet
> 6. EXEC: Confirm the dialog and tell it to publish
> Result:
> It tells you that OpenShift is already up-to-date (which is true!)
> !already-up-to-date.png!
> 7. EXEC: pick Team->Fetch from Upstream
> 8 ASSERT:
> The remote "is ahead of" state of the current branch compared to origin is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
> !is-ahead-0.png!
> If you now publish via adapter it'll tell you that there are no local changes that you can push.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-15059:
----------------------------------------
Assignee: Andre Dietisheim (was: Denis Golovin)
> Server adapter: tells me that there are local commits that I can publish even though there are none
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15059
> URL: https://issues.jboss.org/browse/JBIDE-15059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
> Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png
>
>
> 1. EXEC: launch OpenShift Application wizard
> 2. EXEC: create a new application and have it imported to your workspace
> 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
> !committed-changes-to-publish.png!
> 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of remote by 1)
> !is-ahead-1.png! (*wrong!* since we pushed)
> 5. EXEC: Pick your server adapter and tell it to publish to OpenShift
> Result:
> The adapter tells you that you that there are local commits that you may push. (*wrong!*)
> !committed-changes-to-publish.png!
> Expected:
> We just pushed there cannot be local commits that were not pushed yet
> 6. EXEC: Confirm the dialog and tell it to publish
> Result:
> It tells you that OpenShift is already up-to-date (which is true!)
> !already-up-to-date.png!
> 7. EXEC: pick Team->Fetch from Upstream
> 8 ASSERT:
> The remote "is ahead of" state of the current branch compared to the remote repo is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
> !is-ahead-0.png!
> If you now publish via adapter it'll tell you that there are no local changes that you can push.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15059:
------------------------------------------
pushed patch for jbosstools-4.1.x upstream
> Server adapter: tells me that there are local commits that I can publish even though there are none
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15059
> URL: https://issues.jboss.org/browse/JBIDE-15059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
> Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png
>
>
> 1. EXEC: launch OpenShift Application wizard
> 2. EXEC: create a new application and have it imported to your workspace
> 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
> !committed-changes-to-publish.png!
> 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of remote by 1)
> !is-ahead-1.png! (*wrong!* since we pushed)
> 5. EXEC: Pick your server adapter and tell it to publish to OpenShift
> Result:
> The adapter tells you that you that there are local commits that you may push. (*wrong!*)
> !committed-changes-to-publish.png!
> Expected:
> We just pushed there cannot be local commits that were not pushed yet
> 6. EXEC: Confirm the dialog and tell it to publish
> Result:
> It tells you that OpenShift is already up-to-date (which is true!)
> !already-up-to-date.png!
> 7. EXEC: pick Team->Fetch from Upstream
> 8 ASSERT:
> The remote "is ahead of" state of the current branch compared to the remote repo is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
> !is-ahead-0.png!
> If you now publish via adapter it'll tell you that there are no local changes that you can push.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15059:
------------------------------------------
[~dgolovin] just review my patch:
{quote}
02:49:59 AM) dgolovin: adietisheim: you forgot to remove extra "push yet." in doc comment, everything else looks good to me
(02:50:25 AM) adietisheim: dgolovin: ok thanks
{quote}
> Server adapter: tells me that there are local commits that I can publish even though there are none
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15059
> URL: https://issues.jboss.org/browse/JBIDE-15059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Denis Golovin
> Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
> Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png
>
>
> 1. EXEC: launch OpenShift Application wizard
> 2. EXEC: create a new application and have it imported to your workspace
> 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
> !committed-changes-to-publish.png!
> 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of remote by 1)
> !is-ahead-1.png! (*wrong!* since we pushed)
> 5. EXEC: Pick your server adapter and tell it to publish to OpenShift
> Result:
> The adapter tells you that you that there are local commits that you may push. (*wrong!*)
> !committed-changes-to-publish.png!
> Expected:
> We just pushed there cannot be local commits that were not pushed yet
> 6. EXEC: Confirm the dialog and tell it to publish
> Result:
> It tells you that OpenShift is already up-to-date (which is true!)
> !already-up-to-date.png!
> 7. EXEC: pick Team->Fetch from Upstream
> 8 ASSERT:
> The remote "is ahead of" state of the current branch compared to the remote repo is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
> !is-ahead-0.png!
> If you now publish via adapter it'll tell you that there are no local changes that you can push.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-15059:
----------------------------------------
Assignee: Denis Golovin (was: Max Rydahl Andersen)
> Server adapter: tells me that there are local commits that I can publish even though there are none
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15059
> URL: https://issues.jboss.org/browse/JBIDE-15059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Denis Golovin
> Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
> Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png
>
>
> 1. EXEC: launch OpenShift Application wizard
> 2. EXEC: create a new application and have it imported to your workspace
> 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
> !committed-changes-to-publish.png!
> 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of remote by 1)
> !is-ahead-1.png! (*wrong!* since we pushed)
> 5. EXEC: Pick your server adapter and tell it to publish to OpenShift
> Result:
> The adapter tells you that you that there are local commits that you may push. (*wrong!*)
> !committed-changes-to-publish.png!
> Expected:
> We just pushed there cannot be local commits that were not pushed yet
> 6. EXEC: Confirm the dialog and tell it to publish
> Result:
> It tells you that OpenShift is already up-to-date (which is true!)
> !already-up-to-date.png!
> 7. EXEC: pick Team->Fetch from Upstream
> 8 ASSERT:
> The remote "is ahead of" state of the current branch compared to the remote repo is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed).
> !is-ahead-0.png!
> If you now publish via adapter it'll tell you that there are no local changes that you can push.
--
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
10 years, 10 months