[02:10] <imgbot> [03:55] <imgbot> [03:55] <imgbot> [04:36] <rsalveti> nice, many great fixes
[04:36] <rsalveti> we should promote 171 as well
[08:48] <pete-woods> trainguards: I fixed my not approved silo (#27), if someone could push the publish button again :)
[08:52] <Mirv> pete-woods: ok!
[09:07] <pete-woods> Mirv: thanks!
[09:09] <Mirv> np
[10:52] <Laney> cihelp - hi, looks like syncing of autopkgtest results to the public jenkins instance is broken - e.g. okteta has up to job #94 internal but only shows #85 on jenkins.qa.u.c
[13:06] <rvr> rsalveti: ping
[13:08] <rvr> rsalveti: I'm about to approve silo 9 (network-manager, reconnect). In the spreadsheet it says "Additionally it also needs to be validated with Modem Manager (Ubuntu Desktop, using an external modem dongle)."
[13:09] <rvr> rsalveti: We are not doing any desktop related testing right now.
[13:09] <rvr> rsalveti: Is that already validated by your team?
[13:09] <rsalveti> nops, and unfortunately we don't have a usb dongle in hands to test
[13:09] <rsalveti> we need to test the desktop side in order to land this though
[13:32] <rsalveti> rvr: davmor2: do you guys know if someone from QA has an external modem dongle to validate that silo?
[13:32] <rsalveti> this is host side validation for modem manager
[13:34] <davmor2> rsalveti: how do you mean an external modem dongle?   I have 2-3 usb dongles
[13:35] <davmor2> rsalveti: are we talking just wifi for desktop though?
[13:36] <rsalveti> davmor2: desktop, yeah, a usb modem dongle
[13:36] <rvr> davmor2: I think it is for 3G dongles
[13:36] <rsalveti> yup, 3g dongles
[13:36] <rsalveti> need to find someone that has one at least
[13:37] <rsalveti> one that is known to work with modem manager
[13:38] <rvr> rsalveti: I have a USB 3G dongle that in the past has worked with Ubuntu
[13:39] <rvr> rsalveti: But I'm not happy having to test desktop silos, we are not doing that.
[13:39] <rvr> rsalveti: So, I can do it *exceptionally*
[13:39] <rsalveti> rvr: well, it's the only way to land this
[13:39] <rsalveti> rvr: in order to avoid regressions on the desktop
[13:39] <rsalveti> we don't have only ubuntu touch here
[13:40] <rsalveti> and some components might affect the desktop
[13:40] <rsalveti> so doing some sanity testing with the desktop, sometimes, are expected
[13:40] <rvr> That's exactly the signal I don't want to emit
[13:42] <rvr> QA team are not the testing guys with lots of free time to check everything, we are gating phone silos to prevent regressions in the devices because that's the priority. Don't expect otherwise.
[13:43] <rsalveti> sure, but the goal is having a better phone product, right?
[13:43] <rsalveti> and we can't necessarily land without validating the desktop, in this case
[13:43] <rsalveti> we'd do the validation ourself, if we had the hardware in hands
[13:44] <rvr> That's why, exceptionally, I'll help you validating that it works in the desktop
[13:45] <rsalveti> rvr: great, this is not a rule for sure, it's just that we don't have the hardware
[13:45] <rsalveti> rvr: thanks
[13:46]  * rvr downloads the latest Vivid image
[13:52] <davmor2> rvr: rsalveti I have a 3g dongle that works I just have no credit on it and I'm on vivid
[13:52] <rsalveti> davmor2: can't you use the same sim card you use on arale/krillin?
[13:52] <rvr> davmor2: The silo is for Vivid
[13:54] <davmor2> rsalveti: I don't think they are on the same network let me check
[14:01] <rvr> Ok, mine is recognized in Utopic
[14:05] <robru> lool: got you silo 5
[14:07] <robru> ted: silo 14 for your vivid+1 refund work
[14:08] <ted> robru, Oh, sweet, thanks!
[14:08] <robru> ted: you're welcome!
[14:08] <davmor2> rsalveti: hang on do I need to go to a specific site I have a feeling this will let me connect to 3 for top up let me test that
[14:11] <davmor2> rsalveti: meh no
[14:12] <rsalveti> davmor2: doesn't work or just not compatible with your sim?
[14:12] <davmor2> rsalveti: only works with 3 so doesn't work with the giffgaff sims I have and maybe too old too :(
[14:13] <rsalveti> davmor2: got it, no worries
[14:13] <davmor2> rsalveti: I have a mifi too but that takes care of the modem part so that is no use I guess
[14:20] <om26er_> salem_, Hi!
[14:20] <salem_> om26er_, hello
[14:21] <om26er_> salem_, silo 29 failed. It does not fix the bug :/
[14:21] <om26er_> see my comment here: https://trello.com/c/yGde8ScD/1388-ubuntu-landing-029-messaging-app-boiko
[14:23] <psivaa> Laney: The jenkins publishing queue is quite long, public one being very slow, okteta #96 is on the way
[14:23] <Laney> psivaa: is it going to catch up and stay caught up?
[14:23] <psivaa> Laney: that's the intention
[14:24] <salem_> om26er_, ok, I will have a look. thanks
[14:25] <boiko> om26er_: so, you send messages from one SIM to another, right?
[14:32] <om26er_> boiko, I send the message to myself
[14:32] <om26er_> from the same sim to the same thing, but that should not be different.
[14:34] <boiko> om26er_: ok, just curious, because I tried this multiple times and it works on every try :/
[14:40] <boiko> om26er_: nevermind, just reproduced the case you mentioned
[14:51] <sil2100> jibel: I suppose let's join the RTM meeting each of us on his own PC, no need to share a screen
[14:51] <jibel> sil2100, agreed, it's even more difficult to share a headset :)
[14:52] <sil2100> I'm a bit worried about the internet quality here
[14:53] <rvr> sil2100: Are you also in Austin?
[14:53] <jibel> sil2100, I just had another HO and it's ... painful
[14:53] <sil2100> rvr: yes
[14:53] <rvr> Nice
[14:53] <rvr> rsalveti: Ok, USB with Vivid booted on my laptop, now I'll install the citrain tools and the silo
[14:54] <rsalveti> rvr: great, thanks
[14:59] <lool> dpkg-source: error: syntax error in /var/lib/jenkins/silos/ubuntu/landing-005/ubuntu-location-provider-here_0.1+15.04.20150127~rtm-0ubuntu1.dsc at line 1: line with unknown format (not field-colon-value)
[14:59] <lool> interesting
[15:00] <lool> it works for me here
[15:00] <lool> robru: I think I'm going to require some help fixing this ^
[15:00] <lool> is it because it's running an older dpkg-source maybe?
[15:01] <rvr> davmor2: Is there a way to log into unity 7 in Vivid ISO?
[15:01] <rvr> davmor2: Unity Next is presented instead
[15:02] <davmor2> rvr: did you get the daily iso or the ubuntu-next iso
[15:02] <rvr> vivid-desktop-amd64.iso
[15:03] <davmor2> rvr: yeah but from where
[15:03] <rvr> davmor2: http://cdimage.ubuntu.com/daily-live/20150414/
[15:04] <davmor2> http://cdimages.ubuntu.com/daily-live/current/
[15:07] <jibel> rvr, download from pending instead of current
[15:08] <rvr> Ok
[15:27] <om26er_> seb128, Hi!
[15:27] <seb128> om26er_, hey
[15:28] <om26er_> seb128, re: silo 06, it looks like the fix for bug 1438049 could have some autopilot tests
[15:29] <om26er_> and the battery fix needs to be added to the TestPlan.
[15:29] <seb128> om26er_, I guess it could, I've no slot for that this week and I'm travelling/to a sprint next
[15:30] <seb128> om26er_, so either we delay by that and forget about those fixes for vivid or you ack it like that
[15:31] <om26er_> seb128, Theses fixes don't look very critical so I guess we can delay this landing.
[15:32] <seb128> om26er_, shrug
[15:33] <seb128> om26er_, there is a segfault fix, one usability issue coming from our user testing and a quite visible bug (discharge graph being wrong when waking up the device)
[15:34] <seb128> om26er_, but oh well, if you want to throw the work again please do
[15:34] <om26er_> seb128, yes, we are asked to not land silos without test so I'd prefer not go around that. Unless someone from mgmt approves that.
[15:35] <om26er_> it might make sense to re-upload the silo with the focus fix removed.
[15:35] <seb128> pmcgowan, kenvandine, jgdx, ^ fyi, the fixes in silo 006 (trivial ones) are blocked by qa, I've no slot for writting test in the next week, should we just discard the work and let segfaults & co in vivid?
[15:36] <robru> lool: checking
[15:36] <jgdx> seb128, I don't know what segfaults & co is
[15:36] <seb128> jgdx, segfault is the null check in the bluetooth panel
[15:37] <seb128> I hit that segfault a few time on my bq
[15:37] <seb128> the co are the focus fix, and the one to refresh the discharge graph on wakeup/focus
[15:37] <robru> lool: https://ci-train.ubuntu.com/job/cyphermox-test/893/console indeed that's a funny looking DSC, I never saw one in xml before ;-)
[15:38] <cyphermox> robru: and I thought you were pinging me :)
[15:38] <robru> cyphermox: do you want me to rename the job so we stop pinging you? ;-)
[15:39] <cyphermox> as you wish, it's just funny :)
[15:39] <robru> lool: https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/133/console indeed it is just a transient network issue, restarted the build and it looks ok now
[15:39] <jgdx> seb128, okay dokay
[15:53] <pmcgowan> jgdx, so is creating tests for those something you can do
[16:02] <rvr> jibel: davmor2: I downloaded the correct image, and only suggests to try Ubuntu Next
[16:03] <rvr> Hmm
[16:03] <rvr> Let me check whether I overwrote the wrong image
[16:04] <rvr> md5sum -c MD5SUMS vivid-desktop-amd64.iso: OK
[16:06] <lool> robru: thanks
[16:06] <robru> lool: you're welcome
[16:22] <davmor2> rvr: is it a saying what next try ubuntu install ubuntu
[16:23] <davmor2> and has been mis-translated?
[16:23] <rvr> davmor2: I'm only offered to try Unity 8 or to install it, not to launch Unity 7
[16:23] <davmor2> rvr: that image is only unity 7
[16:24] <davmor2> rvr: let me grab it
[16:24] <rvr> davmor2: Well...
[16:24] <rvr> davmor2: md5sum tells me it is the right image in http://cdimages.ubuntu.com/daily-live/pending/
[16:24] <rvr> davmor2: I downloaded http://cdimages.ubuntu.com/daily-live/pending/vivid-desktop-amd64.iso
[16:31] <rpadovani> sil2100, does this fix the AP issue with calculator? In the first moment I created the project with app/tests because thatś what the QML App with Simlpe UI (cmake) does in the sdk
[16:31] <rpadovani> https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/fixApDirectory/+merge/256175
[16:38] <seb128> sil2100, hey, is there a known issue with vivid update giving a non working calculator?
[16:38] <seb128> the icon is missing in the dash and it doesn't start, aa-exec complains about the missing apparmor profile
[16:40] <sil2100> seb128: hm, I didn't know anything, it worked fine for ubuntu-rtm - we had a reboot landed recently, maybe vivid doesn't have the right apparmor profiles for it yet
[16:40] <sil2100> cwayne: ^ did you have to update something in the custom tarball for 14.09 when the new calculator app landed?
[16:40] <cwayne> sil2100, noep
[16:42] <sil2100> rpadovani: hey! Let me take a look :)
[16:43] <rpadovani> sil2100, sorry, had to fix CMake, now shoulb de ok :-)
[16:43] <sil2100> rpadovani: hah, yeah, just commented on that ;)
[16:44] <sil2100> rpadovani: will the unit tests still work now?
[16:44] <sil2100> I suppose there are no paths that need to be changes in the AP tests themselves, right?
[16:45] <rpadovani> sil2100, afaik unit tests are the ones created by the sdk template
[16:45] <rpadovani> sil2100, no idea, autopilot and I aren't good friends :P
[16:46] <sil2100> bzoltan: hey, I was wondering, since it seems the SDK template creates the test directory in app/tests - is that a standard now?
[16:46] <sil2100> bzoltan: is that also the directory for AP tests?
[16:46] <sil2100> Since if that's the new standard, we'll have to modify phablet-click-test-setup
[16:52] <bzoltan> sil2100:  rpadovani: there is no such standard writen anywhere. It is more like a best practice
[16:53] <sil2100> bzoltan: is that also the best practice directory for AP tests?
[16:53] <sil2100> Since if more people use this directory this way, the AP-test tools need to be accomodated
[16:53] <sil2100> As now they only look for tests in tests/
[16:55] <bzoltan> sil2100:  tests can be anywhere as far as  I know.
[16:55] <sil2100> bzoltan: not for phablet-click-test-setup
[16:59] <jibel> sil2100, that's a bug in phablet-click-test-setup, it shouldn't explode if it doesn't find the tests where it expects them to be
[17:00] <jibel> tests can be anywhere, the tool should be smarter in its discovery
[17:03] <bzoltan> sil2100:  well.. that is the problem of the phablet-click-test-setup :) it should be smarter
[17:08] <om26er_> cihelp Hi! whats happening with smoke testing results, seem last appears on 10th April: http://ci.ubuntu.com/smokeng/vivid/touch/
[17:11] <sil2100> bzoltan, jibel: yeah, in theory, but making it smarter would mean it would have to scan the whole directory tree for tests which in theory can have various forms and format
[17:11] <sil2100> *formats
[17:11] <sil2100> Making it smart would mean writing a lot of guessing code
[17:12] <sil2100> Sure, could be smarter, but best following certain pre-defined standards for that to avoid problems
[17:12] <jibel> sil2100, use adt in CI instead, problem solved
[17:13] <jibel> sil2100, and again if p-c-t-s doesnt' find tests it shouldn't explode
[17:13] <jibel> just ignore it
[17:14] <jibel> cihelp; ^ is anyone on this, there is no result on the dashboard for the last 5 days
[17:15] <psivaa> jibel: om26er_: looking into it, the network being slow does not help
[17:20] <boiko> om26er_: salem_: so, the fix is correct, it is just not working because of a regression I introduced on a previous change, I will add an MR to the silo to get it fully working
[17:21] <boiko> om26er_: salem_: luckily it is just a one-line change
[17:22] <om26er_> boiko, one line fixes are the best ones :)
[17:26] <boiko> om26er_: that's a pitty they are so rare
[17:27] <boiko> om26er_: so, I will add the extra MR to the silo, and re-test it
[17:29] <boiko> trainguards: can I get vivid silo 29 reconfigured? I added a new component there (telephony-service)
[17:30] <sil2100> boiko: on it
[17:31] <rpadovani> sil2100, Jenkins is now happy with https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/fixApDirectory/+merge/256175
[17:31] <rpadovani> afaics, it's all we need
[17:31] <sil2100> rpadovani:
[17:31] <sil2100> rpadovani: \o/
[17:31] <sil2100> rpadovani: I'll check that after lunch and approve if anything
[17:31] <sil2100> rpadovani: thanks :)
[17:32] <sil2100> boiko: reconfigured
[17:32]  * sil2100 lunch, suspending
[17:32] <boiko> sil2100: great! thanks! enjoy your lunch :)
[17:33] <rpadovani> sil2100, thanks, enjoy :-)
[17:34] <bzoltan> sil2100: you are right. It is a double edged sword you know... I could come up with a strict app structure back 2 years ago to serve these types of automatization, discoverability and many other things... believe me there are other areas where a strict app structure policy would be beneficial. For example API control is easier. But community folks and app developers together with hyperfree hipsters woluld have  stond me if I tell them that they need to
[17:34] <bzoltan> follow a policy :D
[17:42] <rpadovani> bzoltan, I think 90% of developers follow sdk templates :-)
[17:43] <bzoltan> rpadovani:  I hope so :)
[17:54] <jgdx> pmcgowan, I think so, if all there is to it is: making a AP test for the highlight in security/privacy, and a section in the testplan for the battery fix.
[17:54] <jgdx> bfiller, ping
[18:21] <boiko> om26er_: silo 29 updated, no more changes required on messaging-app itself, just the extra MR on telephony-service itself
[19:08] <bfiller> jgdx: pong
[22:00] <robru> lol, no
[22:01] <sil2100> huh?
[22:10] <robru> sil2100: silo 15 is mine, i don't want to publish it. clicked that by mistake
[23:01] <sil2100> o/