Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364151

Summary:	Problems getting the "prereq" eclipse
Product:	[Tools] Orbit	Reporter:	David Williams <david_williams>
Component:	releng	Assignee:	David Williams <david_williams>
Status:	RESOLVED FIXED	QA Contact:	Project Inbox <orbit.releng-inbox>
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2011-11-18 09:06:37 EST

There were some recent build failures, that exhibited several problems.

The fundamental problem was that our scripts tried to get the a version of Eclipse SDK to use for our builds, but failed. The antBuilderOutput.log said

[orbit-set1] download:
[orbit-set1] [get] Getting: http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/eclipse-SDK-3.7.1-linux-gtk.tar.gz
[orbit-set1] [get] To: /shared/orbit/prereqsCache/eclipse-SDK-3.7.1-linux-gtk.tar.gz
[orbit-set1] [get] Error getting http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/eclipse-SDK-3.7.1-linux-gtk.tar.gz to /shared/orbit/prereqsCache/eclipse-SDK-3.7.1-linux-gtk.tar.gz

But, using a web browser, from non-build machine network, I can get that file fine ... and then I tried using wget from build machine shell, and it could fetch this file find

wget http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/eclipse-SDK-3.7.1-linux-gtk.tar.gz

During the (initial part of the build we generate dependency.eclipse.xml to get this file, which as far as I recall uses the ant equivilent of wget so it may have been a temporary failure of the "internal" build.eclipse.org network to be able to fetch things from download.eclipse.org.

If there's something wrong with the "dependency scripts" it will take closer investigation and testing. ... but, the build should run right now, that I have manually fetched the prereq with wget.

So, I'll let build run, now, and do more systematic testing later.

But, this issue exposes another bug, and a good enhancement.

A. the file was removed from prereqscache by our "cleanup" scripts, I'm assuming, but it should not have been. It is likely not being marked as "accessed" correctly so the cleanup script thinks it is no longer in use.

B. This would be a good place to improve scripts so if it fails to fetch the pre-req, the build fails immediately with a clear message it failed to fetch the pre-req. As it is, the fetch fails, but the script plods along, and fails later with some unhelpful messages.

I'll open new bugs for "A" and "B" when ready to look at those, but this bug will be used to test the ability for dependencies scripts to fetch the pre-req. It might have been a temporary network problem ... or, might be an error in scripts.

Comment 1 David Williams

2011-11-18 09:27:32 EST

I've opened following bugs for the "A" and "B" issues mentioned in comment 0. 

Bug 364157 - Problems getting the "prereq" eclipse -- could fail more gracefully

Bug 364156 - Problems getting the "prereq" eclipse -- removed prematurely

Comment 2 David Williams

2011-11-19 19:47:59 EST

I'll count this as "fixed". I'm still not positive it wasn't an infrastructure issue, but did see some odd things with regard to "ownership" of one of the directories, so might have been related to that (which, I did fix). But I subsequently deleted it on purpose, and the build was able to fetch and install as its supposed to.