Bug 5853 - BitBake should give some status indication when fetching sstate packages
Summary: BitBake should give some status indication when fetching sstate packages
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.5.1
Hardware: All Multiple
: Medium enhancement
Target Milestone: 2.2
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-02-20 11:54 UTC by Paul Eggleton
Modified: 2016-07-10 22:36 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2014-02-20 11:54:51 UTC 
Before running the setscene tasks, BitBake runs through a process of checking which sstate packages are available. If you have SSTATE_MIRRORS pointing to some remote server on a slow link this process can take significant amount of time and there's no message or other indication as to what is happening.

According to Richard this functionality is in sstate.bbclass in sstate_checkhashes() iterating over fetcher.checkstatus(). We may need to send some events (bb.event.MetadataEvent ?) that the UI can pick up and report.