[JBoss JIRA] (JBIDE-24675) install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24675:
----------------------------------
Summary: install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
Key: JBIDE-24675
URL: https://issues.jboss.org/browse/JBIDE-24675
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: install-tests
Affects Versions: 4.5.0.AM2
Reporter: Nick Boldt
{code}
15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0040f (Add Reposi)
15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
15:51:38 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
15:51:38 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
15:51:56 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0008e (workspace )
15:51:56 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
15:52:02 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.816 sec
15:52:02
15:52:02 Testcase: testInstall took 26.254 sec
15:52:02 Caused an ERROR
15:52:02 Internal error
15:52:02 java.lang.RuntimeException: Internal error
15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:213)
15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:147)
15:52:02 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:133)
15:52:02 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78)
15:52:02 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47)
15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBothttps://dev-platform-jenkins.rh...
15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60)
15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120)
15:52:02 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73)
15:52:02 at java.lang.Thread.run(Thread.java:748)
15:52:02 Caused by: org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Installing Software'
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:472)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntilWidgetAppears(SWTWorkbenchBot.java:1)
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shells(SWTBotFactory.java:116)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shells(SWTWorkbenchBot.java:1)
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:106)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:97)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:156)
15:52:02 Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find shell matching: with text 'Installing Software'
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:522)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:496)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:484)
15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:466){code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-19604.
------------------------------
Verified in Devstudio 11.0.0.AM2-v20170713-2124-B489
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Labels: openshift_v2, openshift_v3
> Fix For: 4.5.0.AM2
>
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24664) Server adapter: unusable if oc is not on the path
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24664?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-24664.
------------------------------
Verified in Devstudio 11.0.0.AM2-v20170713-2124-B489
> Server adapter: unusable if oc is not on the path
> -------------------------------------------------
>
> Key: JBIDE-24664
> URL: https://issues.jboss.org/browse/JBIDE-24664
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Rob Stryker
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.AM2
>
>
> The openshift rest client lib is not including the full path when calling ProcessBuilder. So process builder is being asked to run a command named "oc" without the full path to it. In such situation, the process builder (or the OS, not 100% sure which) will revert to searching the system path for the given command, and choose the one on the system path.
> Since my machine does not have 'oc' on the system path, openshift tools cannot run the oc command, or publish.
> This also blocks adoption of JBIDE-24236, which allows users to select different OC. On linux, the system path's OC will *always* be chosen, regardless of any user settings.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24674) update the list of nag emails to send on QE stage day
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24674:
----------------------------------
Summary: update the list of nag emails to send on QE stage day
Key: JBIDE-24674
URL: https://issues.jboss.org/browse/JBIDE-24674
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.5.0.AM2
Reporter: Nick Boldt
We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them.
We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint.
And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months