[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
From:       Bruce Ashfield <bruce.ashfield () gmail ! com>
Date:       2017-04-27 18:46:39
Message-ID: CADkTA4NQbqiN=+=y5g6c+d8zkgRB59y7v47yW9qeLxYBfBU2=A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Apr 27, 2017 at 12:32 PM, Martin Jansa <martin.jansa@gmail.com>
wrote:

> Yesterday I've deleted all workspaces where I was getting this error and
> since then I haven't seen one.
>
> So maybe the key to reproduce this was to run builds without the fix
> applied and then apply the fix and execute another build without removing
> the tmp-glibc (so that it tries to do incremental build from the bad state
> created before without this fix).
>

Interesting. Thanks for letting me know .. I'll try and set up the same
steps here. I was worried
that all your build were still breaking on this, and yet I couldn't make it
happen.

Hopefully this will lead me to the root cause.

Bruce


>
> On Wed, Apr 26, 2017 at 2:45 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Apr 26, 2017 at 8:25 AM, Burton, Ross <ross.burton@intel.com>
>> wrote:
>>
>>> Not sure if it's related to this problem, but this happened in selftest
>>> last night:
>>>
>>> Log data follows:
>>> | DEBUG: Executing shell function do_kernel_metadata
>>> | ERROR: Could not generate configuration queue for qemux86.
>>> | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-se
>>> lftest/build/build/tmp/work/qemux86-poky-linux/linux-yocto/
>>> 4.10.9+git999-r0/temp/run.do_kernel_metadata.37215: line 190: spp:
>>> command not found
>>>
>>> | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-se
>>> lftest/build/build/tmp/work/qemux86-poky-linux/linux-yocto/
>>> 4.10.9+git999-r0/temp/run.do_kernel_metadata.37215: line 191: kgit:
>>> command not found
>>>
>>> | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-se
>>> lftest/build/build/tmp/work/qemux86-poky-linux/linux-yocto/
>>> 4.10.9+git999-r0/temp/run.do_kernel_metadata.37215: line 197: scc:
>>> command not found
>>>
>>> | ERROR: Function failed: do_kernel_metadata (log file is located at
>>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-se
>>> lftest/build/build/tmp/work/qemux86-poky-linux/linux-yocto/
>>> 4.10.9+git999-r0/temp/log.do_kernel_metadata.37215)
>>>
>>
>>
>> Not related to the patching error, but related to my change where I
>> modified
>> the native depends.  For whatever reason that ran before the
>> do_validate_branches,
>> which is what pulls in the dependency.
>>
>> I can't think of how that could happen, but there seems to be some tasks
>> that are now racing.
>>
>> I'll revisit the patch and put the dependency in both places just to be
>> sure.
>>
>> Bruce
>>
>>
>>>
>>>
>>> Ross
>>>
>>> On 25 April 2017 at 14:17, Bruce Ashfield <bruce.ashfield@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie <
>>>> richard.purdie@linuxfoundation.org> wrote:
>>>>
>>>>> On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote:
>>>>> > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie
>>>>> > <richard.purdie@linuxfoundation.org> wrote:
>>>>> > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote:
>>>>> > > >
>>>>> > > >
>>>>> > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield <bruce.ashfield@g
>>>>> > > mail
>>>>> > > > .com> wrote:
>>>>> > > > >
>>>>> > > > >
>>>>> > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa <martin.jansa@gma
>>>>> > > il.c
>>>>> > > > > om> wrote:
>>>>> > >
>>>>> > > >
>>>>> > > > Richard/Ross: are you seeing this same thing on the autobuilder ?
>>>>> > > >
>>>>> > > > There's some incantation or config that I'm missing, I assume
>>>>> > > this is
>>>>> > > > a straight qemux86 config
>>>>> > > > with a bitbake of something like core-image-minimal ?
>>>>> > >
>>>>> > > We're not seeing this on the autobuilders. I do suspect something
>>>>> > > in
>>>>> > > the handling of extra patches or cfg fragments from SRC_URI if I
>>>>> > > had to
>>>>> > > guess. That certainly was the trigger last time I saw this.
>>>>> > Yah, that's the kicker, I'm still carrying your patch for binfmt_elf,
>>>>> > and I added two of my own
>>>>> > + config fragments, and I can't trigger anything.
>>>>>
>>>>> I managed to reproduce breakage. With master and my separate patch in
>>>>> SRC_URI:
>>>>>
>>>>>
>>>> This particular issue should be fixed with with patch I sent, late
>>>> Friday night:
>>>>
>>>> [OE-core] [PATCH] kernel-yocto/kern-tools: fix do_validate_branches
>>>> clean stage
>>>>
>>>> Martin applied it to his builds and is still seeing an issue in the
>>>> actual patching phase.
>>>> I'm currently not able to reproduce it.
>>>>
>>>> If you do have that patch applied, I'm definitely interested. If you
>>>> don't, and have two
>>>> minutes to re-run with that applied .. I'd be interested to hear if the
>>>> build works after
>>>> that.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>> $ bitbake linux-yocto
>>>>> $ bitbake linux-yocto -c kernel_checkout -f
>>>>> $ bitbake linux-yocto
>>>>>
>>>>> ERROR: linux-yocto-4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0
>>>>> do_validate_branches: Function failed: do_validate_branches (log file is
>>>>> located at /media/build1/poky/build/tmp/w
>>>>> ork/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e
>>>>> 885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726)
>>>>> ERROR: Logfile of failure stored in: /media/build1/poky/build/tmp/w
>>>>> ork/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e
>>>>> 885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726
>>>>> Log data follows:
>>>>> | DEBUG: Executing shell function do_validate_branches
>>>>> | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base
>>>>> | 1493125671.284715: mkdir: cannot create directory ‘.': File exists
>>>>> | 1493125671.370592:
>>>>> | 1493125671.3742917: [ERROR] Can't find patch dir at
>>>>> ./patches/standard/base
>>>>> | 1493125671.3742917: usage: kgit s2q
>>>>> | 1493125671.3743172: WARNING: exit code 1 from a shell command.
>>>>> | 1493125671.3745801: ERROR: Function failed: do_validate_branches
>>>>> (log file is located at /media/build1/poky/build/tmp/w
>>>>> ork/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e
>>>>> 885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726)
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>>>> thee at its end"
>>>>
>>>
>>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
>> at its end"
>>
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr \
27, 2017 at 12:32 PM, Martin Jansa <span dir="ltr">&lt;<a \
href="mailto:martin.jansa@gmail.com" \
target="_blank">martin.jansa@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Yesterday I&#39;ve deleted all workspaces \
where I was getting this error and since then I haven&#39;t seen \
one.<div><br></div><div>So maybe the key to reproduce this was to run builds without \
the fix applied and then apply the fix and execute another build without removing the \
tmp-glibc (so that it tries to do incremental build from the bad state created before \
without this fix).</div></div></blockquote><div><br></div><div>Interesting. Thanks \
for letting me know .. I&#39;ll try and set up the same steps here. I was \
worried</div><div>that all your build were still breaking on this, and yet I \
couldn&#39;t make it happen.</div><div><br></div><div>Hopefully this will lead me to \
the root cause.</div><div><br></div><div>Bruce</div><div>  </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 26, 2017 at 2:45 PM, \
Bruce Ashfield <span dir="ltr">&lt;<a href="mailto:bruce.ashfield@gmail.com" \
target="_blank">bruce.ashfield@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div \
class="gmail_quote"><span>On Wed, Apr 26, 2017 at 8:25 AM, Burton, Ross <span \
dir="ltr">&lt;<a href="mailto:ross.burton@intel.com" \
target="_blank">ross.burton@intel.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Not sure if it&#39;s related to this problem, \
but this happened in selftest last night:<br><br>Log data follows:<br>| DEBUG: \
Executing shell function do_kernel_metadata<br>| ERROR: Could not generate \
configuration queue for qemux86.<br>| \
/home/pokybuild/yocto-autobuil<wbr>der/yocto-worker/nightly-oe-se<wbr>lftest/build/bui \
ld/tmp/work/qe<wbr>mux86-poky-linux/linux-yocto/<wbr>4.10.9+git999-r0/temp/run.do_<wbr>kernel_metadata.37215: \
line 190: spp: command not found<div><br>| \
/home/pokybuild/yocto-autobuil<wbr>der/yocto-worker/nightly-oe-se<wbr>lftest/build/bui \
ld/tmp/work/qe<wbr>mux86-poky-linux/linux-yocto/<wbr>4.10.9+git999-r0/temp/run.do_<wbr>kernel_metadata.37215: \
line 191: kgit: command not found</div><div><br>| \
/home/pokybuild/yocto-autobuil<wbr>der/yocto-worker/nightly-oe-se<wbr>lftest/build/bui \
ld/tmp/work/qe<wbr>mux86-poky-linux/linux-yocto/<wbr>4.10.9+git999-r0/temp/run.do_<wbr>kernel_metadata.37215: \
line 197: scc: command not found</div><div><br>| ERROR: Function failed: \
do_kernel_metadata (log file is located at \
/home/pokybuild/yocto-autobuil<wbr>der/yocto-worker/nightly-oe-se<wbr>lftest/build/bui \
ld/tmp/work/qe<wbr>mux86-poky-linux/linux-yocto/<wbr>4.10.9+git999-r0/temp/log.do_<wbr \
>kernel_metadata.37215)</div></div></blockquote><div><br></div><div><br></div></span><div>Not \
> related to the patching error, but related to my change where I \
> modified</div><div>the native depends.   For whatever reason that ran before the \
> do_validate_branches,</div><div>which is what pulls in the \
> dependency.</div><div><br></div><div>I can&#39;t think of how that could happen, \
> but there seems to be some tasks that are now \
> racing.</div><div><br></div><div>I&#39;ll revisit the patch and put the dependency \
> in both places just to be sure.</div><span \
> class="m_-6245096803047131663HOEnZb"><font \
> color="#888888"><div><br></div><div>Bruce</div></font></span><div><div \
> class="m_-6245096803047131663h5"><div>  </div><blockquote class="gmail_quote" \
> style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
> dir="ltr"><div><span \
> class="m_-6245096803047131663m_-2697917455396176618HOEnZb"><font \
> color="#888888"><br><br></font></span></div><span \
> class="m_-6245096803047131663m_-2697917455396176618HOEnZb"><font \
> color="#888888"><div>Ross</div></font></span></div><div \
> class="m_-6245096803047131663m_-2697917455396176618HOEnZb"><div \
> class="m_-6245096803047131663m_-2697917455396176618h5"><div \
> class="gmail_extra"><br><div class="gmail_quote">On 25 April 2017 at 14:17, Bruce \
> Ashfield <span dir="ltr">&lt;<a href="mailto:bruce.ashfield@gmail.com" \
> target="_blank">bruce.ashfield@gmail.com</a>&gt;</span> wrote:<br><blockquote \
> class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
> solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div \
> class="gmail_quote"><div><div \
> class="m_-6245096803047131663m_-2697917455396176618m_-4198958585454020572h5">On \
> Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie <span dir="ltr">&lt;<a \
> href="mailto:richard.purdie@linuxfoundation.org" \
> target="_blank">richard.purdie@linuxfoundatio<wbr>n.org</a>&gt;</span> \
> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px \
> 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Mon, \
> 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote:<br>
&gt; On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie<br>
&gt; &lt;<a href="mailto:richard.purdie@linuxfoundation.org" \
target="_blank">richard.purdie@linuxfoundatio<wbr>n.org</a>&gt; wrote:<br> &gt; &gt; \
On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote:<br> &gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield \
&lt;bruce.ashfield@g<br> &gt; &gt; mail<br>
&gt; &gt; &gt; .com&gt; wrote:<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa \
&lt;martin.jansa@gma<br> &gt; &gt; il.c<br>
&gt; &gt; &gt; &gt; om&gt; wrote:<br>
&gt; &gt;  <br>
&gt; &gt; &gt;<br>
</span><span>&gt; &gt; &gt; Richard/Ross: are you seeing this same thing on the \
autobuilder ?<br> &gt; &gt; &gt;<br>
&gt; &gt; &gt; There&#39;s some incantation or config that I&#39;m missing, I \
assume<br> &gt; &gt; this is<br>
&gt; &gt; &gt; a straight qemux86 config<br>
&gt; &gt; &gt; with a bitbake of something like core-image-minimal ?<br>
&gt; &gt;<br>
&gt; &gt; We&#39;re not seeing this on the autobuilders. I do suspect something<br>
&gt; &gt; in<br>
&gt; &gt; the handling of extra patches or cfg fragments from SRC_URI if I<br>
&gt; &gt; had to<br>
&gt; &gt; guess. That certainly was the trigger last time I saw this.<br>
&gt; Yah, that&#39;s the kicker, I&#39;m still carrying your patch for \
binfmt_elf,<br> &gt; and I added two of my own<br>
&gt; + config fragments, and I can&#39;t trigger anything.<br>
<br>
</span>I managed to reproduce breakage. With master and my separate patch in<br>
SRC_URI:<br>
<br></blockquote><div><br></div></div></div><div>This particular issue should be \
fixed with with patch I sent, late Friday night:</div><div><br></div><div>[OE-core] \
[PATCH] kernel-yocto/kern-tools: fix do_validate_branches clean \
stage<br></div><div><br></div><div>Martin applied it to his builds and is still \
seeing an issue in the actual patching phase.</div><div>I&#39;m currently not able to \
reproduce it.</div><div><br></div><div>If you do have that patch applied, I&#39;m \
definitely interested. If you don&#39;t, and have two</div><div>minutes to re-run \
with that applied .. I&#39;d be interested to hear if the build works \
after</div><div>that.</div><div><br></div><div>Cheers,</div><div><br></div><div>Bruce</div><span><div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> $ bitbake linux-yocto<br>
$ bitbake linux-yocto -c kernel_checkout -f<br>
$ bitbake linux-yocto<br>
<br>
ERROR: linux-yocto-4.10.9+gitAUTOINC+<wbr>ad2e885015_fe0fb8da3d-r0 \
do_validate_branches: Function failed: do_validate_branches (log file is located at \
/media/build1/poky/build/tmp/w<wbr>ork/qemux86_64-poky-linux/linu<wbr>x-yocto/4.10.9+g \
itAUTOINC+ad2e<wbr>885015_fe0fb8da3d-r0/temp/log.<wbr>do_validate_branches.116726)<br>
                
ERROR: Logfile of failure stored in: \
/media/build1/poky/build/tmp/w<wbr>ork/qemux86_64-poky-linux/linu<wbr>x-yocto/4.10.9+g \
itAUTOINC+ad2e<wbr>885015_fe0fb8da3d-r0/temp/log.<wbr>do_validate_branches.116726<br> \
<span>Log data follows:<br> | DEBUG: Executing shell function \
do_validate_branches<br> | HEAD is now at fe0fb8d Merge tag &#39;v4.10.9&#39; into \
standard/base<br> </span>| 1493125671.284715: mkdir: cannot create directory ‘.': \
File exists<br> | 1493125671.370592:<br>
> 1493125671.3742917: [ERROR] Can&#39;t find patch dir at ./patches/standard/base<br>
> 1493125671.3742917: usage: kgit s2q<br>
> 1493125671.3743172: WARNING: exit code 1 from a shell command.<br>
> 1493125671.3745801: ERROR: Function failed: do_validate_branches (log file is \
> located at /media/build1/poky/build/tmp/w<wbr>ork/qemux86_64-poky-linux/linu<wbr>x-y \
> octo/4.10.9+gitAUTOINC+ad2e<wbr>885015_fe0fb8da3d-r0/temp/log.<wbr>do_validate_branches.116726)<br>
> 
<br>
Cheers,<br>
<br>
Richard<br>
<br>
<br>
<br>
</blockquote></span></div><br><br clear="all"><span><div><br></div>-- <br><div \
class="m_-6245096803047131663m_-2697917455396176618m_-4198958585454020572m_-249460446374544245gmail-m_1060650381739365254gmail_signature">&quot;Thou \
shalt not follow the NULL pointer, for chaos and madness await thee at its \
end&quot;</div> </span></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div></div></div><div><div \
class="m_-6245096803047131663h5"><br><br clear="all"><div><br></div>-- <br><div \
class="m_-6245096803047131663m_-2697917455396176618gmail_signature" \
data-smartmail="gmail_signature">&quot;Thou shalt not follow the NULL pointer, for \
chaos and madness await thee at its end&quot;</div> </div></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div \
class="gmail_signature" data-smartmail="gmail_signature">&quot;Thou shalt not follow \
the NULL pointer, for chaos and madness await thee at its end&quot;</div> \
</div></div>



-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic