10:38 a.m.
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only junit
(not junit4).
--
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
12:31 p.m.
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10529:
------------------------------------
Switched to junit4 -- built fine locally w/ both junit and junit4. Spinning in Jenkins to
verify now:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
4:09 p.m.
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10529:
------------------------------------
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
-- running on RHEL5 instead of RHEL4 to see if that's relevant.
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
11:44 p.m.
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10529:
------------------------------------
Same problem on RHEL5 (builds 609, 610). More info on the error msg here:
http://jojovedder.blogspot.com/2009/04/comvladiumemmaemmaruntimeexception...
http://face.cs.drexel.edu/pipermail/cs576/2008-August/000193.html
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
8:17 p.m.
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-10529:
---------------------------------------
I cannot replicate that locally in my build environment which uses only target platform
update site and locally built common component. This problem seems to be related to
profiles enabled for common component hudson build. It looks like build instruments
classes build locally and then pickup something else from nightly staging update site.
Back to nick
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:26 p.m.
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-10529.
--------------------------------
Resolution: Cannot Reproduce Bug
Does not seem to still be happening (at least not consistently).
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:32 p.m.
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10529:
-------------------------------
Attachment: intermittent-coverage-problems.png
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
== blue
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... ==
blue... but then:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... == red:
{code}
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class
[org.jboss.tools.common.model.util.EclipseResourceUtil] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale metadata
is being used for report generation.{code}
then 1 test failed. then the above error, then 1 test failure again:
!intermittent-coverage-problems.png!
test failure in common.verification
-----------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:34 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10529:
-------------------------------
Summary: com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version
of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with
the version of this class in the metadata, possibly because stale metadata (was: test
failure in common.verification)
Rename issue. Still occurring, but intermittently.
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:36 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10529:
-------------------------------
Fix Version/s: 3.3.0.CR1
(was: 3.3.0.Beta1)
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:36 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10529:
-------------------------------
Comment: was deleted
(was: reopen. will track this a bit more.)
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:36 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10529:
-------------------------------
Comment: was deleted
(was: Rename issue. Still occurring, but intermittently.)
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:36 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10529:
-------------------------------
Comment: was deleted
(was: Does not seem to still be happening (at least not consistently).)
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
12:38 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10529 at 2/21/12 1:37 PM:
-------------------------------------------------------------
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
== blue
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... ==
blue... but then:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... == red:
{code}
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class
[org.jboss.tools.common.model.util.EclipseResourceUtil] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale metadata
is being used for report generation.{code}
then 1 test failed. then the above error, then 1 test failure again:
!intermittent-coverage-problems.png!
Does not seem to be happening consistently, but is happening. Maybe this is an NFS file
lock problem? Slow slaves?
was (Author: nickboldt):
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
== blue
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... ==
blue... but then:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... == red:
{code}
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class
[org.jboss.tools.common.model.util.EclipseResourceUtil] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale metadata
is being used for report generation.{code}
then 1 test failed. then the above error, then 1 test failure again:
!intermittent-coverage-problems.png!
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
6:05 p.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-10529:
---------------------------------------
problem is that at test execution time tycho pick ups different plugins from one of many
nightly/stable/composite/whatever p2 update sites we have. If you check
target/work/configuration/config.ini file for test with error from subject I am sure you
see where those plugins come from.
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
10:30 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10529:
------------------------------------
But...
a) the bits built in the workspace == the bits on the nightly site == the bits on the
composite site
b) Tycho will have JUST finished building the bits so why wouldn't it check ~/.m2
before trying to resolve against remote bits, even if they're the same ones?
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta2
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
2:18 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10529:
----------------------------------------
I can try, but it seems like this issue does not happen anymore. Couldn't we mark it
as "Can't reproduce" ?
The cause could be a concurrent access to M2_REPO or simply using local deps from M2_REPO
instead of nighlty. The only sustainable solution that could help in that case would be
usage of a private Maven repo in builds. It will require a lot of disk space! Do we have
enough?
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta3
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
10:07 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10529:
------------------------------------
All builds should be using private repos to prevent concurrent access to the same (shared)
.m2 repo, like this:
{code}-Dmaven.repo.local=${WORKSPACE}/m2-repository{code}
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta3
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
10:12 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10529:
----------------------------------------
Most jobs have the "build" maven run using private repo (as specified in
MAVEN_ARGS) *and* have the "Use private repo" option checked, whereas test
execution does not have the "use private repo" option checked.
So are we sure they use the same repo?
We should probably get rid of the argument in MAVEN_ARGS and check the "private
repository" option on all Maven executions.
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta3
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
4:19 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10529:
----------------------------------------
Looks like using private repos makes build much slower since the repo has to be updated on
almost each build (Each slave has a copy of $WORKSPACE and repo, these copies are not
sync'd, updates are performed on each build).
We need to find something that is shared (for performances) and isolated enough to prevent
from side-effects.
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta3
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
7:02 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Mickael Istria resolved JBIDE-10529.
------------------------------------
Resolution: Cannot Reproduce Bug
This did not happen for a while, it wasn't reproduced on any CI build for the last
month (as far as I can see).
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta3
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
9:30 a.m.
New subject: [JBoss JIRA] (JBIDE-10529) com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata
[
https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-10529.
------------------------------
Closing: nothing to QA here.
com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class [org.jboss.tools.common.util.****] in the coverage data is not
consistent with the version of this class in the metadata, possibly because stale
metadata
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10529
URL: https://issues.jboss.org/browse/JBIDE-10529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 3.3.0.Beta3
Attachments: intermittent-coverage-problems.png
After switching to newer target platform (JBIDE-10289), one test is failing:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
[INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]
!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are
not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle
initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/
was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.
{code}
Guessing the problem is that the test depends on junit4 but the manifest states only
junit (not junit4).
--
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
5088
days inactive
5221
days old
jbosstools-issues@lists.jboss.org
20 comments
6 participants
participants (6)
-
Denis Golovin (Commented) (JIRA) -
Denis Golovin (JIRA)
-
Mickael Istria (JIRA)
-
Nick Boldt (Commented) (JIRA)
-
Nick Boldt (Created) (JIRA)
-
Nick Boldt (JIRA)