* autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433
@ 2012-04-10 15:16 Lu, Lianhao
2012-04-10 16:01 ` Saul Wold
0 siblings, 1 reply; 4+ messages in thread
From: Lu, Lianhao @ 2012-04-10 15:16 UTC (permalink / raw)
To: Wold, Saul; +Cc: yocto
Hi Saul,
I think I might have some clues why the python-nativesdk failed at http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433. It's due to the commit http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stage/master_under_test&id=a1f1cc4c27b5091870b1dbd9ede7c24c38d765dd.
I guess the above commit which changed eglibc-nativesdk to version 2.15 has some conflict to the sstate-cache the autobuilder used, which might contains content from old eglibc-nativesdk 2.13.
-Lianhao
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433
2012-04-10 15:16 autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433 Lu, Lianhao
@ 2012-04-10 16:01 ` Saul Wold
2012-04-11 1:40 ` Lu, Lianhao
0 siblings, 1 reply; 4+ messages in thread
From: Saul Wold @ 2012-04-10 16:01 UTC (permalink / raw)
To: Lu, Lianhao; +Cc: yocto
On 04/10/2012 08:16 AM, Lu, Lianhao wrote:
> Hi Saul,
>
> I think I might have some clues why the python-nativesdk failed at http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433. It's due to the commit http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stage/master_under_test&id=a1f1cc4c27b5091870b1dbd9ede7c24c38d765dd.
>
> I guess the above commit which changed eglibc-nativesdk to version 2.15 has some conflict to the sstate-cache the autobuilder used, which might contains content from old eglibc-nativesdk 2.13.
>
Yes, that would do it, I will hit the sstate reset button and do a build
that should clear this, but will cause problems for most people, I
wonder if we need a PR bump in eglibc also?
Sau!
> -Lianhao
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433
2012-04-10 16:01 ` Saul Wold
@ 2012-04-11 1:40 ` Lu, Lianhao
2012-04-11 15:35 ` McClintock Matthew-B29882
0 siblings, 1 reply; 4+ messages in thread
From: Lu, Lianhao @ 2012-04-11 1:40 UTC (permalink / raw)
To: Wold, Saul; +Cc: yocto
Saul Wold wrote on 2012-04-11:
> On 04/10/2012 08:16 AM, Lu, Lianhao wrote:
>> Hi Saul,
>>
>> I think I might have some clues why the python-nativesdk failed at http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433.
> It's due to the commit
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stage/ma
> ster_under_test&id=a1f1cc4c27b5091870b1dbd9ede7c24c38d 765dd.
>>
>> I guess the above commit which changed eglibc-nativesdk to version 2.15
>> has some conflict to the sstate-cache the autobuilder used, which might
>> contains content from old eglibc-nativesdk 2.13.
>>
> Yes, that would do it, I will hit the sstate reset button and do a build
> that should clear this, but will cause problems for most people, I
> wonder if we need a PR bump in eglibc also?
>
I think theoretically the PV change from 2.13 to 2.15 has the same effect of PR bump. I guess maybe some -nativesdk packages(other than eglibc-nativesdk) which was built upon eglibc-nativesdk 2.13 didn't get rebuilt somehow and went from sstate-cache directly into sysroot.
Since I can't reproduce this compile failure on my local build, do we have the failure environment on autobuilder which I can log on and check?
Best Regards,
Lianhao
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433
2012-04-11 1:40 ` Lu, Lianhao
@ 2012-04-11 15:35 ` McClintock Matthew-B29882
0 siblings, 0 replies; 4+ messages in thread
From: McClintock Matthew-B29882 @ 2012-04-11 15:35 UTC (permalink / raw)
To: Lu, Lianhao; +Cc: yocto, Wold, Saul
On Tue, Apr 10, 2012 at 8:40 PM, Lu, Lianhao <lianhao.lu@intel.com> wrote:
> Saul Wold wrote on 2012-04-11:
>> On 04/10/2012 08:16 AM, Lu, Lianhao wrote:
>>> Hi Saul,
>>>
>>> I think I might have some clues why the python-nativesdk failed at http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433.
>> It's due to the commit
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stage/ma
>> ster_under_test&id=a1f1cc4c27b5091870b1dbd9ede7c24c38d 765dd.
>>>
>>> I guess the above commit which changed eglibc-nativesdk to version 2.15
>>> has some conflict to the sstate-cache the autobuilder used, which might
>>> contains content from old eglibc-nativesdk 2.13.
>>>
>> Yes, that would do it, I will hit the sstate reset button and do a build
>> that should clear this, but will cause problems for most people, I
>> wonder if we need a PR bump in eglibc also?
>>
>
> I think theoretically the PV change from 2.13 to 2.15 has the same effect of PR bump. I guess maybe some -nativesdk packages(other than eglibc-nativesdk) which was built upon eglibc-nativesdk 2.13 didn't get rebuilt somehow and went from sstate-cache directly into sysroot.
>
> Since I can't reproduce this compile failure on my local build, do we have the failure environment on autobuilder which I can log on and check?
Should the new OEBasicHash force a rebuild of those packages though?
-M
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-04-11 15:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-10 15:16 autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433 Lu, Lianhao
2012-04-10 16:01 ` Saul Wold
2012-04-11 1:40 ` Lu, Lianhao
2012-04-11 15:35 ` McClintock Matthew-B29882
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.