[07:18] <jibel> jin_, hey, about telegram 2.0.10.0. There are still major issues with the colours. See my comment and screenshots on https://trello.com/c/O2Aj3Zmq/3023-1222-telegram-app-jin-cth
[07:18] <jin_> jibel, thanks for your feedback, mate
[07:18] <jibel> jin_, at least the country prefix and preferences pages must be fixed
[07:18] <jin_> i already checked
[07:18] <jibel> jin_, great thanks, ping the team when it's updated
[07:19] <jin_> and actually I already gave a fix for that (i just verified pass from my local but need someone to review)
[07:19] <jin_> jibel, super, thanks mate, will ping you after I get it reviewed and merged
[08:55] <jin_> jibel, Hello jibel,
[08:55] <jin_> here we have this one: https://requests.ci-train.ubuntu.com/#/ticket/1234
[08:55] <jin_> jibel, I just added the task in CI-Train, please help me to sign it off ;)
[08:56] <jin_> (of course I get it verified pass locally)
[08:56] <jin_> jibel, the ticket number is: 1234
[08:56] <jin_> jibel, so that I can check in your dashboard :)
[13:01] <Saviq> plars, hey, looks like arale-01 stopped connecting to WiFi altogether :/
[13:01] <Saviq> phablet-network seems to fail 100%
[13:02] <Saviq> https://unity8-jenkins.ubuntu.com/computer/arale-01/builds
[13:03] <Saviq> but krillin-07 was suddenly quite happy overnight
[13:03] <Saviq> https://unity8-jenkins.ubuntu.com/computer/krillin-07/buildshttps://unity8-jenkins.ubuntu.com/computer/krillin-07/builds
[13:03] <Saviq> https://unity8-jenkins.ubuntu.com/computer/krillin-07/builds I mean
[13:03] <plars> Saviq: are you doing anything on arale-01 right now? I'd be happy to take a look and see what I can figure out
[13:03] <Saviq> plars, take it
[13:06] <plars> meh, my vpn keeps getting in a weird state for some reason
[13:09] <plars> Saviq: on the adb disconnects - I checked around a bit by asking, and also by grepping the tmp scripts created when jenkins runs jobs, and I can't find any place where someone intentionally kills adb but...
[13:09] <Saviq> plars, ack
[13:09] <plars> Saviq: just in case, I've copied the adb keys over to a different user than jenkins, and I use that user to start adb now
[13:09] <plars> Saviq: so if anyone were trying to kill it (intentionally or accidentally) then it would probably fail
[13:10] <plars> Saviq: so hopefully that had some benefit, otherwise your stability there was an accident. I think it may have helped though
[13:11] <Saviq> plars, yeah last night krillin-07 completed 6 or so times in a row, so great - arale-01 never got past networking
[13:12] <Saviq> so if that can be resolved and both behave like k last night - I'm happy
[13:21] <rvr> bzoltan: Silo 50 approved
[13:25] <plars> Saviq: well, this is interesting - you don't seem to have a wlan adapter on arale-01
[13:25] <plars> $ adb -s 75UABKPUK9EW shell ifconfig wlan0
[13:25] <plars> wlan0: error fetching interface information: Device not found
[13:25] <Saviq> plars, yeah I suspected something went really wrong after "nmcli device wifi" was just quiet
[13:26] <plars> Saviq: yeah, I think phablet-network died a little to quietly. It does seem to return an error status, but I would expect 90 foot tall letters of fire for that
[13:27] <plars> or maybe at least some string with "Error:" in it
[13:27] <plars> Saviq: is this the latest rc-proposed image?
[13:27] <Saviq> plars, should be
[13:28] <Saviq> plars, this is the latest job that ran on it https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/95/console - ubuntu-touch/rc-proposed/ubuntu@287
[13:29] <plars> jibel: davmor2: Hey, have you seen this? ^ Saviq seems to have an arale that doesn't see wlan0. Is this a new bug that you are aware of, or has this arale just failed in some horribly bad way?
[13:30] <davmor2> plars: mine is working fine on rc-proposed
[13:30] <Mirv> seb128: around still? splits an old qtdeclarative5-ubuntu-ui-toolkit package into four qml-module-ubuntu-* packages, and adds also libubuntutoolkit5-private-dev package, so it would need a binNEW review
[13:30] <davmor2> plars: currently using it to test hotspot on another device
[13:30] <plars> hmm
[13:30] <Mirv> seb128: link https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-050/+sourcepub/6280693/+listing-archive-extra
[13:30] <jibel> plars, I haven't seen this before
[13:31] <seb128> Mirv, sorry I'm too busy for NEW reviews today
[13:31] <seb128> why do those binaries keep changing?
[13:31] <plars> Saviq: so it could be a hardware issue - very strange though. For some reason arale devices seem to really hate you
[13:32] <plars> Saviq: I'm going to throw a fresh image on it, give me a minute
[13:32] <Mirv> seb128: ok. the renaming was to adhere to the qml-module- naming scheme before 16.04 LTS is out to drop transitional packages out, and the opportunity was used to split the included 4 different QML modules in separate packages. other packages keep increasing as new C++ libraries are created from certain key QML compoments for performance reasons
[13:34] <seb128> Mirv, k, well in any case sorry but too busy atm, I can try to maybe have a look later but I'm unsure I'm going to squeeze that in today
[13:35] <Saviq> plars, yeah, seems like it - I've gotta afk anyway, no rush
[13:36] <plars> Saviq: I'll let you know what I find out
[13:36] <Mirv> seb128: thank, you I'm asking on #ubuntu-release
[13:36] <Mirv> thank you,
[13:37] <seb128> yw, sorry I can't help right now
[14:13] <plars> Saviq: sorry for the delay, had a standup to go to. I reflashed your arale, and the wlan0 interface is visible, and phablet-network worked. So I don't know what happened from your test
[14:14] <plars> Saviq: if it happens again, we should see if there's some reliable way to reproduce it
[14:14] <Saviq> plars, ack, let's try running something on it
[14:14] <plars> +1
[14:15] <Saviq> plars, https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/97/console is flashing it now
[14:16] <Saviq> rc-proposed@287
[14:22] <dobey> Mirv: btw, the qt silo with lpotter's fix worked for me
[14:25] <Mirv> dobey: thanks, I take that as a hint that it should be put towards QA next.
[14:28] <dobey> Mirv: indeed
[14:45] <plars> Saviq: well the job failed, but wifi worked. Something with the sudo password in adt perhaps? 14:25:00 adt-virt-ssh: WARNING: specified sudo password fails, no root available
[14:55] <bfiller> fginther`: we're in process of getting our own jenkaas instance up but taking a while.. i mean time we need a bit of help on s-jenkins
[14:56] <fginther`> bfiller, I might be able to help
[14:56] <fginther`> what's up
[14:57] <bfiller> fginther`: lp:ningbo needs the ningo ppa added to it's repository list as there are some packages in there needed for it to build correctly
[14:58] <bfiller> fginther: let me get you the exact branch
[15:00] <bfiller> fginther: this is the ppa that needs to be added for builds for lp:ningbo project https://launchpad.net/~ningbo-team/+archive/ubuntu/ningbo
[15:01] <fginther> bfiller, I'll get it updated in a second
[15:03] <bfiller> fginther: thank you, that's great. And one other thing if possible. We'd like this this new project added to jenkins as well, with the same setup as lp:ningbo. The branch is https://code.launchpad.net/~phablet-team/messaging-framework/trunk
[15:03] <bfiller> we split ninbo into two projects basically..
[15:24] <davmor2> abeato, morphis ^
[15:24] <Saviq> plars, waaat? --password ubuntuci is passed to both u-d-f and adt-run :/ - and well, the job works on krillin
[15:25] <abeato> davmor2, thanks!
[15:26] <Saviq> plars, I'd say that error msg is bogus
[15:26] <Saviq> trying again
[15:26] <plars> Saviq: yeah, I agree
[15:26] <Saviq> or well, at least it's not about the password
[15:26] <plars> Saviq: but I did confirm that wifi works at least
[15:26] <Saviq> yup
[15:26] <plars> Saviq: and that much is pretty clear from the output in your job too
[15:35] <fginther> bfiller, I have the jobs updated/created and am just doing a test run before calling it done
[15:35] <bfiller> fginther: appreciate it
[15:35] <fginther> bfiller, does messaging-framework just need to build on armhf?
[15:37] <bfiller> fginther: amd64 probably good too, whatever ningbo builds on should be the same for messaging-framework
[15:49] <Elleo> sil2100: ^ any chance you could take a look at that last error? Not sure what's caused it other than possible the attempt to build previously when the bot couldn't see the MR
[15:52] <Saviq> plars, aaand no wifi again https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/98/console ¿?
[15:52] <Saviq> this is *weird*
[15:57] <Elleo> trainguards: anyone available to look at the error on silo 20?
[15:57] <sil2100> Elleo: looking
[15:57] <Elleo> sil2100: ah, thanks
[15:57] <sil2100> Elleo: I'll do it the hard way
[15:57] <sil2100> Abandon and reassign, one moment
[15:57] <sil2100> (no time to debug)
[15:57] <Elleo> okay, thanks
[15:58] <fginther> bfiller, the updates are in place now. They build, but tests fail. Let me know if any further tweaks are necessary
[15:58] <sil2100> Elleo: could you re-try the build now? https://requests.ci-train.ubuntu.com/#/ticket/1239
[15:58] <bfiller> fginther: thanks, will do
[15:58] <plars> Saviq: [   15.281559] [WMT-DETECT][I]wmt_detect_dump_pin_conf:WIFI_EINT_NUM(not defined)
[15:59] <Elleo> sil2100: done, thanks :)
[15:59] <plars> Saviq: can I try rebooting it? I'm curious if it's just something that happens randomly on different reboots
[16:03] <Saviq> plars, sure
[16:06] <plars> Saviq: works now after a reboot... eventually I get this, but I don't think I saw it before... let me try a few more boots: [    6.774437] [WMT-DETECT][E]wmt_detect_read_ext_cmb_status(258):WMT-DETECT: WIFI_EINT input status:1
[16:11] <Elleo> sil2100: any idea why that silo switched back to "Ready to build"? I've kicked it off again for now
[16:16] <plars> Saviq: I've done about 10 reboots so far, and wlan0 is still present in all of them
[16:17] <plars> Saviq: I'm wondering if you've hit some hard-to-reproduce corner-case
[16:17] <Saviq> plars, so what am I doing wrong? maybe I need to reboot it after flashing
[16:17] <Saviq> plars, can you try running the same u-d-f line I'm running there?
[16:17] <plars> I don't think you are doing anything wrong
[16:18] <plars> Saviq: yeah, I'm using that same udf params on another one right now. I could also try it in a loop on yours if it won't affect you
[16:18] <Saviq> plars, it won't, have fun with it
[16:18] <plars> Saviq: it's a small consolation, but at least so far it looks like wifi is consistently there after rebooting it
[16:19] <Saviq> plars, yeah, might as well throw in an adb reboot in there
[16:29] <plars> Saviq: I do see that phablet-network happens *immediately* after the device becomes available. so I've set up a quick script to isolate pushing your device to bootloader mode, reinstalling, and running that
[16:47] <plars> ha
[16:48] <plars> Saviq: I have good news and bad news
[16:48] <plars> Saviq: I had a hunch that this was a weird race, so I ran the script mentioned above on two different arales
[16:48] <plars> Saviq: yours actually worked this time - wlan0 is there, network works fine
[16:48] <plars> Saviq: on the other one, I was able to reproduce the bug
[16:50] <plars> Saviq: I'll talk to QA about this, but I think you've stumbled on an interesting bug here. Fortunately I think it's pretty easy to workaround for your purposes. Just adding a reboot ought to do the trick, or maybe even a delay between wait-for-device and phablet-network
[16:54] <Saviq> plars, ah, so you think wlan0's just not showing up early enough?
[16:54] <Saviq> might be indeed
[17:01] <rvr> Mirv: Silo 5 approved
[17:02] <plars> Saviq: something like that. I'm not messing with arale-01 now, if you'd like to try adding a reboot or delay in your job, it might help. If I get any better idea about it, I'll let you know
[17:06] <Saviq> plars, ack, thanks!
[17:07] <Mirv> rvr: thank you
[17:35] <sil2100> robru: ping
[17:36] <robru> sil2100: yeah that error in Elleo's silo is weird
[17:36] <sil2100> robru: could you help Elleo in getting his branch building? https://requests.ci-train.ubuntu.com/#/ticket/1239 <- it's a private branch so maybe that could be the reason?
[17:36] <robru> sil2100: oh yeah that would do it
[17:37] <sil2100> Can we work-around it somehow? He subscribed ci-train-bot IIRC
[17:38] <robru> sil2100: I don't think so. Branches need to be public. I'm not sure what you're expecting the train to do with as private branch, eg, the source is uploaded to a public ppa before being pushed to public Ubuntu archive
[17:38] <robru> Elleo: make your branch public
[17:48] <sil2100> robru: it's not that I don't want to make it public, I just know that Elleo is not around while I would like this built ASAP
[17:49] <sil2100> Oh, actually I made it public
[17:49] <sil2100> Didn't know I can do that for someone's branch
[17:59] <bzoltan> Mirv: robru: we have debian/control changes in the build dependency section what will be needed in the gles build too -> https://launchpadlibrarian.net/252892024/buildlog_ubuntu-vivid-amd64.ubuntu-ui-toolkit-gles_1.3.1926+15.04.20160408_BUILDING.txt.gz
[18:03] <robru> bzoltan: which silo are you referencing? If you're talking about my branch you need to update control.gles with the same changes
[18:04] <bzoltan> robru: silo16
[18:04] <robru> bzoltan: best to review Delta between control and control.gles and eliminate changes not necessary for gles
[18:04] <bzoltan> robru:  where that control.gles lives?
[18:05] <robru> bzoltan: debian/control.gles
[18:05] <robru> bzoltan: you should really take over my branch, I tried to eliminate the Delta but failed, it was too big and I couldn't determine what was necessary and what wasn't
[18:07] <bzoltan> robru:  ahh... so those 3 files I need to add to my landing branch and fix them
[18:09] <robru> bzoltan: Saviq preferred to keep the gles changes in the form of a patch but I failed to create a workable patch for you, so you just get a control.gles and rules.gles for now. Once you minimize the Delta and get something working it might make sense to convert to a patch but that can be done later
[18:09] <bzoltan> robru: I am fine with these addition files
[18:09] <bzoltan> robru:  thanks for your help
[18:10] <robru> bzoltan: right but it may lead to drift again, having a patch makes it easier to keep gles in sync
[18:10] <robru> bzoltan: you're welcome
[18:14] <Mirv> bzoltan: robru: gave you updated MP based on robru's
[18:15] <Mirv> robru: your branch seem very good, I tested it built on 012. might need some polishing but buildability is already a great thing and it's not too big.
[18:15] <robru> Mirv: you updated it already? Thanks!
[18:27] <Mirv> robru: doh, I'll just merge yours to the trunk, bzoltan had another small problem
[18:28] <Mirv> we tried via MP:s
[18:28] <Mirv> it only adds new files to debian/ so it's safe
[18:38] <robru> Mirv: right
[19:28] <bzoltan> Mirv:  ehh... https://launchpadlibrarian.net/252904187/buildlog_ubuntu-xenial-amd64.ubuntu-ui-toolkit-gles_1.3.1926+16.04.20160408.1_BUILDING.txt.gz
[19:30] <sil2100> Fridays...
[21:37] <Saviq> robru, hey, any idea about this: http://pastebin.ubuntu.com/15699284/ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-013/+sourcepub/6291429/+listing-archive-extra - published over half hour ago but apt-get policy can't see the new amrhf package ¿?
[21:38] <Saviq> hmm Packages.gz shows the new one
[21:38] <Saviq> maybe it was just taking its time
[21:39] <Saviq> yeah, it's good again
[21:39] <Saviq> robru, unping
[21:44] <robru> heh