Bug 8727

Summary:	fetcher: should not log errors but pass them for handling
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Aníbal Limón <anibal.limon>
Component:	bitbake	Assignee:	Jose Lamego <jose.a.lamego>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	benjamin.esquivel, leonardo.sandoval.gonzalez, poky.bs.watcher, poky.watcher
Version:	unspecified
Target Milestone:	2.3 M2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Aníbal Limón 2015-11-25 16:48:59 UTC

When using fetcher it logs errors [1] causing a build to fail.

Fetcher is a utility module so it only need to propagate the error/exception and give the ability to the caller to handle the error/exception.

The changes needs to be evaluated for don't break code base that expect the current behavior.

[1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/bb/fetch2/__init__.py#n1636

Comment 1 Aníbal Limón 2017-01-24 17:08:13 UTC

After some review, i figured out that the current implementation of fetcher is too close to bitbake usage so there is no way to remove logger.error from fetcher. 

The bitbake/oe-core code uses try_mirrors to start download and is the main method exposed so there is no way to remove logging internally without affect dependent code.