On 13 February 2017 at 16:02, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> The test is forcing its own private DL_DIR, so I really don't see why we
> should be concerned about avoiding doing cleanall:
>
So it is! Still, overcomplicating things. No need to have a custom DL_DIR
On 02/13/2017 05:36 PM, Burton, Ross wrote:
runCmd('bitbake -c cleanall man xcursor-transparent-theme')
-result = runCmd('bitbake man xcursor-transparent-theme -k',
ignore_status=True)
+result = runCmd('bitbake -c unpack -k man
xcursor-transparent-them
On 13 February 2017 at 15:06, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> runCmd('bitbake -c cleanall man xcursor-transparent-theme')
> -result = runCmd('bitbake man xcursor-transparent-theme -k',
> ignore_status=True)
> +result = runCmd('bitbake -c unp
This was fetching and building the toolchain and everything else
against empty download dir and sstate cache, and so was enormously slow.
The test does not need that, it only checks that one fetch task fails and
another succeeds when using bitbake's -k option.
Signed-off-by: Alexander Kanavin
---
