diff options
Diffstat (limited to 'production/testScripts/configuration/sdk.tests/testScripts/test.xml')
| -rw-r--r-- | production/testScripts/configuration/sdk.tests/testScripts/test.xml | 13 |
1 files changed, 2 insertions, 11 deletions
diff --git a/production/testScripts/configuration/sdk.tests/testScripts/test.xml b/production/testScripts/configuration/sdk.tests/testScripts/test.xml index 07f0d510d..4857a3ace 100644 --- a/production/testScripts/configuration/sdk.tests/testScripts/test.xml +++ b/production/testScripts/configuration/sdk.tests/testScripts/test.xml @@ -922,12 +922,7 @@ <target name="setRuntimeArchive" unless="runtimeArchive"> - <!-- we'll check "alt" baselinePerf first. This is what's used for "several releases ago", or similar. --> - <condition - property="buildIdToUse" - value="${baselinePerfAltVersionLabel}"> - <istrue value="${baselinePerfAlt}" /> - </condition> + <condition property="buildIdToUse" value="${baselinePerfVersionLabel}" @@ -1457,11 +1452,7 @@ <!-- buildIdToUse equals either baselinePerfVersion or else equals buildId. In either case we want to collect the data --> <!-- TODO: Do we need "buildID" coded somewhere, to know WHICH build to match with? Or, else will take large number of "baselines" averaged? --> - <condition - property="eclipse.perf.config" - value="build=${baselinePerfAltVersion};config=${testedPlatformConfig};jvm=${javaMajorVersion}"> - <istrue value="${baselinePerfAlt}" /> - </condition> + <condition property="eclipse.perf.config" value="build=${baselinePerfVersion};config=${testedPlatformConfig};jvm=${javaMajorVersion}" |