Auto remove corrupt tarballs from the milestone cache

[GoogleCodeExporter]

There are a number of broken builds due to the tar ball cache being corrupt. 
Automatically testing 
and removing the tarballs, will reduce the problem.

Original issue reported on code.google.com by shaunmcd...@gmail.com on 10 Oct 2007 at 6:58

[GoogleCodeExporter]

This requires changes in the cws_get script.

Original comment by shaunmcd...@gmail.com on 13 Oct 2007 at 11:54

• Added labels: Component-Slave

[GoogleCodeExporter]

As the current cws_get will not build broken milestones due to the blacklist 
this is
IMHO not necessary.

Original comment by christia...@web.de on 8 Aug 2008 at 11:17

[GoogleCodeExporter]

The problem is that a tar ball could have been produced before the cws was 
fully tagged, so you end up with a 
wrong tar ball which needs to be fixed. There could also be errors in the 
download of the tar ball or checkout 
from cvs, which means that it may end up corrupt.

This is why you still need a way to force clear the tar ball cache.

Original comment by shaunmcd...@gmail.com on 8 Aug 2008 at 10:35

[GoogleCodeExporter]

I can only think of download failures. Perhaps one can provide checksum to 
identify
this broken tarballs.

A forced clear would be a good way to get rid of stone-aged tarballs.

Original comment by christia...@web.de on 13 Aug 2008 at 3:11

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Currently it is likely that we have no tar cache in the future, so I deferre 
this 
issue.

Original comment by christia...@web.de on 23 Sep 2008 at 12:45

• Changed state: Deferred