Possible bug in bitbake

Possible bug in bitbake

[Otavio Salvador]

Hello,

Rogerio and Daiane, here copied, found a bug in bitbake (we managed to
reproduce it in denzil). The output in console when it happens can be
seen at:

https://groups.google.com/d/msg/meta-fsl-arm/7W9bwxqslnk/htEiOcaJMH8J

The way to reproduce it is very easy:

 * bitbake gnutls -c cleansstate
 * remove gnutls from download cache
 * bitbake gnutls

Adding gnutls back to download cache make the build succeed.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: Possible bug in bitbake

[Mark Hatle]

On 9/13/12 1:41 PM, Otavio Salvador wrote:
> Hello,
>
> Rogerio and Daiane, here copied, found a bug in bitbake (we managed to
> reproduce it in denzil). The output in console when it happens can be
> seen at:
>
> https://groups.google.com/d/msg/meta-fsl-arm/7W9bwxqslnk/htEiOcaJMH8J
>
> The way to reproduce it is very easy:
>
>   * bitbake gnutls -c cleansstate
>   * remove gnutls from download cache
>   * bitbake gnutls
>
> Adding gnutls back to download cache make the build succeed.
>

There is a stamp file in the download cache.  If you don't clear that, then it 
will think it's still there.

bitbake gnutls -c distclean

that should remove from the download cache, the stamp file, and all of the 
actions of cleansstate.

--Mark

Re: Possible bug in bitbake

[Saul Wold]

On 09/13/2012 12:15 PM, Mark Hatle wrote:
> On 9/13/12 1:41 PM, Otavio Salvador wrote:
>> Hello,
>>
>> Rogerio and Daiane, here copied, found a bug in bitbake (we managed to
>> reproduce it in denzil). The output in console when it happens can be
>> seen at:
>>
>> https://groups.google.com/d/msg/meta-fsl-arm/7W9bwxqslnk/htEiOcaJMH8J
>>
>> The way to reproduce it is very easy:
>>
>>   * bitbake gnutls -c cleansstate
>>   * remove gnutls from download cache
>>   * bitbake gnutls
>>
>> Adding gnutls back to download cache make the build succeed.
>>
>
> There is a stamp file in the download cache.  If you don't clear that,
> then it will think it's still there.
>
> bitbake gnutls -c distclean
>
I think you mean cleanall!

I don't think we have distclean.

Sau!

> that should remove from the download cache, the stamp file, and all of
> the actions of cleansstate.
>
> --Mark
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>

Re: Possible bug in bitbake

[Paul Eggleton]

On Thursday 13 September 2012 15:41:15 Otavio Salvador wrote:
> Hello,
> 
> Rogerio and Daiane, here copied, found a bug in bitbake (we managed to
> reproduce it in denzil). The output in console when it happens can be
> seen at:
> 
> https://groups.google.com/d/msg/meta-fsl-arm/7W9bwxqslnk/htEiOcaJMH8J
> 
> The way to reproduce it is very easy:
> 
>  * bitbake gnutls -c cleansstate
>  * remove gnutls from download cache
>  * bitbake gnutls

Oh, hang on - now you mention gnutls, I think I know what it is. I suspect
if you apply either or both of these patches the issue will go away:

http://cgit.openembedded.org/openembedded-core/commit/?id=0de1827a9601143b090f751ea702fdb65a936b77
http://cgit.openembedded.org/bitbake/commit/?id=57055d337a2c9997a6e5d5bdabaec396e3e128e9

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre