From: ChenQi <Qi.Chen@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] devtool.py: remove fetch results from download directory to avoid failure
Date: Tue, 22 Jan 2019 10:22:15 +0800 [thread overview]
Message-ID: <5b260b75-4792-2914-58cd-1f545b0ce6fc@windriver.com> (raw)
In-Reply-To: <adcb2224cfb62745ee54c5f04c1c75ff9d803ed1.camel@linuxfoundation.org>
On 01/21/2019 05:53 PM, Richard Purdie wrote:
> On Mon, 2019-01-21 at 17:29 +0800, Chen Qi wrote:
>> The fetch results need to be removed from the download directory to
>> avoid
>> failures like below.
>>
>> Submodule path 'doxyport': checked out
>> 'db3e1a6eb8677d3166d90d82c3068689803ce547'
>>
>> fatal: reference is not a tree:
>> 67cad692720982ac3cbd99bf1c3421edc69b08f9
>> Unable to checkout '67cad692720982ac3cbd99bf1c3421edc69b08f9' in
>> submodule path 'doxygen2jsdoc'
>>
>> ERROR: Function failed: base_do_unpack
> I'd like to understand the problem here a bit more. My worry is that
> deleting files manually from DL_DIR is bad practise, particularly if
> that directory is shared between builds like on our autobuilder.
>
> We've had similar problems with cleansstate since that can also remove
> artefacts from the sstate cache which another build may be using. We
> can do this only when the sstate directory is not shared.
>
> Cheers,
>
> Richard
>
>
I just pulled to latest master and did the tests again. Things worked
well. This patch is not needed.
It seems that Mark's commits regarding gitsm in bitbake has fixed the
problem I met.
Best Regards,
Chen Qi
prev parent reply other threads:[~2019-01-22 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 9:29 [PATCH 0/1] devtool.py: remove fetch results from download directory to avoid failure Chen Qi
2019-01-21 9:29 ` [PATCH 1/1] " Chen Qi
2019-01-21 9:53 ` Richard Purdie
2019-01-22 2:22 ` ChenQi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b260b75-4792-2914-58cd-1f545b0ce6fc@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox