**** BEGIN LOGGING AT Wed Jul 31 02:59:56 2019
Jul 31 07:52:01 <Herrie> Morning!
Jul 31 09:09:18 <Tofe> Morning!
Jul 31 13:23:56 <JaMa> FYI: some of the testing builds failed because of OOMK
Jul 31 13:24:01 <JaMa> [4090378.536512] Out of memory: Kill process 18076 (Cooker) score 4 or sacrifice child
Jul 31 13:24:04 <JaMa> [4090378.536539] Killed process 18255 (Worker) total-vm:276500kB, anon-rss:141736kB, file-rss:0kB, shmem-rss:0kB
Jul 31 13:24:40 <JaMa> couple days ago as well, I wonder what changed
Jul 31 13:24:48 <JaMa> [Wed Jun 26 09:36:27 2019] Out of memory: Kill process 15309 (Cooker) score 4 or sacrifice child
Jul 31 13:24:51 <JaMa> [Wed Jun 26 09:36:27 2019] Killed process 3563 (pseudo) total-vm:9716kB, anon-rss:104kB, file-rss:0kB, shmem-rss:64kB
Jul 31 13:25:01 <JaMa> [Wed Jun 26 09:36:27 2019] Out of memory: Kill process 15309 (Cooker) score 4 or sacrifice child
Jul 31 13:25:01 <JaMa> [Wed Jun 26 09:36:27 2019] Killed process 15309 (Cooker) total-vm:726636kB, anon-rss:440324kB, file-rss:0kB, shmem-rss:28kB
Jul 31 13:25:01 <JaMa> [Wed Jun 26 09:36:29 2019] Out of memory: Kill process 1897 (cc1plus) score 2 or sacrifice child
Jul 31 13:25:03 <JaMa> [Wed Jun 26 09:36:29 2019] Killed process 1897 (cc1plus) total-vm:338228kB, anon-rss:286908kB, file-rss:0kB, shmem-rss:13592kB
Jul 31 13:25:09 <JaMa> [Wed Jul 31 11:54:49 2019] Out of memory: Kill process 18076 (Cooker) score 4 or sacrifice child
Jul 31 13:25:09 <JaMa> [Wed Jul 31 11:54:49 2019] Killed process 18255 (Worker) total-vm:276500kB, anon-rss:141736kB, file-rss:0kB, shmem-rss:0kB
Jul 31 13:25:18 <Herrie> JaMa: Hmmz weord
Jul 31 13:25:19 <Herrie> wird
Jul 31 13:25:23 <Herrie> weird
Jul 31 13:25:27 <Tofe> weird, even
Jul 31 13:25:31 <Herrie> Need a new KB
Jul 31 13:25:39 <Herrie> Or clean it LOL
Jul 31 13:25:55 <JaMa> there is 20G in unstable tmpfs, that might cause that
Jul 31 13:26:55 <JaMa> as there is 60G free space in testing tmpfs and around 60G free ram, so if the tmpfs gets full there won't be any ram left for the build
Jul 31 13:27:43 <JaMa> will restart failed builds after this round is finished
Jul 31 13:33:38 <JaMa> also milla has full disk
Jul 31 13:34:21 <JaMa> what's the status of the new drives?
Jul 31 13:34:37 <JaMa> /dev/xvdc1      985G  985G     0 100% /home/jenkins
Jul 31 13:42:29 <JaMa> 29G     /home/jenkins/htdocs/buildlogs
Jul 31 13:42:29 <JaMa> 668G    /home/jenkins/htdocs/builds
Jul 31 13:42:29 <JaMa> 88K     /home/jenkins/htdocs/feeds
Jul 31 13:42:29 <JaMa> 12K     /home/jenkins/htdocs/index.html
Jul 31 13:42:29 <JaMa> 235G    /home/jenkins/htdocs/oe-sources
Jul 31 13:42:31 <JaMa> 55G     /home/jenkins/htdocs/sources
Jul 31 13:43:04 <JaMa> 176G    /home/jenkins/htdocs/builds/luneos-unstable-zeus
Jul 31 13:43:04 <JaMa> 345G    /home/jenkins/htdocs/builds/luneos-testing-warrior
Jul 31 13:43:09 <JaMa> ready to drop all except latest?
Jul 31 13:45:36 <Herrie> JaMa: Yeah guess so
Jul 31 13:45:45 <Herrie> I guess my trialling with the Preware feeds might have used up some space
Jul 31 13:46:21 <Tofe> JaMa: no problem for dropping earlier builds
Jul 31 13:50:06 <JaMa> ok
Jul 31 13:59:33 <JaMa> /dev/xvdc1      985G  791G  194G  81% /home/jenkins
Jul 31 14:00:30 <JaMa> 6.3G    /home/jenkins/htdocs/builds/luneos-testing-warrior/images
Jul 31 14:00:30 <JaMa> 87G     /home/jenkins/htdocs/builds/luneos-testing-warrior/sstate-cache
Jul 31 14:00:30 <JaMa> 174G    /home/jenkins/htdocs/builds/luneos-testing-warrior/ipk
Jul 31 14:00:43 <JaMa> maybe I should drop ipk feed as well at this point
Jul 31 14:04:38 <Tofe> yes, for testing we should care much
Jul 31 14:04:45 <Tofe> shouldn't
Jul 31 14:05:14 <JaMa> will recreate the latest versions later
Jul 31 14:11:03 <JaMa> /dev/xvdc1      985G  579G  407G  59% /home/jenkins
**** ENDING LOGGING AT Thu Aug 01 03:00:25 2019