Bug 255840 - SIOOBE during performance test commit
Summary: SIOOBE during performance test commit
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4.2   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance, test
Depends on:
Blocks:
 
Reported: 2008-11-19 12:11 EST by Olivier Thomann CLA
Modified: 2008-11-21 05:05 EST (History)
0 users

See Also:

Attachments
Proposed patch (2.62 KB, patch)
2008-11-21 05:03 EST, Frederic Fusier CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2008-11-19 12:11:00 EST 
Using I20081118-1720, I got this error running the api tooling performance tests inside my workspace.
You have to run them as ui tests since they required the external tool builder to run.

java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1938)
	at org.eclipse.test.internal.performance.InternalPerformanceMeter.printSample(InternalPerformanceMeter.java:139)
	at org.eclipse.test.internal.performance.InternalPerformanceMeter.commit(InternalPerformanceMeter.java:97)
	at org.eclipse.test.performance.PerformanceTestCase.commitMeasurements(PerformanceTestCase.java:151)
	at org.eclipse.jdt.core.tests.junit.extension.TestCase.commitMeasurements(TestCase.java:764)
	at org.eclipse.pde.api.tools.builder.tests.performance.ApiDescriptionTests.testCleanVisit(ApiDescriptionTests.java:86)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at junit.framework.TestCase.runTest(TestCase.java:164)
	at junit.framework.TestCase.runBare(TestCase.java:130)
Comment 1 Olivier Thomann CLA 2008-11-19 14:10:43 EST 
It didn't fail again on the next run. But if this path is possible in the code, it should be protected.
Comment 2 Frederic Fusier CLA 2008-11-21 05:03:39 EST 
Created attachment 118444 [details]
Proposed patch
Comment 3 Frederic Fusier CLA 2008-11-21 05:05:00 EST 
Released both in HEAD and R3_4_maintenance streams.