Closed eclipse-modisco-bot closed 3 days ago
Oct 08, 2015 10:21
New Gerrit change created: https://git.eclipse.org/r/57717
Oct 09, 2015 05:25
Gerrit change https://git.eclipse.org/r/57717 was merged to [master].\ Commit: http://git.eclipse.org/c/modisco/org.eclipse.modisco.git/commit/?id=4f8ad95a184431e95b9d43106a731b73fa4f08a0
By Gregoire Dupe on Oct 09, 2015 05:26
This bug is resolved.
| --- | --- | | Bugzilla Link | 479339 | | Status | RESOLVED FIXED | | Importance | P1 normal | | Reported | Oct 08, 2015 09:39 EDT | | Modified | Oct 09, 2015 05:27 EDT | | Version | 0.13.0 | | See also | Gerrit change https://git.eclipse.org/r/57717, Git commit 4f8ad95a | | Reporter | Gregoire Dupe |
Description
Since a few days the test 'TestMemoryUsage.test002' fails randomly.
The process tested by this junit test look to use more memory than expected:
Abnormal memory use for Java Composition Discoverer 175 > 100\ Abnormal memory use for Java Composition Discoverer 106 > 100\ Abnormal memory use for Java Composition Discoverer 107 > 100\ Abnormal memory use for Java Composition Discoverer 154 > 100\ Abnormal memory use for Java Composition Discoverer 116 > 100\ Abnormal memory use for Java Composition Discoverer 101 > 100
No code have been modified. It may be caused by the recent use of Java 1.8 or by an update of release train component.
Further more this test cannot be really accurate. (Memory tracking is populated by other threads and by the garbage collector random behavior.)
The less worth solution is to increase the threshold to 180Mo.