[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11360: ------------------------------------ Still failing in http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... -- 16 builds w/ failed tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- I was unable to build vpe component and its tests with maven3. I've got {code} [ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: URI has an authority component -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: URI has an authority component at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- Thanks, Nick, I'll try three slashes. I used instructions from [How to Build JBoss Tools with Maven 3|https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3] for Linux system: {code} -Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ {code} I guess file:/// (3 slashes) should be mentioned there as well. P.S. BUILD SUCCESS, tests are passed locally, (207 tests summary): {code} ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.vpe.docbook.test.DocbookAllTests Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.173 sec Results : Tests run: 8, Failures: 0, Errors: 0, Skipped: 0 ------------------------------------------------------- Running org.jboss.tools.vpe.ui.test.VpeAllTests Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.309 sec Results : Tests run: 14, Failures: 0, Errors: 0, Skipped: 0 ------------------------------------------------------- Running org.jboss.tools.vpe.html.test.HtmlAllTests Tests run: 116, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.663 sec Results : Tests run: 116, Failures: 0, Errors: 0, Skipped: 0 ------------------------------------------------------- Running org.jboss.tools.vpe.spring.test.SpringAllTests Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.439 sec Results : Tests run: 27, Failures: 0, Errors: 0, Skipped: 0 ------------------------------------------------------- Running org.jboss.tools.vpe.jsp.test.JSPAllTests Create JSPDoBodyTemplate Create JSPDoBodyTemplate Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.718 sec Results : Tests run: 24, Failures: 0, Errors: 0, Skipped: 0 ------------------------------------------------------- Running org.jboss.tools.vpe.test.VpeAllTests Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.627 sec Results : Tests run: 11, Failures: 0, Errors: 0, Skipped: 0 ------------------------------------------------------- Running org.jboss.tools.vpe.xulrunner.test.XulRunnerAllTests Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.085 sec Results : Tests run: 7, Failures: 0, Errors: 0, Skipped: 0 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- The log file for vpe tests is attached. I've run tests for VPE component only with the command: {code} mvn3 clean install -U -B -fae -e -P local.site,vpe-bootstrap -Dlocal.site=file:///${HOME}/Projects/jboss_trunk/build/target-platform/REPO/ -Dmaven.test.skip=false | tee build.vpe_tests_20120326.log.txt {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11360 at 3/26/12 10:47 AM: -------------------------------------------------------------- @Denis: I've updated the doc to reflect the file:/// requirement. Thanks for finding & reporting the problem! https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#comment-9544 Last VPE build in trunk shows only 17 failures (down from 44), but those failures have been happening for 29 builds: {code:title=https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--vpe/896/testReport/} All Failed Tests Test Name Duration Age Could it be a RHEL6 problem? If you move your ~/.m2 repo folder to another location and start the build again, does everything still work? (I wonder if something is cached in ~/.m2 which makes it work locally but in Jenkins, where we start w/ a clean ~/.m2 every time, it does not.) was (Author: nickboldt): @Denis: I've updated the doc to reflect the file:/// requirement. Thanks for finding & reporting the problem! https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#comment-9544 Last VPE build in trunk shows only 17 failures (down from 44), but those failures have been happening for 29 builds: {code:title=https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--vpe/896/testReport/} All Failed Tests Test Name Duration Age Could it be a RHEL6 problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- 1) I removed folder ~/.m2, created the new one. 2) I started vpe-bootstrap build with tests enabled from *vpe* plugin folder: {code} cd jboss_trunk/vpe mvn3 clean install -U -B -fae -e -P local.site,vpe-bootstrap -Dlocal.site=file:///${HOME}/Projects/jboss_trunk/build/target-platform/REPO/ -Dmaven.test.skip=false | tee build.vpe_tests_20120327_clean_m2.log.txt {code} Build failed with the following [message|^build.vpe_tests_20120327_clean_m2.log.txt]: {code} ... Downloading: https://repository.sonatype.org/content/groups/sonatype-public-grid/org/e... Downloaded: https://repository.sonatype.org/content/groups/sonatype-public-grid/org/e... (11 KB at 8.9 KB/sec) [INFO] Computing target platform for MavenProject: org.jboss.tools.vpe.plugins:org.jboss.tools.vpe:3.3.0-SNAPSHOT @ /home/dmaliarevich/Projects/jboss_trunk/vpe/plugins/org.jboss.tools.vpe/pom.xml [INFO] Adding repository file:////home/dmaliarevich/Projects/jboss_trunk/build/target-platform/REPO/ [INFO] Adding repository file:////home/dmaliarevich/Projects/jboss_trunk/build/target-platform/REPO/ [INFO] Resolving dependencies of MavenProject: org.jboss.tools.vpe.plugins:org.jboss.tools.vpe:3.3.0-SNAPSHOT @ /home/dmaliarevich/Projects/jboss_trunk/vpe/plugins/org.jboss.tools.vpe/pom.xml [INFO] Cannot complete the request. Generating details. [INFO] Cannot complete the request. Generating details. [INFO] {org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1, osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true, org.osgi.framework.system.packages=} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.vpe 3.3.0.qualifier [ERROR] Missing requirement: org.jboss.tools.vpe 3.3.0.qualifier requires 'bundle org.jboss.tools.common.el.core 0.0.0' but it could not be found [ERROR] [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.jsp 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.el.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.el.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web.kb 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.model.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.css 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.model.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.resref.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.resref.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.el.core 2.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.xulrunner 3.3.0.qualifier to bundle org.jboss.tools.common 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.jsp 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.el.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.el.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web.kb 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.model.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.css 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.model.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.resref.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.resref.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.el.core 2.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.xulrunner 3.3.0.qualifier to bundle org.jboss.tools.common 0.0.0.", "No solution found because the problem is unsatisfiable."] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.jsp 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.el.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.el.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.web.kb 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.common.model.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe 3.3.0.qualifier to bundle org.jboss.tools.jst.css 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.model.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.jst.web 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.resref.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.resref.ui 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.resref 3.3.0.qualifier to bundle org.jboss.tools.common.el.core 2.0.0.", "Unable to satisfy dependency from org.jboss.tools.vpe.xulrunner 3.3.0.qualifier to bundle org.jboss.tools.common 0.0.0.", "No solution found because the problem is unsatisfiable."] at org.eclipse.tycho.p2.impl.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:79) at org.eclipse.tycho.p2.impl.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:83) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:118) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:76) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:445) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:422) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:98) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:61) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. {code} 3) Then I removed folder ~/.m2, created the new one once again. 4) I started vpe-bootstrap build with tests enabled from *build* folder: {code} cd jboss_trunk/build mvn3 clean install -U -B -fae -e -P local.site,vpe-bootstrap -Dlocal.site=file:///${HOME}/Projects/jboss_trunk/build/target-platform/REPO/ -Dmaven.test.skip=false | tee build.vpe_20120327_build_tests_clean_m2.log.txt {code} Build failed with the following [message|^build.vpe_20120327_build_tests_clean_m2.log.txt]: {code} ... Downloading: https://repository.sonatype.org/content/groups/sonatype-public-grid/org/e... Downloaded: https://repository.sonatype.org/content/groups/sonatype-public-grid/org/e... (11 KB at 9.2 KB/sec) [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.NullPointerException at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:185) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:316) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:96) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:158) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:140) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:76) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:56) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. {code} 5) I removed folder ~/.m2, created the new one once again. 6) I started vpe-bootstrap build from *build* folder but without running tests at this time. See [log|^build.vpe_20120327_build_only_clean_m2.log.txt] Build was successful. 7) After everything was built I started vpe-bootstrap with tests enabled from *build* folder. See [log|^build.vpe_20120327_tests_after_build.log.txt] I've got FAILURE only for org.jboss.tools.vpe.ui.test due to JVM crash. (I think it's my local environment problem) 8) The same thing but from *vpe* folder: [log|^build.vpe_tests_20120327_after_build.log.txt] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich edited comment on JBIDE-11360 at 3/27/12 8:11 AM: -------------------------------------------------------------------- So to sum up: * when I started a build with tests enabled on clean ~/.m2 -- build failed. * The separate build plus tests after that -- worked, i.e. ** First build vpe-bootstrap without running tests -- build success ** Then run vpe-bootstrap tests -- build success was (Author: dmaliarevich): So to sum up: * when I started a build with tests enabled on clean ~/.m2 -- build failed. * The separate build plus tests after that -- worked, i.e. ** First build vpe-bootstrap -- build success ** Then run vpe-bootstrap tests -- build success -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich edited comment on JBIDE-11360 at 3/27/12 8:14 AM: -------------------------------------------------------------------- So to sum up: * when I started a build with tests enabled on clean ~/.m2 -- build failed. * The separate build plus tests after that -- worked, i.e. ** First build vpe-bootstrap without running tests -- build success ** Then run vpe tests -- build success P.S. Yesterday I did the separate build first, and separate tests after that. was (Author: dmaliarevich): So to sum up: * when I started a build with tests enabled on clean ~/.m2 -- build failed. * The separate build plus tests after that -- worked, i.e. ** First build vpe-bootstrap without running tests -- build success ** Then run vpe-bootstrap tests -- build success -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11360: ------------------------------------ Can you look at that folder & into the related .log file(s) for more details? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- In [surefire-reports|^org.jboss.tools.vpe.ui.test.VpeAllTests.txt] there is a test failure for vpe scrolling test. That's because the IDE had no focus and the page had not been scrolled to its end. I've increased memory size for maven needs by the command {code} export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m" {code} Now I'll run vpe tests for a couple of times to check if there are any falures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich updated JBIDE-11360: -------------------------------------- Attachment: vpe_wtests.log.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich updated JBIDE-11360: -------------------------------------- Attachment: org.jboss.tools.vpe.docbook.test.DocbookAllTests.txt vpe_wtests2.log.txt hs_err_pid11732.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich updated JBIDE-11360: -------------------------------------- Attachment: build.vpe_with_tests.log.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11360: ------------------------------------ when there's no surefire-reports, it means the test crashed before anything could be logged. Usually means there's an eclipse .log folder, eg., in a given plugin's target/work/.metadata/.log file (if I recall correctly). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich updated JBIDE-11360: -------------------------------------- Attachment: build.vpe_with_tests2.log.txt org.jboss.tools.jst.web.kb.test.JstWebKbAllTests.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich updated JBIDE-11360: -------------------------------------- Attachment: build.vpe_with_tests3.log.txt org.jboss.tools.jst.web.kb.test.JstWebKbAllTests3.txt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- All tests on Jenkins are failed due to NPE in {code}org.jboss.tools.vpe.base.test.VpeTest.getSourceDocument(VpeTest.java:182){code} I've added some assertion checks to distinguish what variable is null. My guess is that some dependencies are not built -- thus test plugins are not executed. According to Jenkins test results only 2 test plugins are executed more or less normal(without dependencies errors): * org.jboss.tools.vpe.docbook.test * org.jboss.tools.vpe.xulrunner.test Other plugins have more Require-Bundles, and very likely it is RHEL6 build problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich edited comment on JBIDE-11360 at 3/29/12 3:08 AM: -------------------------------------------------------------------- Jenkis failures details: 1) In org.jboss.tools.vpe.xulrunner.test.XulRunnerAllTests.testGetInterfaceId the cause is org.eclipse.ui.internal.ErrorViewPart cannot be cast to org.jboss.tools.vpe.xulrunner.view.XulRunnerView 2) In SpringAllTests and DocbookAllTests -- mostly VpeSourceDomBuilder is null. 3) In XulRunnerAllTests and JSPAllTests and VpeAllTests -- mostly java.lang.ClassFormatError: Invalid length 65532 in LocalVariableTable in class file org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser etc. And thus in org.jboss.tools.vpe.test.VpeAllTests.initializationError the cause is java.lang.NoClassDefFoundError: org/jboss/tools/vpe/editor/template/VpeTemplate Also it says "The activator org.jboss.tools.vpe.VpePlugin for bundle org.jboss.tools.vpe is invalid", Root exception: java.lang.ClassFormatError: Invalid length 65532 in LocalVariableTable in class file org/jboss/tools/vpe/VpePlugin was (Author: dmaliarevich): Jenkis failures details: 1) In org.jboss.tools.vpe.xulrunner.test.XulRunnerAllTests.testGetInterfaceId the cause is org.eclipse.ui.internal.ErrorViewPart cannot be cast to org.jboss.tools.vpe.xulrunner.view.XulRunnerView 2) In SpringAllTests and DocbookAllTests -- mostly VpeSourceDomBuilder is null. 3) In XulRunnerAllTests and JSPAllTests and VpeAllTests -- mostly java.lang.ClassFormatError: Invalid length 65532 in LocalVariableTable in class file org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser etc. And thus in org.jboss.tools.vpe.test.VpeAllTests.initializationError the cause is java.lang.NoClassDefFoundError: org/jboss/tools/vpe/editor/template/VpeTemplate -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- Googling gave me the following results about java.lang.ClassFormatError: * [Code Coverage causes:Invalid length 65528 in LocalVariableTable|http://jenkins.361315.n4.nabble.com/Code-Coverage-caus...] It could be Cobertura or Emma code coverage tools integrated to maven * it could be a combintaion of [eclemma and jacoco|https://community.jboss.org/message/631380]: ??"The problem was the eclemma plugin which instrumented the files twice after jacoco has instrumented it."?? * Recent EclEmma issues [#1|http://sourceforge.net/tracker/index.php?func=detail&aid=3487174&group_id=177969&atid=883351] and [#2|http://sourceforge.net/tracker/?func=detail&atid=883351&aid=3486469&group_id=177969] and in general the cause of [java.lang.ClassFormatError|http://docs.oracle.com/javase/1.4.2/docs/guide...]: ??"This error is caused by bytecodes generated from old JDK 1.0.2/1.1 compilers, or from a third-party obfuscator. In the past, many of these compilers and obfuscators generated bytecode that does not conform to the Java VM Specification. Because the verifiers in recent J2SE releases are much stricter about bad class format, the ClassFormatError is thrown by the VM when these bad class files are loaded."?? So Nick, are there any code coverage jobs on Jenkins or other obfuscators that could "damage" class files? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich edited comment on JBIDE-11360 at 3/29/12 3:47 AM: -------------------------------------------------------------------- Nick, could changes in JBIDE-10537 on 02/Mar/12 be the problem? As I see jsf component has similar [problems|http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_...] was (Author: dmaliarevich): Nick, could changes in JBIDE-10537 on 02/Mar/12 be the problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich updated JBIDE-11360: -------------------------------------- Summary: A lot of test failures in VPE and JSF components (failing for a long time) (was: 44 test failures in VPE (failing for over 11 builds)) Description: [component--jsf, build #809, testReport|http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudi...] [component--vpe, build #905, testReport|http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudi...] was: {code:title=https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--vpe/878/testReport/} All Failed Tests Test Name Duration Age {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich commented on JBIDE-11360: ------------------------------------------- Description was updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11360: ---------------------------------------- Denis, the move from emma.filter to coverage.filter was just a renaming, if I did it well, it was an overall replacement of emma.filter by coverage.filter in all poms. I don't know how this could be an issue, bat that's an interesting entry point to investigate. Combination of Emma and Jacoco could be a valid reason. But I don't understand why it would work for some other projects? Maybe coverage is simply disabled for them... I should try to reproduce it locally, and see whether I can easily see it failing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11360: ---------------------------------------- What does happen locally when you start build with the same options that with Jenkins (mainly including emma coverage) ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11360: ------------------------------------ Try adding the "coverage" profile. See parent pom for details on what it does/how it's configured. mvn clean install ... -Pcoverage,local.site,... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Denis Maliarevich edited comment on JBIDE-11360 at 4/3/12 6:11 AM: ------------------------------------------------------------------- There is a "coverage" profile, but how can I specify to process only VPE and JSF plugins? I suppose otherwise ALL the plugins will be covered. I'm not familiar with *coverage* settings, so I need direct instructions. And as I see, vpe-bootstrap lies in /build/pom.xml, but the coverage -- in /build/parent/pom.xml, thus I should run coverage first, and only after that -- vpe/jsf-bootstrap. was (Author: dmaliarevich): There is a "coverage" profile, but how can I specify to process only VPE and JSF plugins? I suppose otherwise ALL the plugins will be covered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11360: ---------------------------------------- Jacoco was disabled as suggested by Denis Golovin (on mailing-list). Please retry now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11360?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-11360. ------------------------------------ Resolution: Done Jacoco was disabled, everything is working fine. We can conclude the Jacoco/Emma conflict is the cause of all troubles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira