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

Bug 325985

Summary:	need to add general " check for 'build failed' " test at various points
Product:	[WebTools] WTP Releng	Reporter:	David Williams <david_williams>
Component:	releng	Assignee:	webtools.releng <webtools.releng-inbox>
Status:	RESOLVED WONTFIX	QA Contact:	David Williams <david_williams>
Severity:	normal
Priority:	P3
Version:	3.10
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description David Williams

2010-09-22 12:00:32 EDT

Currently, the build can fail in various ways, at several points, but is allowed to continue as best it can, for the purpose of possibly finding as many problems at possible in one run. 

The problem with this approach is that it eventually gets to a point that it can not continue, and ends with some "build failed" message that is inaccurate or misleading. 

For example, if signing fails, we continue on compiling, but do not create the standard repository ... so once testing starts, we get a 'failed' message saying such and such bundle could not be found in repository ... or similar. 

I have a vague memory of some task to "check log for failed messages", which would fail if found matching message or phrase. Perhaps that would be a good approach to this problem to get more accurate "failed" messages.

Comment 1 David Williams

2011-09-21 12:51:24 EDT

I am blindly closing old bugs  as "won't fix" (I selected those opened over two years ago, mostly opened by me, with no comments made in past couple of years). 

This is entirely an effort to focus on relevant bugs ... so if anyone sees any of these old bugs closed as "won't fix" that _are_ still relevant, do feel free to reopen. It would be much appreciated to know it was still important and deserves some attention beyond a blind close. Apologies in advance for closing any prematurely.