> 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 Ashfield <bruce.ashfield@gmail.com> wrote:


On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:


On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa <martin.jansa@gmail.com> 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.ashfield@gmail.com> wrote:


On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:


On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:


On Fri, Apr 21, 2017 at 11:55 AM, akuster808 <akuster808@gmail.com> 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"