[JBoss JIRA] (JBTIS-728) Fix 'DataTransformationDeploymentEAPTest'
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-728?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-728.
-----------------------------------
pushed to master
> Fix 'DataTransformationDeploymentEAPTest'
> -----------------------------------------
>
> Key: JBTIS-728
> URL: https://issues.jboss.org/browse/JBTIS-728
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE
> Affects Versions: 4.3.0.Final
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Fix For: 4.3.0.Final
>
>
> (/)
> {code}
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: at least one project is loaded
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37)
> at org.jboss.reddeer.eclipse.ui.wizards.datatransfer.WizardProjectsImportPage.setPath(WizardProjectsImportPage.java:154)
> at org.jboss.reddeer.eclipse.ui.wizards.datatransfer.WizardProjectsImportPage.setRootDirectory(WizardProjectsImportPage.java:62)
> at org.jboss.tools.fuse.ui.bot.test.utils.ProjectFactory.importExistingProject(ProjectFactory.java:155)
> at org.jboss.tools.fuse.ui.bot.test.DataTransformationDeploymentEAPTest.testDeployment(DataTransformationDeploymentEAPTest.java:72)
> {code}
> on Mac only:
> (/)
> {code}
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 300 s.: server's state is: Started
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37)
> at org.jboss.reddeer.eclipse.wst.server.ui.view.Server.operateServerState(Server.java:304)
> at org.jboss.reddeer.eclipse.wst.server.ui.view.Server.start(Server.java:159)
> at org.jboss.tools.runtime.reddeer.ServerBase.setState(ServerBase.java:97)
> at org.jboss.tools.runtime.reddeer.requirement.ServerRequirement.fulfill(ServerRequirement.java:98)
> at org.jboss.reddeer.junit.internal.requirement.Requirements.fulfill(Requirements.java:95)
> at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:34)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
by Nikoleta Žiaková (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ]
Nikoleta Žiaková commented on JBIDE-22436:
------------------------------------------
JBDS 9.1.0.GA from Customer Portal.
> Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22436
> URL: https://issues.jboss.org/browse/JBIDE-22436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Michal Jurc
> Assignee: Snjezana Peco
> Fix For: 4.4.x
>
> Attachments: helloworld-cheatsheet.xml, JBIDE-22436-9.1-helloworld.log, kitchensink-cheatsheet.xml, org.jboss.tools.cheatsheet.test.zip
>
>
> After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message:
> {quote}An error has occurred. See error log for more details.
> java.lang.NullPointerException{quote}
> The detailed error log produces the same message.
> The quickstarts and their cheat sheets work even after the prompt with NullPointerException message.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3924:
---------------------------------
No default assignee so ccing [~akazakov] to make sure this finds the correct owner.
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Environment: Fedora 23
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> Reporter: Misha Ali
> Attachments: devstudio10install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Misha Ali (JIRA)
Misha Ali created JBDS-3924:
-------------------------------
Summary: Installation looks incomplete but is actually completed
Key: JBDS-3924
URL: https://issues.jboss.org/browse/JBDS-3924
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Environment: Fedora 23
Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
Reporter: Misha Ali
Attachments: devstudio10install.png
Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months