| Summary: | Add a build profile which checks the things which may need a proxy | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Dave Stewart <david.c.stewart> |
| Component: | bitbake | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | josh, poky.bs.watcher, poky.watcher, sgw |
| Version: | unspecified | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | Code under review | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Dave Stewart
2011-03-25 15:18:25 UTC
*** Bug 1014 has been marked as a duplicate of this bug. *** We should be able to add such checking into the sanity tests (so that it's run automatically). As this will potentially be a lengthy test we can use the check_sanity_tmpdir_change() sanity check harness such that it's only run when the tmpdir location has changed. It would probably be a nice idea to allow people to disable this test in their local.conf rather than running the test each time a new build dir is used. Alternatively we may consider adding a new sanity test harness for "first run" or some such which doesn't rely on any changeable configuration - however this could easily be a part 2 patch implemented later. I have a first stab at this. Before we can merge it we'll need a list of uris we can rely on to fetch from (http/https/ftp/git) and to populate the wiki page: https://wiki.yoctoproject.org/wiki/ConnectivityTroubleshooting The code I have only checks http and https for now, feedback gratefully received! http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=josh/proxy-test Based on some feedback from Richard I've updated the patch and pushed it to the same contrib branch. I have a set of URL's to use: https://eula-downloads.yoctoproject.org/ http://yoctoproject.org/ git://git.yoctoproject.org Code out for review on the oe-core mailing list. |