**** BEGIN LOGGING AT Fri Nov 24 03:00:03 2017 Nov 24 07:41:26 Morning! Nov 24 08:42:52 Mornign! Nov 24 17:26:39 so, i'm taking a few minutes to try and diagnose where bitbake is failing in WSL when run on the Windows drive mounts instead of the Linux drive mounts .. it is just *halted* at "Initialising tasks: 100% |############...| Time: 0:00:01 Nov 24 17:26:48 any idea how to get an idea of where it's stuck at ? Nov 24 17:33:46 meanwhile, i'm going to let it spin for a couple hours and see if it eventually gets through it. ps axfww indicates bitbake spawn bitbake spawned bitbake-worker and seems to be doing nothing Nov 24 17:35:22 oh, running top I find a process called "Cooker" running at 800% CPU Nov 24 18:28:13 Morning! Nov 24 18:43:02 howdy Herrie Nov 24 18:51:22 Howdy folks Nov 24 18:55:44 howdy ka6sox Nov 24 18:56:04 hiya EricBlade ...how goes? Nov 24 18:59:40 going alright.. takign a few minutes to poke WSL with a stick and see if I can figure out why bitbake halts on it when using Windows drives . . . i should probably take the lower hanging fruit and see if I can figure out a way to fix linux-libc-headers .. but i wanted to file a bug report on this if i could figure out the reason Nov 24 19:01:12 :( Nov 24 19:01:51 i'm clueless though. it looks like some process called Cooker is just burning up CPU and not doing anything, and i don't know how to look inside it to see what's happening Nov 24 19:03:28 sucks Nov 24 19:10:36 EricBlade: Why you're so much trying WSL? Nov 24 19:10:47 If Linux doesn't work you could do VBOX or VMWare? Nov 24 19:14:09 i just want to get the bugs figured out and filed so that it'll get fixed Nov 24 19:15:35 if not for the disk I/O on WSL being quite slower than native, it'd be quite nice to be able to utilize the full resources of the machine, without a VM. but I think they'll have the disk I/O mostly worked out in the next major release Nov 24 20:40:59 EricBlade: OK, you're on insider build I assume? Nov 24 23:14:36 Herrie: not right at the moment, but i do have a test laptop that is. i'm hoping to gain some insight into what the problem is with the Cooker process to report it in the most recent major, so it will hopefully get fixed for the next major Nov 24 23:15:16 we already know what the root of the problem is with linux-libc-headers.bb, but not what actually causes it. . (that package fails the packaging process . . ) Nov 24 23:15:58 and we know that's probably not going to get fixed in the next major, so if it's possible to fix it in the recipe or the package itself, then i'd like to find that Nov 24 23:17:39 what i probably need to do is knock bitbake and make down to single threading, and then run strace on it, so that i can see exactly what it's doing. it's holding some file open inside the package tree, at the time when it tries to move the package tree over to the target directory Nov 25 02:15:11 whoa. looks like it's a race condition that prevents that package from working. i ran the build with double the normal number of make processes to try and get all the dependencies built fastfasto n this machine, so i could get it to fail faster... Nov 25 02:15:26 and i'm about 800 tasks beyond that now **** ENDING LOGGING AT Sat Nov 25 03:00:01 2017