Re: [linuxtools-dev] Java exists on test run

[Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx>]

I was able to access this log now too thanks to whoever fixed jenkins.

So its tried to load wrong arch for hamrest? Why linuxtools having this issue? We use mockito in my product and no hacks involved...

Are we using very old orbit build or something?

On Tue, Dec 8, 2015 at 10:56 AM, Roland Grunberg <rgrunber@xxxxxxxxxx> wrote:

> Who was admin rights to edit jenkins jobs? Can somebody please add a
> post-build action to archive log files so I can at least look at
> workspace/valgrind/org.eclipse.linuxtools.valgrind.core.tests/target/work/configuration/1449088931139.log

I've archived log files :

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/10208/artifact/valgrind/org.eclipse.linuxtools.valgrind.core.tests/target/work/configuration/1449589438672.log

!ENTRY org.eclipse.linuxtools.valgrind.core.tests 2 0 2015-12-08 10:44:01.657
!MESSAGE Could not resolve module: org.eclipse.linuxtools.valgrind.core.tests [181]
  Unresolved requirement: Require-Bundle: org.mockito
    -> Bundle-SymbolicName: org.mockito; bundle-version="1.9.5.v201311280930"
       org.mockito [183]
         Unresolved requirement: Import-Package: COM.jrockit.reflect; resolution:="optional"
         Unresolved requirement: Import-Package: jrockit.vm; resolution:="optional"
         Unresolved requirement: Import-Package: org.hamcrest; version="[1.0.0,2.0.0)"


It looks to me like the same issue we ran into with mockito for the
Docker Tooling. IIRC the latest mockito is a split package so it
must be combined and re-exported or something to that effect. [1]

contains/org.eclipse.linuxtools.docker.tests.hamcrest-wrap was
created for this reason.

If other plugins start using mockito, I think it would make sense
to move that hamcrest wrapper bundle somewhere more common, maybe
even releng/

Cheers,
--
Roland Grunberg

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=403676#c10