[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17207:
----------------------------------------
The reason of the failure on Mac was identified and fixed on a few slaves. I've opened another ticket to get that propagated to all macosx slaves: https://engineering.redhat.com/rt/Ticket/Display.html?id=319509
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 4.2.x
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3057:
-------------------------------------------
not blocking release - we should though identify why we or others are blocking the UI thread for that long.
> JBDS causes "not responding" message on RHEL
> --------------------------------------------
>
> Key: JBDS-3057
> URL: https://issues.jboss.org/browse/JBDS-3057
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 7.1.1.GA
> Environment: RHEL 7 Beta
> OpenJDK 1.7
> JBDS 7.1.1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Labels: f2f2014
> Fix For: 8.0.x, 9.x
>
> Attachments: jbds-not-responding.png
>
>
> I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait.
> Obviously this is due to some limit that is set in the OS and when reached, this popup is shown.
> On subsequent starts of JBDS with the same workspace, this does not happen.
> The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow.
> I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3057:
--------------------------------------
Fix Version/s: 9.x
8.0.x
(was: 8.0.0.GA)
> JBDS causes "not responding" message on RHEL
> --------------------------------------------
>
> Key: JBDS-3057
> URL: https://issues.jboss.org/browse/JBDS-3057
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 7.1.1.GA
> Environment: RHEL 7 Beta
> OpenJDK 1.7
> JBDS 7.1.1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Labels: f2f2014
> Fix For: 8.0.x, 9.x
>
> Attachments: jbds-not-responding.png
>
>
> I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait.
> Obviously this is due to some limit that is set in the OS and when reached, this popup is shown.
> On subsequent starts of JBDS with the same workspace, this does not happen.
> The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow.
> I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18457:
-------------------------------------
Without a full support matrix or version range for java vs runtime, there's not much I can do to warn the user because my tools have no way of knowing the wrong java is being used. So for this bug i'll just be sorting the available compatible jre's and choosing the one closest to the exec-env.
> EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18457
> URL: https://issues.jboss.org/browse/JBIDE-18457
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac.
> 1. Start JBDS 8.0.0.CR1
> 2. Download EAP 6.1 via runtime detection
> 3. Start the server
> In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed:
> {code}
> 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
> 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
> {code}
> And with this the status bar changed to 100 % and the progress view shows:
> Preparing launch deletage.
> It's been like this at least 5 minutes now. The server is not started.
> I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start.
> ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection.
> In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter.
> Right now I haven't tried other server versions.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3057:
--------------------------------------
Labels: f2f2014 (was: )
> JBDS causes "not responding" message on RHEL
> --------------------------------------------
>
> Key: JBDS-3057
> URL: https://issues.jboss.org/browse/JBDS-3057
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 7.1.1.GA
> Environment: RHEL 7 Beta
> OpenJDK 1.7
> JBDS 7.1.1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Labels: f2f2014
> Fix For: 8.0.0.GA
>
> Attachments: jbds-not-responding.png
>
>
> I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait.
> Obviously this is due to some limit that is set in the OS and when reached, this popup is shown.
> On subsequent starts of JBDS with the same workspace, this does not happen.
> The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow.
> I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18457:
--------------------------------
Summary: EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable (was: EAP 6.1 fails to start on Windows 7 - need to warn users if they use wrong java)
> EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18457
> URL: https://issues.jboss.org/browse/JBIDE-18457
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac.
> 1. Start JBDS 8.0.0.CR1
> 2. Download EAP 6.1 via runtime detection
> 3. Start the server
> In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed:
> {code}
> 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
> 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
> {code}
> And with this the status bar changed to 100 % and the progress view shows:
> Preparing launch deletage.
> It's been like this at least 5 minutes now. The server is not started.
> I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start.
> ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection.
> In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter.
> Right now I haven't tried other server versions.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18527) "rm -rf project" in Forge Console doesn't delete project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18527?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18527:
---------------------------------------------
Same would happen if you delete other apps essential files from command line or similar thus I'm not considering this blocking CR2/GA.
Forge should though be able to notify eclipse and even warn the user that he is about delete projects loaded in eclipse.
> "rm -rf project" in Forge Console doesn't delete project
> --------------------------------------------------------
>
> Key: JBIDE-18527
> URL: https://issues.jboss.org/browse/JBIDE-18527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system.
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:951)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:897)
> at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1705)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refreshResource(CommandLineListener.java:315)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refresh(CommandLineListener.java:129)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.access$2(CommandLineListener.java:126)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener$1.run(CommandLineListener.java:86)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Contains: The project description file (.project) for 'jboss-as-kitchensink-html5-mobile' is missing. This file contains important information about the project. The project will not function properly until this file is restored.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18527) "rm -rf project" in Forge Console doesn't delete project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18527?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18527:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> "rm -rf project" in Forge Console doesn't delete project
> --------------------------------------------------------
>
> Key: JBIDE-18527
> URL: https://issues.jboss.org/browse/JBIDE-18527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system.
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:951)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:897)
> at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1705)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refreshResource(CommandLineListener.java:315)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refresh(CommandLineListener.java:129)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.access$2(CommandLineListener.java:126)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener$1.run(CommandLineListener.java:86)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Contains: The project description file (.project) for 'jboss-as-kitchensink-html5-mobile' is missing. This file contains important information about the project. The project will not function properly until this file is restored.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months