[JBoss JIRA] (JBIDE-13854) intermittent install-grinder test failures caused by SIGSEGV
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13854?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13854:
------------------------------------
As noted in the JIRA description, the affected slave is dsp06-rhel5-x86_64, so it's running RHEL5. If it's a slave config problem, then I can fire an email at ci-issues@ and they can investigate.
> intermittent install-grinder test failures caused by SIGSEGV
> ------------------------------------------------------------
>
> Key: JBIDE-13854
> URL: https://issues.jboss.org/browse/JBIDE-13854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> When run on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dsp06-rhel5-x86..., this build failed:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%2Fdevstudio-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console}
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest
> Command-line arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product -data workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest -consoleLog -debug
> !ENTRY org.eclipse.osgi 2 1 2013-03-23 10:07:15.646
> !MESSAGE NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
> Testsuite: org.jboss.tools.tests.installation.InstallFromCentralTest
> Application Started: 24573
> log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher).
> log4j:WARN Please initialize the log4j system properly.
> !ENTRY org.eclipse.ui.browser 2 0 2013-03-23 10:07:23.217
> !MESSAGE Internal browser is not available: XPCOM error 0x80004003
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x0000003420c08b9b, pid=17450, tid=1076410688
> #
> # JRE version: 6.0_43-b01
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [ld-linux-x86-64.so.2+0x8b9b]
> #
> # An error report file with more information is saved as:
> # /qa/local/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/cdf6d04c/eclipse/hs_err_pid17450.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> {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
13 years
[JBoss JIRA] (JBIDE-13854) intermittent install-grinder test failures caused by SIGSEGV
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13854?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13854:
-------------------------------
Summary: intermittent install-grinder test failures caused by SIGSEGV (was: intermittent install-grinter test failures caused by SIGSEGV)
> intermittent install-grinder test failures caused by SIGSEGV
> ------------------------------------------------------------
>
> Key: JBIDE-13854
> URL: https://issues.jboss.org/browse/JBIDE-13854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> When run on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dsp06-rhel5-x86..., this build failed:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%2Fdevstudio-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console}
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest
> Command-line arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product -data workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest -consoleLog -debug
> !ENTRY org.eclipse.osgi 2 1 2013-03-23 10:07:15.646
> !MESSAGE NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
> Testsuite: org.jboss.tools.tests.installation.InstallFromCentralTest
> Application Started: 24573
> log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher).
> log4j:WARN Please initialize the log4j system properly.
> !ENTRY org.eclipse.ui.browser 2 0 2013-03-23 10:07:23.217
> !MESSAGE Internal browser is not available: XPCOM error 0x80004003
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x0000003420c08b9b, pid=17450, tid=1076410688
> #
> # JRE version: 6.0_43-b01
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [ld-linux-x86-64.so.2+0x8b9b]
> #
> # An error report file with more information is saved as:
> # /qa/local/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/cdf6d04c/eclipse/hs_err_pid17450.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> {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
13 years
[JBoss JIRA] (JBIDE-13742) Investigate how modernizr affects vjet/jsdt/etc.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13742?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-13742:
-----------------------------------------
VJET, NexJ, JSDT (all of them) complain to parse/calculate proposals on Modernizr.js.
VJET has an issue on parsing the Regular Expressions [Bug 401250: regular expression causes false comment color|https://bugs.eclipse.org/bugs/show_bug.cgi?id=401250] that prevents the JavaScript to be parsed correctly (Tested with both, full developer version and customized minified one on a little working test project). So, VJET cannot create a model of JS-objects for this script.
NexJ and JSDT both complain on minified version of Modernizr script, so they can't use it (the reason is the same as for jQuery Minifoed files - JSDT Parser). But also I couldn't make it parse and show me the content assist on Modernizr object and its members somwhere in the code outside the script itself. So, content assist shows the Modernizr object when I'm editing modernizr.js file itself, but the object is not-available when editing some HTML that includes modernizr.js or some other JS file.
Neither VJET nor NexJ has a type library support for the modernizr.js.
So, modernizr.js doesn't affect the content assistant.
> Investigate how modernizr affects vjet/jsdt/etc.
> ------------------------------------------------
>
> Key: JBIDE-13742
> URL: https://issues.jboss.org/browse/JBIDE-13742
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
>
> Check how javascript completion is affected by usage of modernizr.
> http://modernizr.com/docs/#load
> Can they still provide code completion for the library ?
--
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
13 years
[JBoss JIRA] (JBDS-2365) ESB projects cannot be deployed using Server Add/Remove
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ]
Len DiMaggio closed JBDS-2365.
------------------------------
This problem is not seen with:
Version: 6.0.1.GA
Build id: GA-v20130320-0407-B354
Build date: 20130320-0407
And tooling installed from:
http://download.jboss.org/jbosstools/updates/integration/juno/integration...
> ESB projects cannot be deployed using Server Add/Remove
> -------------------------------------------------------
>
> Key: JBDS-2365
> URL: https://issues.jboss.org/browse/JBDS-2365
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Jeremy Davis
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 6.0.0.CR1, 6.0.1.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years
[JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-13821:
-------------------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
back to you - shouldn't we get the branch cleaned up too or at least roll back to what was there previously ?
> CI runs tests against minimum instead of maximum
> ------------------------------------------------
>
> Key: JBIDE-13821
> URL: https://issues.jboss.org/browse/JBIDE-13821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.x, 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
> Maven order to set properties is
> # look a -D... to set property, if not found
> # look at active profiles to set property, if not found
> # look at default value of property to set it
> This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
> This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.
--
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
13 years
[JBoss JIRA] (JBIDE-13821) CI runs tests against minimum instead of maximum
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13821?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13821:
---------------------------------------------
Nick - those jobs referring to it would set the flag but the flag would have *zero* effect since the pom fixes were *not* listening to that property.
Looking in gitrepo master now seem to be sane, but 4.0.x branch still has the parent pom where nothing will listen to -DTARGET_PLATFORM-maximum; only TARGET_PLATFORM_MAXIMUM or tpc.version is honored.
so branch has this broken code still afaics.
> CI runs tests against minimum instead of maximum
> ------------------------------------------------
>
> Key: JBIDE-13821
> URL: https://issues.jboss.org/browse/JBIDE-13821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.x, 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
> Maven order to set properties is
> # look a -D... to set property, if not found
> # look at active profiles to set property, if not found
> # look at default value of property to set it
> This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
> This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.
--
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
13 years
[JBoss JIRA] (JBIDE-13854) intermittent install-grinter test failures caused by SIGSEGV
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13854?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13854:
---------------------------------------------
does this happen when running on older rhel machines ? the error seem to be missing/wrong xpcom libs.
> intermittent install-grinter test failures caused by SIGSEGV
> ------------------------------------------------------------
>
> Key: JBIDE-13854
> URL: https://issues.jboss.org/browse/JBIDE-13854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> When run on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dsp06-rhel5-x86..., this build failed:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%2Fdevstudio-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console}
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest
> Command-line arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product -data workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest -consoleLog -debug
> !ENTRY org.eclipse.osgi 2 1 2013-03-23 10:07:15.646
> !MESSAGE NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
> Testsuite: org.jboss.tools.tests.installation.InstallFromCentralTest
> Application Started: 24573
> log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher).
> log4j:WARN Please initialize the log4j system properly.
> !ENTRY org.eclipse.ui.browser 2 0 2013-03-23 10:07:23.217
> !MESSAGE Internal browser is not available: XPCOM error 0x80004003
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x0000003420c08b9b, pid=17450, tid=1076410688
> #
> # JRE version: 6.0_43-b01
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [ld-linux-x86-64.so.2+0x8b9b]
> #
> # An error report file with more information is saved as:
> # /qa/local/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/cdf6d04c/eclipse/hs_err_pid17450.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> {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
13 years
[JBoss JIRA] (JBIDE-13715) soa-p 5.3 is incorrectly detected as 5.2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13715?page=com.atlassian.jira.plugi... ]
Len DiMaggio closed JBIDE-13715.
--------------------------------
Verified in:
Version: 6.0.1.GA
Build id: GA-v20130320-0407-B354
Build date: 20130320-0407
See attached screenshot
> soa-p 5.3 is incorrectly detected as 5.2
> ----------------------------------------
>
> Key: JBIDE-13715
> URL: https://issues.jboss.org/browse/JBIDE-13715
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Labels: respin-a
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
> Attachments: 601_CR1a_Screenshot.png, Screenshot.png
>
>
> When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2.
> When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there.
--
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
13 years
[JBoss JIRA] (JBIDE-13715) soa-p 5.3 is incorrectly detected as 5.2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13715?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-13715:
---------------------------------
Attachment: 601_CR1a_Screenshot.png
> soa-p 5.3 is incorrectly detected as 5.2
> ----------------------------------------
>
> Key: JBIDE-13715
> URL: https://issues.jboss.org/browse/JBIDE-13715
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Labels: respin-a
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
> Attachments: 601_CR1a_Screenshot.png, Screenshot.png
>
>
> When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2.
> When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there.
--
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
13 years