Investigating a hung job on the autobuilder We've yet another hung job on the autobuilder. I thought I'd write down what I did to investigate it so others can learn how to do it and so I can remember

The AGL file[1] appears to have another entry in it for FallbackTimeservers. It is also complicated by oe-core only doing this for qemu* machines. I'm not sure a single variable is going to work well.

Hi Jan-Simon/Scott, The attached change is going to break meta-agl: https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/1032 I think what OE-Core plans to do with a config file isn't un

Hi, We saw an LTP image failure today: https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/2937 It was in the contoller tests (cgroup ones). I logged in and was able to grab the backtrac

Hi, We saw a failure in qemux86-64-ltp on fedora35-ty-2: https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/2905 I saved the logs here: https://autobuilder.yocto.io/pub/failed-builds-da

After the discussion in triage I tried to test some of the theories mentioned on the call. There was this failed build: https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3169/steps/14/

Just to save some time, for whoever is triaging the currently failing master- next build, I added a change to bitbake which shows errors for questionable git url usage. This appears to: * show errors

Hi Richard, I hate to be the bearer of bad news but there is a bit of an issue with meta-aws and it may be more serious then we originally thought. I've been trying to fix some fetcher issues and came

I did already talk with Scott Murray and there are patches ready for this. I think meta-aws was ok? Cheers, Richard

It may be a deliberate choice but I suspect there are some issues you aren't considering, specifically: a) it breaks anyone doing offline builds b) it means source archives don't function correct c) i

wrote: I did just have a look at the aws-c-iot recipes: https://git.yoctoproject.org/meta-aws/tree/recipes-sdk/aws-c-iot/aws-c-iot_0.0.2.bb https://git.yoctoproject.org/meta-aws/tree/recipes-sdk/aws-c

qemux86 didn't shutdown 120s on ubuntu1804-ty-3 https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/4421 showed an rcu stall in the kernel logs cat pokybuild@ubuntu1804-ty-3:~/yocto-work

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2808 2060878 ? S 3:51 bitbake-server /home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/bin/bitbake-server decafbad 3 5 /ho

We have another hung build: https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2805 [pokybuild@centos8-ty-1 ~]$ pstree -p 3610382 Worker(3610382)─┬─linux-yocto:com(3686989)───run.do_com

wrote: Sending an ECHLD (sig 17) to the process had it exit and start building again. Logs show it was stuck in wic.Wic.test_bootloader_config. That means it could be the above bug and something got m

wrote: This was on centos8-ty-2. gdb -p 909354 GNU gdb (GDB) Red Hat Enterprise Linux 8.2-16.el8 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gn

I noticed: https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2779 has hung. Since this will be gone by the time anyone looks, inspection on the system suggests it is hung in perl do_co

wrote: Not sure if this means anything or not (run on centos7-ty-4 for around 10 mins): -bash-4.2$ while true; do ping typhoon.yocto.io -c 1 > /dev/null || date; sleep 0.1; done Tue 19 Oct 12:53:35 GM

wrote: Checking this again, I think the timestamps are not an hour different and I was misreading some tests I made. The do_install task finished at 17:07 and the do_package finished by 17:11 so we ha

Yesterday there was some talk in irc about a breif networking failure on centos7-ty-4. The build was: https://autobuilder.yoctoproject.org/typhoon/#/builders/104/builds/3083 Showing these warnings: st