Re: Fetcher error reporting
Richard Purdie <rpurdie@...>
On Fri, 2010-10-22 at 11:22 -0700, Darren Hart wrote:
Here is an example of the do_fetch/do_unpack failure that I believe isWe've talked about this a lot over jabber. We don't have a reproducer.
What we do see is its always the wget fetcher that hits this (for mirror
urls in the case of git repos) and its failing creating a zero length
If we make the assumption that wget is creating the empty file and
exiting with an error code and look at what bitbake would do, it would
give the behaviour described in these bugs.
Why? If the original fetch fails, it falls back to the mirror code. That
looks, sees a file on the disk and says "nothing to do".
Solution is therefore to make sure if the wget fetcher fails we wipe any
file that may be present.
Is is possible the wget fetcher is creating a zero length file and no
setting an error code but I really hope its not that broken.
So I've pushed this patch as a bandaid for the problem: