[00:00] <veebers> alesage: I tried to flash my device before and got the screen with an IC in a cross stating that the device needed to be restored. After a reboot I tried again but u-d-f complained about not enough space. It was then suggested that I needed to boot to recovery and use that command
[00:02] <alesage> veebers, ok I have the full history--not sure how to help except to give you a new set of instructions shared by rvr with me earlier today
[00:02] <veebers> alesage: hit me I'll give it a try
[00:03] <alesage> veebers, to confirm, is this a krillin?
[00:03] <veebers> alesage: yes
[00:03] <alesage> veebers, ok supah
[00:03] <alesage> veebers, forwarding a mail to you
[00:03] <veebers> alesage: much appreciated
[00:03] <alesage> veebers, we're needing vivid or RTM?
[00:04] <veebers> alesage: devel-proposed?
[00:04] <veebers> :-(
[00:04] <veebers> err :-)
[00:04] <alesage> veebers, ok
[00:08] <veebers> alesage: you fired that email my way?
[00:08]  * veebers is feeling impatient today
[00:08] <veebers> :-)
[00:09] <alesage> veebers, just had to verify something, in your inbox
[00:09] <veebers> alesage: heh awesome, thans
[00:09] <veebers> thanks even
[00:10] <veebers> alesage: just gonna get lunch then I'll give it a try and bother you if I can't get it going ^_^
[00:11] <alesage> veebers, ok I'll EOD soon but send you positive vibes
[02:21] <veebers> elopio: let me know when you get back, if after my EOD I'll fire an email (not urgent)
[04:00] <elopio> veebers: I'm back.
[04:03] <veebers> elopio: rats now I've forgotten what it was specifically :-\ one moment
[04:03] <veebers> sorry :-\
[04:05] <elopio> np.
[04:05] <veebers> elopio: ah right I totally remember what it was now, looking the vanguard journal, why was the suggestion to kalikiana to us qt slots for the orientation and not the functionality described to Kaleo?
[04:07] <elopio> veebers: he wants to change the property, not to read it.
[04:07] <elopio> so we use the slots to call a javascript function.
[04:08] <elopio> reading the property is no problem in his case, because it is accessible to autopilot on the OrientationHelper component.
[04:09] <veebers> elopio: correct me if I'm wrong, but isn't that the intention of this code? https://code.launchpad.net/~canonical/unity8/fake_platform_sensors_module/+merge/247334
[04:09] <veebers> to fire off those events so the device acts as though it's been rotated?
[04:11] <elopio> veebers: yes. But what kalikiana is doing is for a lower level of testing. Switching the orientation through QML will be mainly used in QML tests, nothing specific to a device with sensors and nothing related to Unity.
[04:12] <veebers> elopio: ack ok, although (once that code lands) it'll be better supported than the autopilot slot calling code :-)
[04:12] <elopio> there are some tests for the toolkit that are currently hard to write in QML, but easy to write in autopilot. So it's useful for those cases to have the option to rotate.
[04:12] <elopio> still, those tests should be low level, and isolated from the shell and the sensors.
[04:13] <veebers> elopio: makes sense.
[04:14] <elopio> veebers: yes, almost all the autopilot tests, I'd prefer to use the fake sensors.
[04:14] <veebers> elopio: on a different note, can you recall the project that brendand mentioned this morning in the standup re: accounts and a cli?
[04:14] <elopio> we need to be careful to watch at the level of the tests they are adding, and recommend the right thing for each case.
[04:14] <elopio> veebers: accounts-console?
[04:14] <veebers> elopio: very true
[04:14] <elopio> I wasn't really paying attention to that part of the meeting.
[04:14] <veebers> elopio: perhaps, man. I haven't gotten everything I wanted to get done today :-|
[04:15] <veebers> I've been spending it all pinging you to annoy you :-) Oh yeah, got my device flashed in the end, once I fixed the commands you gave me ;-)
[04:21] <elopio> veebers: accounts-console does the same thing calling glib, but in an ugly way.
[04:22] <elopio> and sorry about the flashing commands. recovery, bootloader, boostrap, reboot. They are all the same to me :)
[04:24] <veebers> elopio: no worries, I got there in the end. Ah cool, I'll investigate further for the accounts stuff, at this stage it'll probably be tomorrow unfortunately
[04:25] <elopio> veebers: what is it that you are trying to do with accounts?
[04:26] <veebers> elopio: this is for the card "After upgrading check that online accounts are present and accesible"
[04:27] <veebers> so I (assume( that i'll need to check that the accounts that were created before reboot/upgrade still exist
[04:27] <veebers> this is the MP that I showed you yesterday
[04:31] <elopio> veebers: yes, you can get some ideas from the list method in accounts-console
[04:31] <elopio> http://bazaar.launchpad.net/~online-accounts/account-plugins/trunk/view/head:/tools/account-console
[04:31] <elopio> it just need to be cleaned up.
[04:32] <veebers> elopio: ack, that's the plan. I'll hit it tonight/tomorrow
[06:04] <pitti> Good morning
[09:49] <rvr> Good morning
[13:44] <rhuddie> fgimenez, I need to add another reactor for doing download and waiting on UpdateDownloaded signal
[13:44] <rhuddie> I was looking at your apply update branch, and it makes sense to branch from that I think, so I can use your reactor base class
[13:45] <fgimenez> rhuddie, yes, it's copied from barry's branch and a bit refactored to prevent code duplication
[13:46] <rhuddie> fgimenez, yes, looks very helpful for what I need
[13:46] <fgimenez> you just have to define the namedtuple with the expected signal and fields and the subclass of BaseReactor with the signal name and the callable from the iface
[13:48] <alecu> vanguard: here's the proposed design for Refunds: https://docs.google.com/a/canonical.com/document/d/1Ecfz4TTL65S43KR68ZIlw2A-DB8ojg2RLw7sutxpB7o/edit#
[13:54] <fgimenez> alecu, ok thanks, i've added the link to the vanguard journal
[13:54] <alecu> fgimenez: I was expecting leo to reply to that, but thank you! :-)
[13:55] <fgimenez> alecu, i'm on call today you know :)
[13:59] <brendand> alecu, the vanguard is actually ubuntu-qa
[13:59] <brendand> alecu, just so you know - otherwise we don't get a highlight
[14:00] <alecu> brendand: ah, good point
[14:01] <alecu> brendand: would you mind adding that to the channel topic? eg: #ubuntu-ci-eng explains who to ping there.
[14:01] <brendand> alecu, it is :)
[15:14] <barry> this mp has been merged with the updated trunk, so it's ready for re-review: https://code.launchpad.net/~barry/ubuntu-ota-tests/check-for-update-2/+merge/252324
[15:21] <elopio> thanks barry. I moved the card to the review lane.
[15:22] <elopio> barry: you are missing the dependencies on
[15:22] <elopio> 62	+Tests: check_for_update
[15:23] <elopio> does this depend on the 3.0 version?
[15:24] <barry> elopio: oops, i meant to move it, sorry
[15:25] <barry> elopio: ah yes, it does, but now i have a successful recent build: https://launchpad.net/~barry/+archive/ubuntu/systemimage/+build/7052762
[15:25]  * barry will add them
[16:35] <pitti> jibel: I just updated lp:auto-package-testing for armhf/ppc64el, could you please roll this out on tachash?
[16:35] <pitti> (added --eatmydata, for go-faster stripes)
[16:36] <jibel> pitti, if the VPN let me in ...
[16:36] <pitti> jibel: going through batuan?
[16:36] <jibel> pitti, no, it often loses DNS resolution
[16:37] <jibel> and my brain stopped remembering IP addresses
[16:37] <pitti> $ host tachash.ubuntu-ci
[16:37] <pitti> tachash.ubuntu-ci has address 10.100.0.2
[16:37] <pitti> does that help at all?
[16:38] <pitti> jibel: ^
[16:38] <jibel> pitti, thanks, that's fine, I bounced the VPN connection but then lost IRC :)
[16:39] <jibel> anyway, it's done
[16:39] <jibel> pitti, r397
[16:40] <pitti> jibel: cheers
[16:44] <pitti> jibel: I'll be on holidays the next 1.5 weeks (Mar 16 to 25); do you have time during that to watch the jenkins failures and hit the retry buttons?
[16:45] <jibel> pitti, sure, no problem.
[16:46] <jibel> pitti, is there anything to do with the testbeds? for example we received lot of notifications for dead cyclops today.
[16:46] <pitti> jibel: yeah, I'm working on the cyclops and  wolfes ATM
[16:46] <pitti> jibel: I have all of them back running now
[16:46] <pitti> plars: ^ FYI
[16:46] <pitti> but often starting LXC gets stuck
[16:46] <jibel> pitti, OK. house cleaning before leaving on holidays :)
[16:47] <pitti> it's not the new kernel and it's not upstart vs. systemd
[16:47] <pitti> so apparenlty some problem with vivid's lxc, or cgmanager etc.
[16:48] <plars> pitti: yes, I got 4 back up and going yesterday, forgot to mention that, sorry
[16:48] <plars> pitti: I figured you would see too though :)
[16:49] <plars> pitti: was there anything else you needed done on them?
[16:49] <pitti> plars: no worries, I noticed that it was back and reinstalled it
[16:49] <pitti> plars: no, all fine; thanks muchly!
[16:49] <plars> pitti: awesome
[16:49] <pitti> jibel: FYI, I upgraded all of them to vivid as we can't run vivid containers on trusty any more (no systemd support)
[16:50] <pitti> or at least not until all the stuff gets backported, which is planned, but still some time out
[16:50] <pitti> and I don't want to completely stop testing on these
[16:51] <pitti> plars, jibel: FYI, the armhf boxes are running trusty's kernel as vivid's doesn't boot (I don't know why, I don't have a serial console -- would be nice to get a log/trace!)
[16:51] <pitti> ppc64 wolfes are happy with vivid's 3.19
[17:10] <pitti> jibel: hm, so containers often hang on startup, not sure why yet; cancelling the jobs in jenkins works, and they become red fast, so at least there's some manual but easy way to clean up
[18:51] <spagewmf> I followed a Google link to https://help.ubuntu.com/community/Installation/FromUSBStick , I get a Python exceptions.TypeError
[18:51] <spagewmf> (I reported it in #ubuntu-website, no ack yet)
[18:52] <spagewmf> seems every community wiki page also getting the same MoinMoin.py error
[19:19] <elopio> balloons: you have just send an email for which I have not a single word to reply.
[19:19] <elopio> I will just say: "hum..."
[19:21] <elfy> balloons: ok - so got the nexus, got ubuntu on it, want to do some of this touch testing - what's the best course of action here?
[19:22] <elfy> I've found some dekko issues and hassled DanChapman - so that's ok - but generally, is there a tracker type affair?
[19:22] <balloons> elopio, wow.. I've silenced you?
[19:22] <balloons> elfy, go break stuff!
[19:23] <balloons> https://wiki.ubuntu.com/Touch/Testing and https://wiki.ubuntu.com/QATeam/TouchTesting
[19:23] <elfy> balloons: yea that works - except I don't use it as a phone obviously :D
[19:23] <elfy> aah cool
[19:24] <elfy> oh cool - so there is tracker
[19:24] <elopio> balloons: yes. I won't speak anymore until you get the issue solved ;)
[19:24] <dobey> drink the kool aid!
[19:24] <balloons> in general though yes, try stuff break it, and hang out on the ubuntu-phone list also
[19:24] <elfy> mmm
[19:24] <elfy> so list and -touch on irc?
[19:26] <elfy> balloons: ok - so can I assume that the people who wrote these tests weren't English?
[19:27] <elfy> I don't want to blitz the system with pointless bug reports on test wording
[19:27] <balloons> elfy, there is no tracker
[19:27]  * balloons waves hand
[19:28] <elfy> god - that sounds horrid - don't mean that like that ...
[19:28] <elfy> balloons: what's this then ? http://iso.qa.ubuntu.com/qatracker/milestones/326/builds/89032/testcases
[19:29] <balloons> that is something someone continues to publish, and I don't know why
[19:29]  * balloons knows a sneaky fix
[19:34] <elfy> balloons: lol - ok so basically - just use it and see waht goes on ?
[19:34] <balloons> elfy, yep. File bugs when you find breakages. Are you running -proposed?
[19:34] <elfy> no idea  ,,,
[19:36] <elfy> I set it up from https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[19:37] <balloons> elfy, ok, so devel channel
[19:37] <elfy> as far as I know yep
[19:37] <balloons> you should switch to proposed for maximum breakages
[19:38] <elfy> ok
[19:38] <balloons> also, generally there are calls to test specific new versions of apps
[19:38] <balloons> just try and watch the list.. and let popey know you want 'in' on testin stuff
[19:38] <elfy> yep
[19:38] <elfy> not on list yet
[19:39] <balloons> elopio, I'm not sure if I've done a good or bad thing, but it's taken me a few weeks to be able to write that mail
[19:40] <elfy> balloons: mmm - see I went https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/ which made it seem like /devel was the right channel
[19:41] <balloons> elfy, indeed.. That's really aimed at folks who won't be testing of course
[19:42] <elfy> balloons: ok - I'll grab popey :)
[19:42] <elopio> balloons: it's good, of course.
[19:42] <balloons> definitely flash proposed though.. all the cool kids run it ;-)
[19:42] <elopio> it's a huge hole in our strategy.
[19:43] <balloons> yea, but I know how you feel realizing it.. I thought we fixed this stuff last summer
[19:43] <Kaleo> who is the vanguard?
[19:44] <balloons> elopio, ^^ in regards to vanguard do you want to update it here, or just ubuntu-qa?
[19:47] <Kaleo> elopio, I have a qml test that does some rendering but it fails on jenkins, is there a special thing to do to fix that?
[19:47] <Kaleo> https://launchpadlibrarian.net/200047799/buildlog_ubuntu-vivid-armhf.camera-app_3.0.0%2B15.04.20150312-0ubuntu1_BUILDING.txt.gz
[19:47] <Kaleo> "This plugin does not support createPlatformOpenGLContext!"
[19:49] <brendand> Kaleo, just ping ubuntu-qa and the vanguard knows who they are
[19:49] <brendand> Kaleo, right now it happens to be elopio anyway
[19:50] <Kaleo> brendand, there is no ubuntu-qa
[19:50] <Kaleo> or I don't understand what "pinging" means
[19:50] <brendand> Kaleo, it's an alias (irc highlight)
[19:50] <balloons> Kaleo, so true..
[19:51] <balloons> sorry, hence the questions.
[19:51] <elopio> coincidentially, I'm the vanguard.
[19:51] <elopio> Kaleo: let me see what you are talking about.
[19:52] <elopio> Kaleo: this is run while the package is built?}
[19:53] <jfunk> there is no spoon
[19:53] <elopio> nevermind, I see on the logs that the answer is yes.
[19:53] <jfunk> there is no ubuntu-qa
[19:53] <Kaleo> :)
[19:54] <elopio> Kaleo: we need ci here. Lets talk in ci-eng.
[19:54] <brendand> jfunk, we are but ghosts
[19:54] <alesage> whoa
[19:55] <jfunk> mind.. blown
[19:55] <josepht> alesage: hrm, that sounded more like a Bill and Ted "whoa" than a Matrix "whoa" ;)
[19:55] <veebers> this is far too deep for a Friday morning
[19:56] <jfunk> good thing its thursday
[19:56] <jfunk> in normal countries
[19:56] <alesage> josepht I'm working on a ronin one too ;) , thanks for picking up that ref
[19:57] <veebers> Hey, someone has to try the Friday out to make sure it's OK for the rest of the world
[19:58] <veebers> It's a hard job but something something beer
[19:58] <ToyKeeper> I'm okay with someone QA-ing my Mondays before I have to deal with them.
[19:58] <balloons> mmmhhhh.. ^^
[20:00] <elopio> ToyKeeper: that's veebers too.
[20:00] <elopio> by the time when we arrive on monday he has already solved the problems.
[20:00] <davmor2> ToyKeeper: but veebers does that on Sunday for you
[20:01] <veebers> davmor2: wait, ToyKeepers Monday is my Tuesday, so that's what I spend Monday doing (or maybe that's what I should be doing on Sunday and that's why they are rubbish)
[20:03] <davmor2> veebers: no you are hard at work on our sunday to ensure out Mondays go without a hitch, I mean if you were online Monday morning our time some of the names they call you when things go wrong ;)
[20:03] <veebers> ^_^
[20:04] <brendand> veebers, clue, they rhyme with 'justin beibers'
[20:04] <alesage> . . . which is why it's ok for davmor2 and ToyKeeper to break everything their Fri.
[20:05] <alesage> also I had no idea this 'lockout' feature existed
[20:05] <veebers> brendand: lol, that's a good one
[20:05] <davmor2> alesage: hey no fair we deliberately break stuff to catch which developer are workaholics and fix things over the weekend ;)
[20:07] <brendand> davmor2, the answer is ogra
[20:08] <davmor2> brendand: the answer is always ogra.....who broke this ogra, who fixed this ogra, who implemented this craziness of turning off adb ogra ;)
[20:08] <alesage> this is probably the one channel he's not in
[20:09] <davmor2> alesage: we should invite him but then he'd have more work to do :)
[20:09] <alesage> davmor2, I'm finding that the lockout doesn't persist after reboot, is that a known thing?  (if so I'll correct the test)
[20:10] <davmor2> alesage: lockout?
[20:10] <alesage> davmor2, i.e. the greeter passcode lockout
[20:12] <davmor2> alesage: it works fine here on everyreboot I get 2 sim unlock screens and a pin unlock to get into the phone
[20:13] <alesage> davmor2, according to how the test is written I should still see the "device locked" screen--but it sounds like this isn't new, I'll file a bug or ask for clarification
[20:13] <alesage> davmor2, if you'll confirm pretty-please
[20:13] <davmor2> alesage: which test
[20:14] <alesage> davmor2 PMing
[20:14] <alesage> query davmor2
[20:14] <alesage> doh
[20:14]  * elopio goes away for lunch.
[20:15] <davmor2> elopio: but you can't do that you are vanguard what happens if someone has a question ;)
[20:15] <elopio> davmor2: I'm too fast for you. No vanguard anymore :D
[21:20] <dobey> davmor2: all's fair in war and testing
[21:20] <dobey> or something
[21:38] <barry> elopio: i think your last branch left a bzr conflict turd in debian/tests/ubuntu_ota_tests/tests - update trunk and notice the .THIS file
[21:39] <elopio> barry: damn it. I'll fix it, thanks for the notice.
[21:39] <barry> np