Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Thu, Apr 27, 2017 at 12:32 PM, Martin Jansawrote: > 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 > wrote: > >> >> >> On Wed, Apr 26, 2017 at 8:25 AM, Burton, Ross >> 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 >>> wrote: >>> On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie < richard.pur...@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 > > wrote: > > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > > mail > > > > .com> wrote: > > > > > > > > > > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > > 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 >
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
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). On Wed, Apr 26, 2017 at 2:45 PM, Bruce Ashfieldwrote: > > > On Wed, Apr 26, 2017 at 8:25 AM, Burton, Ross > 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- >> selftest/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- >> selftest/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- >> selftest/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- >> selftest/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 >> wrote: >> >>> >>> >>> On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie < >>> richard.pur...@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 > wrote: > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > mail > > > .com> wrote: > > > > > > > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > 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/work/qemux86_64-poky-linux/linu x-yocto/4.10.9+gitAUTOINC+ad2e885015_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
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Wed, Apr 26, 2017 at 8:25 AM, Burton, Rosswrote: > 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-selftest/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-selftest/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-selftest/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-selftest/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 > wrote: > >> >> >> On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie < >> richard.pur...@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 >>> > wrote: >>> > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: >>> > > > >>> > > > >>> > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield >> > > mail >>> > > > .com> wrote: >>> > > > > >>> > > > > >>> > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa >> > > 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/work/qemux86_64-poky-linux/linu >>> x-yocto/4.10.9+gitAUTOINC+ad2e885015_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, >>> >>>
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
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-selftest/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-selftest/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-selftest/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-selftest/build/build/tmp/work/qemux86-poky-linux/linux-yocto/4.10.9+git999-r0/temp/log.do_kernel_metadata.37215) Ross On 25 April 2017 at 14:17, Bruce Ashfieldwrote: > > > On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie < > richard.pur...@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 >> > wrote: >> > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: >> > > > >> > > > >> > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > > > mail >> > > > .com> wrote: >> > > > > >> > > > > >> > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > > > 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/work/qemux86_64-poky-linux/linu >> x-yocto/4.10.9+gitAUTOINC+ad2e885015_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" > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdiewrote: > On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote: > > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie > > wrote: > > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > > mail > > > > .com> wrote: > > > > > > > > > > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > > 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/work/qemux86_64-poky-linux/linu > x-yocto/4.10.9+gitAUTOINC+ad2e885015_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" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote: > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie >wrote: > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > mail > > > .com> wrote: > > > > > > > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > 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: $ 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/work/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726) ERROR: Logfile of failure stored in: /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e885015_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/work/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726) Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie < richard.pur...@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> .com> wrote: > > > > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > > om> wrote: > > > > I'm still seeing this with your "kernel-yocto/kern-tools: fix > > > > do_validate_branches clean stage" patch applied: > > > > > > > > > > > > | DEBUG: Executing shell function do_patch > > > > | ERROR: Could not apply patches for qemux86. > > > > | ERROR: Patch failures can be resolved in the linux source > > > > directory work-shared/qemux86/kernel-source) > > > > | > > > > | [ERROR] Can't find patch dir at .kernel-meta/ > > > > | usage: kgit s2q > > > > | ERROR: Function failed: do_patch (log file is located at linux- > > > > yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d- > > > > r0/temp/log.do_patch.44497) > > > > NOTE: recipe linux-yocto- > > > > 1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_patch: > > > > Failed > > > > > > > Well bugger. > > > > > > I'll start another set of builds. > > > > > I had this on a build loop all day without any luck. I also enlisted > > a few others around the office > > to build master and see if they could cause an issue .. again, no > > luck. > > > > 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. Bruce gmail garbled and and paste below: --- % git describe v4.10.9-378-gff739b66b0bc % git whatchanged commit ff739b66b0bc5cd65bcc26d4556736309f4b180c Author: Bruce Ashfield Date: Fri Jul 8 11:32:11 2016 -0400 makefile: comment two Signed-off-by: Bruce Ashfield :100644 100644 a027ca58d9ff... 2402e34170b5... MMakefile commit 238fd7383ebb99f080febdfb31d680b43fbb7438 Author: Bruce Ashfield Date: Fri Jul 8 11:31:34 2016 -0400 makefile: comment one Signed-off-by: Bruce Ashfield :100644 100644 3d994e6df89a... a027ca58d9ff... MMakefile commit 5376026f981849bee7d1789c67b81e1e758ef6f0 Author: invalid_git config Date: Mon Apr 24 20:48:24 2017 -0400 The kernel makes the assumption that all PT_LOAD sections are continous, at least to the point where PT_PHDR is contained. If there are holes between the PT_LOAD sections, the calculation load_addr + exec->e_phoff fails to correctly locate the phdrs. This change notices where phdrs are located in some other PT_LOAD section other than the first one and corrects the offsets used. This is useful where userspace wants to rewrite elf files but can't guarantee that all PT_LOAD sections are continuous without holes without potentially creating large holes in the binaries. I was unable to find any ELF spec which requires continuous PT_LOAD sections or that PT_PHDR be in the first PT_LOAD section. Signed-off-by: Richard Purdie :100644 100644 422370293cfd... 392dab375b63... Mfs/binfmt_elf.c --- > > Cheers, > > Richard > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield.com> wrote: > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > om> wrote: > > > I'm still seeing this with your "kernel-yocto/kern-tools: fix > > > do_validate_branches clean stage" patch applied: > > > > > > > > > | DEBUG: Executing shell function do_patch > > > | ERROR: Could not apply patches for qemux86. > > > | ERROR: Patch failures can be resolved in the linux source > > > directory work-shared/qemux86/kernel-source) > > > | > > > | [ERROR] Can't find patch dir at .kernel-meta/ > > > | usage: kgit s2q > > > | ERROR: Function failed: do_patch (log file is located at linux- > > > yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d- > > > r0/temp/log.do_patch.44497) > > > NOTE: recipe linux-yocto- > > > 1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_patch: > > > Failed > > > > > Well bugger. > > > > I'll start another set of builds. > > > I had this on a build loop all day without any luck. I also enlisted > a few others around the office > to build master and see if they could cause an issue .. again, no > luck. > > 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. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Mon, Apr 24, 2017 at 4:05 PM, Martin Jansawrote: > > 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 ? > > One of the layers has linux-yocto_4.10.bbappend with 4 added .cfg files > and one .patch file. Maybe that could influence do_patch behavior. > cool. I'll add that as well. I've been running with an extra patch in my config since that is something that Richard had in the past to trigger it. But I'll start adding some more patches and configs to see if I can trigger it. Bruce > > On Mon, Apr 24, 2017 at 9:56 PM, Bruce Ashfield > wrote: > >> >> >> On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > > wrote: >> >>> >>> >>> On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa >>> wrote: >>> I'm still seeing this with your "kernel-yocto/kern-tools: fix do_validate_branches clean stage" patch applied: | DEBUG: Executing shell function do_patch | ERROR: Could not apply patches for qemux86. | ERROR: Patch failures can be resolved in the linux source directory work-shared/qemux86/kernel-source) | | [ERROR] Can't find patch dir at .kernel-meta/ | usage: kgit s2q | ERROR: Function failed: do_patch (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.44497) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_patch: Failed >>> Well bugger. >>> >>> I'll start another set of builds. >>> >> >> I had this on a build loop all day without any luck. I also enlisted a >> few others around the office >> to build master and see if they could cause an issue .. again, no luck. >> >> 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 ? >> >> Bruce >> >> >>> >>> Bruce >>> >>> On Sat, Apr 22, 2017 at 6:39 AM, Bruce Ashfield < bruce.ashfi...@gmail.com> wrote: > > > On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield < > bruce.ashfi...@gmail.com> wrote: > >> >> >> On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield < >> bruce.ashfi...@gmail.com> wrote: >> >>> >>> >>> On Fri, Apr 21, 2017 at 11:55 AM, akuster808 >>> wrote: >>> On 04/21/2017 01:36 AM, Martin Jansa wrote: Anyone else seeing this as well? yes >>> >>> If you see it, can you take a look at the linux source dir and see >>> if the directories are >>> present ? >>> >>> I've been doing a tight loop on builds all day, and haven't seen >>> this yet. >>> >>> Nothing has changed with the build process in months, so something >>> else underneath >>> is now causing this race/issue. >>> >>> >> I finally managed to make this happen. >> >> Thanks for the report .. I can now spin a fix. >> > > I'm no longer able to trigger the error, and I sent the patch to the > list. > > Hopefully this never comes back .. but if anyone does see it after > applying that patch, let me know. > > Cheers, > > Bruce > > >> >> Cheers, >> >> Bruce >> >> >>> Bruce >>> >>> - armin I've updated to oe-core commit: c6cd5865b6914521a841ae0c9f4e2bcda99beff2 from some revision maybe 20-40 commits older and now I'm seeing: ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_validate_branches: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) ERROR: Logfile of failure stored in: linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 Log data follows: | DEBUG: Executing shell function do_validate_branches | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base | mkdir: cannot create directory ‘.’: File exists | | [ERROR] Can't find patch dir at ./patches/standard/base | usage: kgit s2q | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_validate_branches: Failed ERROR: Task
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
> 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 ? One of the layers has linux-yocto_4.10.bbappend with 4 added .cfg files and one .patch file. Maybe that could influence do_patch behavior. On Mon, Apr 24, 2017 at 9:56 PM, Bruce Ashfieldwrote: > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > wrote: > >> >> >> On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa >> wrote: >> >>> I'm still seeing this with your "kernel-yocto/kern-tools: fix >>> do_validate_branches clean stage" patch applied: >>> >>> >>> | DEBUG: Executing shell function do_patch >>> | ERROR: Could not apply patches for qemux86. >>> | ERROR: Patch failures can be resolved in the linux source directory >>> work-shared/qemux86/kernel-source) >>> | >>> | [ERROR] Can't find patch dir at .kernel-meta/ >>> | usage: kgit s2q >>> | ERROR: Function failed: do_patch (log file is located at >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.44497) >>> NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task >>> do_patch: Failed >>> >>> >> Well bugger. >> >> I'll start another set of builds. >> > > I had this on a build loop all day without any luck. I also enlisted a few > others around the office > to build master and see if they could cause an issue .. again, no luck. > > 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 ? > > Bruce > > >> >> Bruce >> >> >>> >>> On Sat, Apr 22, 2017 at 6:39 AM, Bruce Ashfield < >>> bruce.ashfi...@gmail.com> wrote: >>> On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield < bruce.ashfi...@gmail.com> wrote: > > > On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield < > bruce.ashfi...@gmail.com> wrote: > >> >> >> On Fri, Apr 21, 2017 at 11:55 AM, akuster808 >> wrote: >> >>> >>> >>> On 04/21/2017 01:36 AM, Martin Jansa wrote: >>> >>> Anyone else seeing this as well? >>> >>> >>> yes >>> >> >> If you see it, can you take a look at the linux source dir and see if >> the directories are >> present ? >> >> I've been doing a tight loop on builds all day, and haven't seen >> this yet. >> >> Nothing has changed with the build process in months, so something >> else underneath >> is now causing this race/issue. >> >> > I finally managed to make this happen. > > Thanks for the report .. I can now spin a fix. > I'm no longer able to trigger the error, and I sent the patch to the list. Hopefully this never comes back .. but if anyone does see it after applying that patch, let me know. Cheers, Bruce > > Cheers, > > Bruce > > >> Bruce >> >> >>> >>> - armin >>> >>> I've updated to oe-core commit: >>> >>> c6cd5865b6914521a841ae0c9f4e2bcda99beff2 >>> >>> from some revision maybe 20-40 commits older and now I'm seeing: >>> >>> ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 >>> do_validate_branches: Function failed: do_validate_branches (log file >>> is located at >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >>> ERROR: Logfile of failure stored in: >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 >>> Log data follows: >>> | DEBUG: Executing shell function do_validate_branches >>> | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base >>> | mkdir: cannot create directory ‘.’: File exists >>> | >>> | [ERROR] Can't find patch dir at ./patches/standard/base >>> | usage: kgit s2q >>> | WARNING: exit code 1 from a shell command. >>> | ERROR: Function failed: do_validate_branches (log file is located at >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >>> NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: >>> task do_validate_branches: Failed >>> ERROR: Task >>> (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) >>> failed with exit code '1' >>> >>> >>> >>> >>> >>> -- >>> ___ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >>> >>> >> >> >> -- >> "Thou shalt not follow the NULL pointer, for chaos and madness await >> thee
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfieldwrote: > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > wrote: > >> I'm still seeing this with your "kernel-yocto/kern-tools: fix >> do_validate_branches clean stage" patch applied: >> >> >> | DEBUG: Executing shell function do_patch >> | ERROR: Could not apply patches for qemux86. >> | ERROR: Patch failures can be resolved in the linux source directory >> work-shared/qemux86/kernel-source) >> | >> | [ERROR] Can't find patch dir at .kernel-meta/ >> | usage: kgit s2q >> | ERROR: Function failed: do_patch (log file is located at >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.44497) >> NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task >> do_patch: Failed >> >> > Well bugger. > > I'll start another set of builds. > I had this on a build loop all day without any luck. I also enlisted a few others around the office to build master and see if they could cause an issue .. again, no luck. 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 ? Bruce > > Bruce > > >> >> On Sat, Apr 22, 2017 at 6:39 AM, Bruce Ashfield > > wrote: >> >>> >>> >>> On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield < >>> bruce.ashfi...@gmail.com> wrote: >>> On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield < bruce.ashfi...@gmail.com> wrote: > > > On Fri, Apr 21, 2017 at 11:55 AM, akuster808 > wrote: > >> >> >> On 04/21/2017 01:36 AM, Martin Jansa wrote: >> >> Anyone else seeing this as well? >> >> >> yes >> > > If you see it, can you take a look at the linux source dir and see if > the directories are > present ? > > I've been doing a tight loop on builds all day, and haven't seen this > yet. > > Nothing has changed with the build process in months, so something > else underneath > is now causing this race/issue. > > I finally managed to make this happen. Thanks for the report .. I can now spin a fix. >>> >>> I'm no longer able to trigger the error, and I sent the patch to the >>> list. >>> >>> Hopefully this never comes back .. but if anyone does see it after >>> applying that patch, let me know. >>> >>> Cheers, >>> >>> Bruce >>> >>> Cheers, Bruce > Bruce > > >> >> - armin >> >> I've updated to oe-core commit: >> >> c6cd5865b6914521a841ae0c9f4e2bcda99beff2 >> >> from some revision maybe 20-40 commits older and now I'm seeing: >> >> ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 >> do_validate_branches: Function failed: do_validate_branches (log file is >> located at >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >> ERROR: Logfile of failure stored in: >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 >> Log data follows: >> | DEBUG: Executing shell function do_validate_branches >> | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base >> | mkdir: cannot create directory ‘.’: File exists >> | >> | [ERROR] Can't find patch dir at ./patches/standard/base >> | usage: kgit s2q >> | WARNING: exit code 1 from a shell command. >> | ERROR: Function failed: do_validate_branches (log file is located at >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >> NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: >> task do_validate_branches: Failed >> ERROR: Task >> (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) >> failed with exit code '1' >> >> >> >> >> >> -- >> ___ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> >> > > > -- > "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" >>> >> >> > > > -- > "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" -- ___ Openembedded-core mailing list
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansawrote: > I'm still seeing this with your "kernel-yocto/kern-tools: fix > do_validate_branches clean stage" patch applied: > > > | DEBUG: Executing shell function do_patch > | ERROR: Could not apply patches for qemux86. > | ERROR: Patch failures can be resolved in the linux source directory > work-shared/qemux86/kernel-source) > | > | [ERROR] Can't find patch dir at .kernel-meta/ > | usage: kgit s2q > | ERROR: Function failed: do_patch (log file is located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.44497) > NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task > do_patch: Failed > > Well bugger. I'll start another set of builds. Bruce > > On Sat, Apr 22, 2017 at 6:39 AM, Bruce Ashfield > wrote: > >> >> >> On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield > > wrote: >> >>> >>> >>> On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield < >>> bruce.ashfi...@gmail.com> wrote: >>> On Fri, Apr 21, 2017 at 11:55 AM, akuster808 wrote: > > > On 04/21/2017 01:36 AM, Martin Jansa wrote: > > Anyone else seeing this as well? > > > yes > If you see it, can you take a look at the linux source dir and see if the directories are present ? I've been doing a tight loop on builds all day, and haven't seen this yet. Nothing has changed with the build process in months, so something else underneath is now causing this race/issue. >>> I finally managed to make this happen. >>> >>> Thanks for the report .. I can now spin a fix. >>> >> >> I'm no longer able to trigger the error, and I sent the patch to the list. >> >> Hopefully this never comes back .. but if anyone does see it after >> applying that patch, let me know. >> >> Cheers, >> >> Bruce >> >> >>> >>> Cheers, >>> >>> Bruce >>> >>> Bruce > > - armin > > I've updated to oe-core commit: > > c6cd5865b6914521a841ae0c9f4e2bcda99beff2 > > from some revision maybe 20-40 commits older and now I'm seeing: > > ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 > do_validate_branches: Function failed: do_validate_branches (log file is > located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) > ERROR: Logfile of failure stored in: > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 > Log data follows: > | DEBUG: Executing shell function do_validate_branches > | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base > | mkdir: cannot create directory ‘.’: File exists > | > | [ERROR] Can't find patch dir at ./patches/standard/base > | usage: kgit s2q > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_validate_branches (log file is located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) > NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: > task do_validate_branches: Failed > ERROR: Task > (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) > failed with exit code '1' > > > > > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > -- "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" >> > > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
I'm still seeing this with your "kernel-yocto/kern-tools: fix do_validate_branches clean stage" patch applied: | DEBUG: Executing shell function do_patch | ERROR: Could not apply patches for qemux86. | ERROR: Patch failures can be resolved in the linux source directory work-shared/qemux86/kernel-source) | | [ERROR] Can't find patch dir at .kernel-meta/ | usage: kgit s2q | ERROR: Function failed: do_patch (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.44497) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_patch: Failed On Sat, Apr 22, 2017 at 6:39 AM, Bruce Ashfieldwrote: > > > On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield > wrote: > >> >> >> On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield > > wrote: >> >>> >>> >>> On Fri, Apr 21, 2017 at 11:55 AM, akuster808 >>> wrote: >>> On 04/21/2017 01:36 AM, Martin Jansa wrote: Anyone else seeing this as well? yes >>> >>> If you see it, can you take a look at the linux source dir and see if >>> the directories are >>> present ? >>> >>> I've been doing a tight loop on builds all day, and haven't seen this >>> yet. >>> >>> Nothing has changed with the build process in months, so something else >>> underneath >>> is now causing this race/issue. >>> >>> >> I finally managed to make this happen. >> >> Thanks for the report .. I can now spin a fix. >> > > I'm no longer able to trigger the error, and I sent the patch to the list. > > Hopefully this never comes back .. but if anyone does see it after > applying that patch, let me know. > > Cheers, > > Bruce > > >> >> Cheers, >> >> Bruce >> >> >>> Bruce >>> >>> - armin I've updated to oe-core commit: c6cd5865b6914521a841ae0c9f4e2bcda99beff2 from some revision maybe 20-40 commits older and now I'm seeing: ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_validate_branches: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) ERROR: Logfile of failure stored in: linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 Log data follows: | DEBUG: Executing shell function do_validate_branches | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base | mkdir: cannot create directory ‘.’: File exists | | [ERROR] Can't find patch dir at ./patches/standard/base | usage: kgit s2q | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_validate_branches: Failed ERROR: Task (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) failed with exit code '1' -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core >>> >>> >>> -- >>> "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" > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfieldwrote: > > > On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield > wrote: > >> >> >> On Fri, Apr 21, 2017 at 11:55 AM, akuster808 >> wrote: >> >>> >>> >>> On 04/21/2017 01:36 AM, Martin Jansa wrote: >>> >>> Anyone else seeing this as well? >>> >>> >>> yes >>> >> >> If you see it, can you take a look at the linux source dir and see if the >> directories are >> present ? >> >> I've been doing a tight loop on builds all day, and haven't seen this >> yet. >> >> Nothing has changed with the build process in months, so something else >> underneath >> is now causing this race/issue. >> >> > I finally managed to make this happen. > > Thanks for the report .. I can now spin a fix. > I'm no longer able to trigger the error, and I sent the patch to the list. Hopefully this never comes back .. but if anyone does see it after applying that patch, let me know. Cheers, Bruce > > Cheers, > > Bruce > > >> Bruce >> >> >>> >>> - armin >>> >>> I've updated to oe-core commit: >>> >>> c6cd5865b6914521a841ae0c9f4e2bcda99beff2 >>> >>> from some revision maybe 20-40 commits older and now I'm seeing: >>> >>> ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 >>> do_validate_branches: Function failed: do_validate_branches (log file is >>> located at >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >>> ERROR: Logfile of failure stored in: >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 >>> Log data follows: >>> | DEBUG: Executing shell function do_validate_branches >>> | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base >>> | mkdir: cannot create directory ‘.’: File exists >>> | >>> | [ERROR] Can't find patch dir at ./patches/standard/base >>> | usage: kgit s2q >>> | WARNING: exit code 1 from a shell command. >>> | ERROR: Function failed: do_validate_branches (log file is located at >>> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >>> NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task >>> do_validate_branches: Failed >>> ERROR: Task >>> (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) >>> failed with exit code '1' >>> >>> >>> >>> >>> >>> -- >>> ___ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >>> >>> >> >> >> -- >> "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" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfieldwrote: > > > On Fri, Apr 21, 2017 at 11:55 AM, akuster808 wrote: > >> >> >> On 04/21/2017 01:36 AM, Martin Jansa wrote: >> >> Anyone else seeing this as well? >> >> >> yes >> > > If you see it, can you take a look at the linux source dir and see if the > directories are > present ? > > I've been doing a tight loop on builds all day, and haven't seen this yet. > > Nothing has changed with the build process in months, so something else > underneath > is now causing this race/issue. > > I finally managed to make this happen. Thanks for the report .. I can now spin a fix. Cheers, Bruce > Bruce > > >> >> - armin >> >> I've updated to oe-core commit: >> >> c6cd5865b6914521a841ae0c9f4e2bcda99beff2 >> >> from some revision maybe 20-40 commits older and now I'm seeing: >> >> ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 >> do_validate_branches: Function failed: do_validate_branches (log file is >> located at >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >> ERROR: Logfile of failure stored in: >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 >> Log data follows: >> | DEBUG: Executing shell function do_validate_branches >> | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base >> | mkdir: cannot create directory ‘.’: File exists >> | >> | [ERROR] Can't find patch dir at ./patches/standard/base >> | usage: kgit s2q >> | WARNING: exit code 1 from a shell command. >> | ERROR: Function failed: do_validate_branches (log file is located at >> linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) >> NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task >> do_validate_branches: Failed >> ERROR: Task >> (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) >> failed with exit code '1' >> >> >> >> >> >> -- >> ___ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> >> > > > -- > "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" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 11:55 AM, akuster808wrote: > > > On 04/21/2017 01:36 AM, Martin Jansa wrote: > > Anyone else seeing this as well? > > > yes > If you see it, can you take a look at the linux source dir and see if the directories are present ? I've been doing a tight loop on builds all day, and haven't seen this yet. Nothing has changed with the build process in months, so something else underneath is now causing this race/issue. Bruce > > - armin > > I've updated to oe-core commit: > > c6cd5865b6914521a841ae0c9f4e2bcda99beff2 > > from some revision maybe 20-40 commits older and now I'm seeing: > > ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 > do_validate_branches: Function failed: do_validate_branches (log file is > located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) > ERROR: Logfile of failure stored in: > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 > Log data follows: > | DEBUG: Executing shell function do_validate_branches > | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base > | mkdir: cannot create directory ‘.’: File exists > | > | [ERROR] Can't find patch dir at ./patches/standard/base > | usage: kgit s2q > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_validate_branches (log file is located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) > NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task > do_validate_branches: Failed > ERROR: Task > (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) > failed with exit code '1' > > > > > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On 04/21/2017 01:36 AM, Martin Jansa wrote: Anyone else seeing this as well? yes - armin I've updated to oe-core commit: c6cd5865b6914521a841ae0c9f4e2bcda99beff2 from some revision maybe 20-40 commits older and now I'm seeing: ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_validate_branches: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) ERROR: Logfile of failure stored in: linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 Log data follows: | DEBUG: Executing shell function do_validate_branches | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base | mkdir: cannot create directory ‘.’: File exists | | [ERROR] Can't find patch dir at ./patches/standard/base | usage: kgit s2q | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_validate_branches: Failed ERROR: Task (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) failed with exit code '1' -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 9:44 AM, Martin Jansawrote: > On Fri, Apr 21, 2017 at 08:39:33AM -0400, Bruce Ashfield wrote: > > On Fri, Apr 21, 2017 at 8:36 AM, Alexander Kanavin < > > alexander.kana...@linux.intel.com> wrote: > > > > > On 04/21/2017 03:26 PM, Bruce Ashfield wrote: > > > > > > Anyone else seeing this as well? > > >> > > >> > > >> > > >> Richard saw this once last week, and we weren't able to reproduce it. > > >> I've just updated > > >> and am doing builds now. > > >> > > >> If anyone has info on their config, build steps, etc, I'm interested > to > > >> hear so I can figure > > >> out what is going on. > > >> > > > > > > I saw this once as well today. I nuked tmp/ and it was gone. > > > > > > > Interesting. I'm updating my existing build (I only ever have one that I > > constantly update and re-use), so maybe it'll show up in that existing > tmp > > dir. > > > > If there's a clean/rebuild cycle that was in play, let me know as well, > > since I'll try that as well. > > > > I've been carrying a config like Richard was using since last week and > > in all my builds it has never happened. > > I've seen it 4 times already in various builds executed today and > yesterday. All of them were incremental. > > Last failure was a bit different and failed in do_patch already (maybe > some race-condition between do_patch and do_validate_branches? > Could be. I've got my kernel builds running in a loop now. Maybe my builder is too slow to expose it .. but it can't hide from me forever. I'll start looking into the code while I wait for my build to explode. Cheers, Bruce > > ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_patch: > Could not apply patches for qemux86. > ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_patch: > Patch failures can be resolved in the linux source directory > work-shared/qemux86/kernel-source) > ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_patch: > Function failed: do_patch (log file is located at linux-yocto/1_4.10.9+ > gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.25077) > ERROR: Logfile of failure stored in: linux-yocto/1_4.10.9+ > gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.25077 > Log data follows: > | DEBUG: Executing python function extend_recipe_sysroot > | NOTE: Direct dependencies are ['meta/recipes-devtools/quilt/ > quilt-native_0.65.bb:do_populate_sysroot', 'meta/recipes-kernel/kern- > tools/kern-tools-native_git.bb:do_populate_sysroot'] > | NOTE: Considering setscene task: ['icecc-create-env-native', > 'do_populate_sysroot'] > | considering dependency: ['quilt-native', 'do_populate_sysroot'] > | Adding dependency on icecc-create-env-native > | NOTE: quilt-native exists in sysroot, skipping > | NOTE: kern-tools-native exists in sysroot, skipping > | NOTE: icecc-create-env-native exists in sysroot, skipping > | DEBUG: Python function extend_recipe_sysroot finished > | DEBUG: Executing shell function do_patch > | ERROR: Could not apply patches for qemux86. > | ERROR: Patch failures can be resolved in the linux source directory > work-shared/qemux86/kernel-source) > | > | [ERROR] Can't find patch dir at .kernel-meta/ > | usage: kgit s2q > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_patch (log file is located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_ > patch.25077) > NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: > task do_patch: Failed > ERROR: Task (meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_patch) > failed with exit code '1' > > > > > Bruce > > > > > > > > > > Alex > > > > > > > > > -- > > > ___ > > > Openembedded-core mailing list > > > Openembedded-core@lists.openembedded.org > > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > > > > > > > > > -- > > "Thou shalt not follow the NULL pointer, for chaos and madness await thee > > at its end" > > > -- > > ___ > > Openembedded-core mailing list > > Openembedded-core@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > -- > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 08:39:33AM -0400, Bruce Ashfield wrote: > On Fri, Apr 21, 2017 at 8:36 AM, Alexander Kanavin < > alexander.kana...@linux.intel.com> wrote: > > > On 04/21/2017 03:26 PM, Bruce Ashfield wrote: > > > > Anyone else seeing this as well? > >> > >> > >> > >> Richard saw this once last week, and we weren't able to reproduce it. > >> I've just updated > >> and am doing builds now. > >> > >> If anyone has info on their config, build steps, etc, I'm interested to > >> hear so I can figure > >> out what is going on. > >> > > > > I saw this once as well today. I nuked tmp/ and it was gone. > > > > Interesting. I'm updating my existing build (I only ever have one that I > constantly update and re-use), so maybe it'll show up in that existing tmp > dir. > > If there's a clean/rebuild cycle that was in play, let me know as well, > since I'll try that as well. > > I've been carrying a config like Richard was using since last week and > in all my builds it has never happened. I've seen it 4 times already in various builds executed today and yesterday. All of them were incremental. Last failure was a bit different and failed in do_patch already (maybe some race-condition between do_patch and do_validate_branches? ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_patch: Could not apply patches for qemux86. ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_patch: Patch failures can be resolved in the linux source directory work-shared/qemux86/kernel-source) ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_patch: Function failed: do_patch (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.25077) ERROR: Logfile of failure stored in: linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.25077 Log data follows: | DEBUG: Executing python function extend_recipe_sysroot | NOTE: Direct dependencies are ['meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot', 'meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:do_populate_sysroot'] | NOTE: Considering setscene task: ['icecc-create-env-native', 'do_populate_sysroot'] | considering dependency: ['quilt-native', 'do_populate_sysroot'] | Adding dependency on icecc-create-env-native | NOTE: quilt-native exists in sysroot, skipping | NOTE: kern-tools-native exists in sysroot, skipping | NOTE: icecc-create-env-native exists in sysroot, skipping | DEBUG: Python function extend_recipe_sysroot finished | DEBUG: Executing shell function do_patch | ERROR: Could not apply patches for qemux86. | ERROR: Patch failures can be resolved in the linux source directory work-shared/qemux86/kernel-source) | | [ERROR] Can't find patch dir at .kernel-meta/ | usage: kgit s2q | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_patch (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_patch.25077) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_patch: Failed ERROR: Task (meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_patch) failed with exit code '1' > > Bruce > > > > > > Alex > > > > > > -- > > ___ > > Openembedded-core mailing list > > Openembedded-core@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await thee > at its end" > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 8:36 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 04/21/2017 03:26 PM, Bruce Ashfield wrote: > > Anyone else seeing this as well? >> >> >> >> Richard saw this once last week, and we weren't able to reproduce it. >> I've just updated >> and am doing builds now. >> >> If anyone has info on their config, build steps, etc, I'm interested to >> hear so I can figure >> out what is going on. >> > > I saw this once as well today. I nuked tmp/ and it was gone. > Interesting. I'm updating my existing build (I only ever have one that I constantly update and re-use), so maybe it'll show up in that existing tmp dir. If there's a clean/rebuild cycle that was in play, let me know as well, since I'll try that as well. I've been carrying a config like Richard was using since last week and in all my builds it has never happened. Bruce > > Alex > > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On 04/21/2017 03:26 PM, Bruce Ashfield wrote: Anyone else seeing this as well? Richard saw this once last week, and we weren't able to reproduce it. I've just updated and am doing builds now. If anyone has info on their config, build steps, etc, I'm interested to hear so I can figure out what is going on. I saw this once as well today. I nuked tmp/ and it was gone. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update
On Fri, Apr 21, 2017 at 4:36 AM, Martin Jansawrote: > Anyone else seeing this as well? > > > Richard saw this once last week, and we weren't able to reproduce it. I've just updated and am doing builds now. If anyone has info on their config, build steps, etc, I'm interested to hear so I can figure out what is going on. Bruce > I've updated to oe-core commit: > > c6cd5865b6914521a841ae0c9f4e2bcda99beff2 > > from some revision maybe 20-40 commits older and now I'm seeing: > > > ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 > do_validate_branches: Function failed: do_validate_branches (log file is > located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) > ERROR: Logfile of failure stored in: > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 > Log data follows: > | DEBUG: Executing shell function do_validate_branches > | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base > | mkdir: cannot create directory ‘.’: File exists > | > | [ERROR] Can't find patch dir at ./patches/standard/base > | usage: kgit s2q > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_validate_branches (log file is located at > linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) > NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task > do_validate_branches: Failed > ERROR: Task > (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) > failed with exit code '1' > > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] linux-yocto.do_validate_branches failing since last oe-core update
Anyone else seeing this as well? I've updated to oe-core commit: c6cd5865b6914521a841ae0c9f4e2bcda99beff2 from some revision maybe 20-40 commits older and now I'm seeing: ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_validate_branches: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) ERROR: Logfile of failure stored in: linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385 Log data follows: | DEBUG: Executing shell function do_validate_branches | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base | mkdir: cannot create directory ‘.’: File exists | | [ERROR] Can't find patch dir at ./patches/standard/base | usage: kgit s2q | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at linux-yocto/1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.5385) NOTE: recipe linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0: task do_validate_branches: Failed ERROR: Task (oe-core/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_validate_branches) failed with exit code '1' -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core