[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[tycho-user] What could have triggered the change of the caching behavior of "Adding repository" ?
|
Hi,
from one day to the other one of my build jobs begun to fail because of java.lang.OutOfMemoryError: Java heap space. And I'm still trying to figure out why?
I noticed a little behavioral change while the tycho-surefire-plugin tries to resolve the org.eclipse.equinox.launcher from my locally mirrored Indigo repository. Befor the build started to fail, the Indo repository was already cached by Tycho, but now Tycho decides to add a "fresh" repository, see snippets below (Adding repository (cached) vs. Adding repository).
What could have triggered this behavioral change?
Neither the build configuration, hardware or software was changed nor the source code. BUT around this time I have updated the local Indigo mirror with the new 3.7.2 stuff.
Thanks in advance
Bernd
The good old days (
http://jenkins.sourcepit.org/job/b2_nightly/213/consoleFull):
[INFO] --- tycho-surefire-plugin:0.14.1:test (default-test) @ org.sourcepit.b2.examples.simple.module.tests ---
[...]
[INFO] Adding repository
(cached) http://p2.sourcepit.org/eclipse/indigo/[INFO] Downloading org.eclipse.equinox.launcher
[...]
Now (
http://jenkins.sourcepit.org/job/b2_nightly/209/consoleFull):
[INFO] --- tycho-surefire-plugin:0.14.1:test (default-test) @ org.sourcepit.b2.examples.simple.module.tests ---
[...]
[INFO] Adding repository
http://p2.sourcepit.org/eclipse/indigo/[ERROR] Java heap space -> [Help 1]
java.lang.OutOfMemoryError: Java heap space
