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

Bug 399274

Summary:	I-build not publishing correct DL page
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert
Version:	4.2.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2013-01-28 10:04:08 EST

This is evident in 

http://build.eclipse.org/eclipse/eclipse4I/siteDir/eclipse/downloads/drops4/I20130127-2000/

Funny thing is, the build _is_ there. 

If you know the filename you want, you can access it directly, such as 

http://build.eclipse.org/eclipse/eclipse4I/siteDir/eclipse/downloads/drops4/I20130127-2000/eclipse-SDK-I20130127-2000-win32-x86_64.zip

Moderately sure the build DL page was "correct" at first, but may have been "stepped" on when we update it after getting test results. ? Just to guess.

Comment 1 David Williams

2013-01-28 10:10:50 EST

Whoops, should have used the download URLs in comment 0. 

http://download.eclipse.org/eclipse/downloads/drops4/I20130127-2000/

http://download.eclipse.org/eclipse/downloads/drops4/I20130127-2000/eclipse-SDK-I20130127-2000-win32-x86_64.zip

Comment 2 David Williams

2013-01-28 16:20:05 EST

I'm going to count this as one of the 1% problems mentioned in bug 396213. 

My RSS Feed from "test complete" was time stamped at 8:08 AM, and that was from the I20130127-2000 build. See. 
https://hudson.eclipse.org/hudson/job/ep4-unit-win32/492/

That was "right after" the 8:00 AM I build started and while exact timing is unknown, I suspect the build was "replacing" the base builder (or, perhaps eclipsebuilder) just at the time that the tests publishing process needed it. (Or, for example, replaced a template, right after the tests publisher has modified it?) 

Rather than focus on fixing this case, I think instead it'll serve as a good reminder not to do it that way for our cbi based builds and tests -- as long as it stays so rare.

*** This bug has been marked as a duplicate of bug 396213 ***