[jbosstools-issues] [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

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688276#comment-12688276 ] 

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/job/jbosstools-3.3_trunk.component--common/606/console
> https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--common/ws/sources/tests/org.jboss.tools.common.verification.test/target/work/data/.metadata/.log/*view*/
> {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 at 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