From 3ca66f6d8839ae87f6e7dc2196b93265173220e2 Mon Sep 17 00:00:00 2001
From: Sravan Kumar L
Date: Thu, 21 Mar 2019 21:44:38 +0530
Subject: Bug 545606 - Mac Test run failed for I20190320-1800

Change-Id: I4e54d98f81a84ee7acde339a3c5ca19dd6e303cf
---
 production/testScripts/configuration/streamSpecific.properties | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/production/testScripts/configuration/streamSpecific.properties b/production/testScripts/configuration/streamSpecific.properties
index 9d8364f4a..140c732b9 100644
--- a/production/testScripts/configuration/streamSpecific.properties
+++ b/production/testScripts/configuration/streamSpecific.properties
@@ -11,7 +11,7 @@ streamSpecificPropertiesTitle="Properties for 4.12.0 builds and tests"
 # stable version of Eclipse, that is used, for example, for it's p2
 # director, etc., so that "running the tests" is not actually using
 # the "just built" versions.
-previousReleaseLocation=https://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
+previousReleaseLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
 # version here is "build label" ... in general form, the "middle" of archive name,
 # such as  "eclipse-platform-${previousReleaseVersion}-linux-gtk-x86_64.tar.gz
 # Also used used in p2 testing?
@@ -34,7 +34,7 @@ apiTestsPreviousRefererenceWin32Filename=obsoleteAndNotUsed
 # baselinePerf=true
 # are specified. The baselinePerf will often be the same as "previous release", but
 # not necessarily, so is not hard coded in assumptions.
-baselinePerfLocation=https://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
+baselinePerfLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
 baselinePerfVersion=R-4.11-201903070500
 # TODO: could/should eventually "compute" label, from full version?
 baselinePerfVersionLabel=4.11
-- 
cgit v1.2.3