Re: [OE-core] [pseudo][PATCH] Fix to fcntl guts to ignore flags that can be ORed into cmd

2017-09-16 Thread Seebs
On Sat, 16 Sep 2017 02:22:01 + Will Page wrote: > Thanks, Ross. > > I had contacted the maintainer off list to ask where I should submit > my patch. I may have misunderstood his reply. No, I'm just confused, because I'm not really otherwise active in yocto/oe-core these days, I just still

Re: [OE-core] State of bitbake world, Failed tasks 2017-09-14

2017-09-16 Thread Khem Raj
On Sat, Sep 16, 2017 at 7:41 AM, Martin Jansa wrote: > Just the commit IDs from the top won't be very useful, because it's from > jansa/master branches which are rebased even more often than master-next. > > If you really want to see them, then there are links to the build logs for > each MACHINE

Re: [OE-core] State of bitbake world, Failed tasks 2017-09-14

2017-09-16 Thread Martin Jansa
Just the commit IDs from the top won't be very useful, because it's from jansa/master branches which are rebased even more often than master-next. If you really want to see them, then there are links to the build logs for each MACHINE and you can see the build configuration there. That's why at t

Re: [OE-core] State of bitbake world, Failed tasks 2017-09-14

2017-09-16 Thread Khem Raj
On Sat, Sep 16, 2017 at 2:00 AM, Martin Jansa wrote: > Probably is, qemux86 was built from slightly older metadata, so probably > including previous versions of your klibc changes. > > I know it's confusing in the report, but still each build takes around 24 > hours per machine and I have only 2 b

Re: [OE-core] State of bitbake world, Failed tasks 2017-09-14

2017-09-16 Thread Martin Jansa
Probably is, qemux86 was built from slightly older metadata, so probably including previous versions of your klibc changes. I know it's confusing in the report, but still each build takes around 24 hours per machine and I have only 2 builders. e.g. this qemux86 build was started 20170912_234104