[06:43] <dkessel> good morning
[07:11] <pitti> hey dkessel, wie gehts?
[08:41] <dkessel> hey pitti :) gut, wie gehts dir?
[08:41] <dkessel> hey thetoxicarcade
[08:43] <thetoxicarcade> :D
[08:43] <thetoxicarcade> waaaaaiiiit is that ***THE*** dkessel?
[08:44] <thetoxicarcade> Hello all, I'm noticing that the ubuntu testing wikis are really really old. Do we still do classroom sessions or is this mostly erm...
[08:45] <dkessel> thetoxicarcade: sure, that's me
[08:46] <dkessel> for example?
[08:46] <thetoxicarcade> https://wiki.ubuntu.com/Testing/Activities/Classroom <-- last edit 2013
[08:50] <dkessel> mhh, looks like there were no classroom sessions in 2014 at all.
[08:50] <dkessel> do you need any information thetoxicarcade ?
[08:50] <thetoxicarcade> Quite, I would love help messing with CI
[08:52] <thetoxicarcade> I heard it was juju charms and it seems like the stuff I'm digging through involves the manual stuff (Which is good to know, too). How do I design a test that gets tested within the milestones and stuff? Know where to point me?
[08:54] <thetoxicarcade> General question for the channel too: Who is the poor soul that runs @ubuntutesting on twitter? I owe them 5lbs of bacon and a hug.
[08:58] <dkessel> thetoxicarcade: manual testcases are kept in launchpad, at https://launchpad.net/ubuntu-manual-tests .
[08:58] <dkessel> there is also a todo list ;)
[08:59] <dkessel> generally, you might want to coordinate with balloons, who is normally here during US working hours
[08:59] <dkessel> did you do any iso or package test yet?
[09:00] <thetoxicarcade> cool :D wait how should I coordinate with him
[09:01] <thetoxicarcade> I booted with testdrive once (jeepers!) but I'm still digging for where to find a test to perform
[09:20] <dkessel> thetoxicarcade: go to iso.qa.ubuntu.com or packages.qa.ubuntu.com , and then click on "testing tracker" on the left
[09:20] <dkessel> you will need to log in with launchpad to enter results
[09:22] <thetoxicarcade> cool, so I can't see any bugs on the daily build but there's an older bug for ubuntu gnome for instance. Should I just boot the iso for daily and run from the ppa?
[09:29] <dkessel> run from the ppa? you can boot the daily iso and then you can perform the tests listed von *.qa.ubuntu.com. no need for any ppas here
[09:33] <thetoxicarcade> :D (my wifi is failing but yay I think I'm set)
[14:00] <robotfuel> ping ubuntu-qa can someone review this for me? https://code.launchpad.net/~canonical-platform-qa/camera-app/fix-ap-tests/+merge/241965
[14:00] <om26er> robotfuel, I will.
[14:00] <robotfuel> om26er: thanks
[14:06] <om26er> robotfuel, can you add the date and your name to the comment and also explain a bit more about the reason you are sleeping in the code comment because right now looking at the linked bug its not clear why we are sleeping.
[14:06] <robotfuel> om26er: ok
[14:11] <robotfuel> om26er: done
[16:37] <elfy> afternoon all you quality peoples
[17:17] <elopio> alesage: that libfaketime seems really cool
[17:18] <alesage> elopio, yeah although it seems to break everything
[17:18] <alesage> elopio, also, some question about whether or not it'd be possible to change the time value after a process is started, i.e. it may just copy the env var and that's it
[17:19] <elopio> alesage: I would ask the unity apis team what do they propose to test timed things.
[17:19] <alesage> charles and I discussing earlier, there's a faked power reading in indicator-power, we might follow that pattern instead
[17:19] <elopio> if they have no proposals, we should file a bug for them to work nicely with libfaketime.
[17:20] <elopio> alesage: is power reading a dbus call?
[17:20] <alesage> elopio, yes via d-bus, looks like this in the test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/indicator-power
[17:21] <elopio> alesage: but I guess that reading the system time is not done through dbus.
[17:21] <alesage> elopio, I haven't gotten into that code as yet but sounds fun :)
[17:21] <alesage> elopio, true--indicator-datetime takes responsibility for this (at least for the title/menu bar case)
[17:22] <elopio> alesage: yes, when it's dbus everything can be nicely done.
[17:22] <alesage> elopio, yes d-bus works well with our autopilot world
[20:16] <Letozaf_> balloons_, hi
[20:16] <elfy> evening Letozaf_
[20:16] <Letozaf_> elfy, good evening to you :) how are you ?
[20:17] <balloons_> Letozaf_, why hello
[20:18] <Letozaf_> balloons_,hello :-)
[20:18] <Letozaf_> balloons_, I was looking at clock app code to see if I find out the reason why I am having problems with filemanager app
[20:18] <elfy> Letozaf_: I'm good thanks :)
[20:18] <elfy> hi balloons_
[20:18] <balloons_> elfy, hello good sir
[20:19] <balloons_> happy monday to you all
[20:19]  * elfy looks over his shoulder to see who balloons_ is talking to :p
[20:19] <knome> me i guess
[20:19]  * knome sips a beer
[20:20] <knome> unfortunately this is far from the best ones that i've had, put nicely
[20:20] <elfy> ha ha
[20:22] <Letozaf_> balloons_, happy monday to you too
[20:23] <balloons_> dkessel, are you about btw?
[20:23] <doug5> hello
[20:24] <balloons_> Letozaf_, so did you get any further with the mp for file manager? I didn't try and recreate your issue; I think you did leave some source though didn't you? if there is a branch to pull, let me know
[20:24] <balloons_> doug5, howdy!
[20:25] <Letozaf_> balloons_, this one has the last "tries" that failed: https://code.launchpad.net/~carla-sella/junk/filemanager-try
[20:25] <Letozaf_> doug5, howdy :-P
[20:25] <balloons_> Letozaf_, ok I'll pull that
[20:27] <dkessel> mhh sort of, balloons_ . at a company evening event.
[20:27] <dkessel> Everybody had BBQ and is getting tired ;)
[20:28] <elfy> more food needed then obviously :p
[20:28] <doug5> Letozaf_, bonsoir!
[20:30] <Letozaf_> doug5, bonsoir, :-P my French is not so good ...
[20:30] <doug5> Letozaf_, pretty much like mine, I guess... :)
[20:30] <Letozaf_> doug5, mmm maybe ma Afrikaans is better than my French :P
[20:31] <dkessel> balloons_: I'll read later if there's anything you want
[20:32] <Letozaf_> doug5, do you want to try and run the filemanager test I pasted to balloons on the emulator ?
[20:32] <Letozaf_> doug5, so you can see if you find out why it fails ?
[20:33] <balloons_> dkessel, no you just enjoy! I was going to ask if cameron got ahold of you
[20:33] <doug5> Letozaf_, you mean if I can run your branch on the emulator? No ;)
[20:33] <Letozaf_> doug5, lol :-P
[20:34] <Letozaf_> doug5, what problems have you got ?
[20:34] <dkessel> Yup he was there. Read the backlog... Something.. thetoxicarcade was his nick
[20:34] <balloons_> dkessel, right, I do remember seeing that now, awesome
[20:35] <doug5> Letozaf_, the same...I'm only able to run the emulator with the "desktop" profile
[20:36] <Letozaf_> doug5, oh yes, now I remember you get an error in the armhf kit, rithg ?
[20:36] <Letozaf_> right
[20:39] <Letozaf_> doug5, did you try to create a new armhf kit ?
[20:42] <balloons_> I keep losing my handle :-(
[20:42] <knome> balloons_, you got to start holding on tighter
[20:47] <doug5> Letozaf_, thing is that on my machine QtCreator crashes really a lot
[20:48] <balloons_> doug5, o? what release?
[20:49] <Letozaf_> doug5, unfortunatly I do not use QtCreator much :P I use my device for testing so I do not get a lot of crashes as you
[20:51] <doug5> balloons_, 3.1.1
[20:52] <balloons_> doug5, ahh sorry.. I meant, trusty, utopic, vidi?
[20:53] <doug5> balloons_, utopic
[20:53] <knome> balloons_, veni, vidi, vici?
[20:53] <doug5> :D
[20:54] <doug5> balloons_, Letozaf_ do you have something for me which does not imply using an emulator?
[20:54] <balloons_> knome, something like that
[20:55] <balloons_> doug5, yea any core app that is not a binary will be easy to run and hack on without the emulator
[20:55] <balloons_> calendar for example is not compiled
[20:56] <doug5> balloons_, is there anything open for calendar?
[20:57] <balloons_> doug5, yes, recently support landed (again) for the datepicker used by the new event tests for calendar in autopilot
[20:58] <balloons_> doug5, so those new event tests need to be expanded to include setting the new event
[20:58] <Letozaf_> thetoxicarcade, hello :-)
[20:58] <doug5> balloons_, do we have a bug opened for this?
[20:58] <balloons_> doug5, if calendar is interesting for you I would encourage you to join up and meet mihir and kunal who are the developers
[20:58] <thetoxicarcade> :D Hello! Question, is balloons_ balloons? where do I get the container package for unity8?
[20:59] <doug5> balloons_, ok sure
[20:59] <balloons_> doug5, yes, let me go have a look
[21:00] <balloons_> doug5, the calendar team meet weekly on IRC in #ubuntu-touch-meeting weekly at 1400 UTC
[21:00] <balloons_> thetoxicarcade, hello! ahh yes, the unity8 container
[21:01] <balloons_> I'm trying to get through all the UOS goodness as soon as I can. For now the session and notes are the best info.
[21:01] <thetoxicarcade> I'm making a 4 minute youtube video summing up what I saw from the hour long ones
[21:01] <doug5> balloons_, ok, I'll try to get in touch with them :) if there is a bug I can take just drop me an email
[21:02] <doug5> good night to everyone
[21:02] <balloons_> doug5, sure thing. is that time a good time for you?
[21:02] <balloons_> doug5, I will introduce you by email to the team :-)
[21:02] <doug5> balloons_, unfortunately not because I'm at work :(
[21:03] <balloons_> I think it will be easier since it doesn't require compliation
[21:03] <balloons_> doug5, ahh, no worries then. you'll be able to talk to the other devs easily enough still
[21:03] <doug5> yes I guess so
[21:04] <Letozaf_> doug5, good night
[21:04] <doug5> Letozaf_, ciao ciao
[21:04] <balloons_> doug5,  à bientôt!
[21:04] <doug5> balloons_, :))
[21:08] <balloons_> thetoxicarcade, awesome
[21:08] <balloons_> Letozaf_, sorry, your branch is still sitting here un-run by me :-(
[21:10] <balloons_> thetoxicarcade, ok, so here's the ppa with the container: ppa:unity8-desktop-session-team/unity8-preview-lxc
[21:10] <balloons_> thetoxicarcade, have a look at https://wiki.ubuntu.com/Unity8inLXC
[21:10] <Letozaf_> balloons_, :) I am trying to figure out why QQuickFlickable and PlacesPage objects are not seen, tried other things but had no good luck, anyway I am still trying ...
[21:11] <balloons_> thetoxicarcade, also I heard you wanted to help dkessel out with the qatracker? That would be awesome!
[21:12] <thetoxicarcade> I think the term I'm grasping for is the smoke tests or the qatracker or.. you know, the automated "sane images" stuff
[21:12] <thetoxicarcade> "vivid is 60% sane/passing on amd64"
[21:12] <balloons_> thetoxicarcade, were you able to get started on setting up a development environment? On a related note to that, I'm trying to get a charm setup for installing the qatracker, so if that's something that peaks your interest . . .
[21:13] <thetoxicarcade> (anything that impresses QA people is something I'm willing to try!) I've got lots of the testing environment ready just confused on the implementation.
[21:14] <balloons_> thetoxicarcade, yes http://ci.ubuntu.com/ more or less shows you results from the various jenkins automated test runs
[21:15] <balloons_> thetoxicarcade, simply put everyday a new image is created from a snapshot of the archive. It's built and run against a series of automated smoke tests
[21:15] <balloons_> if these tests pass the image is pushed to the 'current' image on cdimage
[21:16] <balloons_> from there, we can manually test the image and report results on the isotracker. Typically this testing is done as part of a milestone
[21:16] <balloons_> thetoxicarcade, so you are correct at the moment 67% of the smoke tests on the image pass
[21:17] <thetoxicarcade> so it's jenkins (a program or a person) that runs smoketests that display on ci, then manual tests are performed using an actual install of vivid from the instructions on the isotracker?
[21:17] <balloons_> for the desktop, that is
[21:17] <balloons_> thetoxicarcade, jenkins is a CI tool yes. The smoke tests and images are done automatically
[21:19] <balloons_> the idea is to manually test images after they've been vetted a little bit by the automated tests
[21:19] <thetoxicarcade> balloons_, yay :D so I should figure out how to: triage bugs to vet them for developers, boot and click through manual tests from the iso tracker, and then look at jenkins (which is probably written in...?)
[21:20] <balloons_> that's for the desktop and server stuff. On the phone images, the automated tests are much larger as you can see. And manual testing is done daily on them by Canonical QA folks. For now this really requires some hardware (a nexus4) but that will change soon enough with the release of ubuntu phones into the wild from oem's
[21:21] <balloons_> thetoxicarcade, well if you've played a bit with manual testing that's good. We try and automate as much as possible, so if you have the tech skills and desire I would push you in that direction
[21:21] <balloons_> this early in the cycle we don't worry too much about rigorous manual testing (like say a milestone) for desktop and server images
[21:21]  * thetoxicarcade none_whatsoever
[21:21] <thetoxicarcade> (sort of)
[21:22] <thetoxicarcade> I will probably forward a backstory to you
[21:22] <balloons_> thetoxicarcade, well you can still write and help maintain our manual testcases, which elfy is one of the resident experts for. You just need to be able to write english coherently and understand how testcases should work
[21:22] <elfy> shhh
[21:22] <elfy> :p
[21:23] <balloons_> :p
[21:23] <thetoxicarcade> <.< ._. elves
[21:23] <balloons_> Letozaf_, looking now finally
[21:23] <elfy> talking of which - balloons_ https://code.launchpad.net/~elfy/ubuntu-manual-tests/1132847/+merge/237065
[21:23] <Letozaf_> balloons_, :)
[21:24] <balloons_> after Letozaf_ I will look :-)
[21:24] <thetoxicarcade> in short, I've written code, just not much debian (yuck) ((*GASP*)) and automated testing is like, da bomb
[21:24] <balloons_> oO we never merged that
[21:24]  * balloons_ turns a little red
[21:24] <elfy> thanks - it's just been kicking about since ages ;)
[21:24] <elfy> lol
[21:24] <elfy> you wanted some changes - I did them ;)
[21:25] <elfy> ish
[21:25] <balloons_> Letozaf_, so I was going to mention that autopilot3-sandbox-run with a small tweak should replicate jenkins if needed
[21:25]  * balloons_ forgets he must build
[21:26] <Letozaf_> balloons_, oh that would be very useful
[21:27] <Letozaf_> balloons_, but if the test fails on device I have no hope it won't on Jenkins
[21:27] <balloons_> Letozaf_, yea I have a pending merge for mp.. you just need to add a line to start a wm first. you could make the change locally easily
[21:27] <balloons_> Letozaf_, right, that was for the original ? on jenkins issue. We're past that now, so it's not needed
[21:27] <balloons_> but I wanted to mention it so you could file it away as useful knowledge
[21:28] <Letozaf_> balloons_, sure It will certainly be useful for the next tests
[21:30] <balloons_> Letozaf_, so running filemanager.tests.test_places.PlacesTestCase.test_go_to_root_must_open_the_root_directory works ok on my desktop. I thought it didn't?
[21:30] <balloons_> it didn't run in phone mode though
[21:30] <Letozaf_> balloons_, on the desktop it runs fine as it uses the places sidebar and not the bottom edge
[21:31] <Letozaf_> balloons_, you have to run the test on the device or in phone mode
[21:31] <Letozaf_> balloons_, I run it on the device and it fails :(
[21:32] <balloons_> Letozaf_, weird it says it runs in phone-mode, but it doesn't
[21:33]  * balloons_ tries device
[21:34] <Letozaf_> balloons_, you have reduce filemanager window the size of a phone and you will see the bottom edge pop up and the sidebare dissapear
[21:34] <Letozaf_> balloons_, but that has to be done manually
[21:34] <Letozaf_> balloons_, so I run tests directly on the device
[21:37] <balloons_> Letozaf_, ohh looking at your code the output makes sense
[21:37] <balloons_> Letozaf_, notice you wait for the PlacesPage to appear
[21:37] <balloons_> then select inside of it
[21:38] <Letozaf_> balloons_, you mean I have to put that peace of code inside the Placespage ?
[21:39] <Letozaf_> balloons_, I was thinking of a problem of that type, but wan't quite sure
[21:39] <balloons_> Letozaf_, no I mean what I originally wanted you to do doesn't make as much sense
[21:39] <Letozaf_> balloons_, oh :-)
[21:40] <balloons_> Letozaf_, does what's in the mp work on the device as-is?
[21:40] <balloons_> I mean this: v
[21:40] <balloons_> https://code.launchpad.net/~carla-sella/ubuntu-filemanager-app/test-places-fixed/+merge/241206
[21:40] <Letozaf_> balloons_, yes
[21:41] <balloons_> so in your mp you are checking the dragging and waiting for it to complete
[21:42] <balloons_> in filemanager-try you are doing a .visible.wait_for(True).. that doesn't make sense to me
[21:42] <Letozaf_> balloons_, If you want I will run it again
[21:42] <balloons_> Letozaf_, no I'm sure it's fine
[21:42] <Letozaf_> balloons_, in the filemanager-try that was a second desperate try :-P
[21:43] <Letozaf_> balloons_, as the part commented out did not work
[21:44] <Letozaf_> balloons_, I first tried to get places page and test that it wasn't been dragged anymore
[21:44] <balloons_> Letozaf_, so I merged trunk with your filemanager-try branch trunk fixes the issue with -p being ignored
[21:44] <balloons_> makes it easier to debug on the desktop
[21:45] <balloons_> since you can add the -p to the launcher
[21:45]  * Letozaf_ is looking
[21:46] <balloons_> add the '-p' arg to launch_test_local
[21:46] <balloons_> that should make it easier for you
[21:46] <Letozaf_> balloons_, ok
[21:48] <balloons_> Letozaf_, that said it seems to run in phone mode, with your fix
[21:50] <Letozaf_> balloons_, you mean the filemanager-try :O
[21:50] <balloons_> Letozaf_, yes with filemanager-try
[21:51] <balloons_> Letozaf_, using self.wait_select_single("QQuickFlickable",  objectName="placesFlickable").dragging.wait_for(False) at the end of _drag_bottomedge_to_open_places
[21:51]  * Letozaf_ is trying on her desktop
[21:53] <balloons> woot, success
[21:53]  * balloons ponders 'what's in a name?'
[21:54] <elfy> and a,e, m and a n
[21:54] <elfy> sigh
[21:54] <elfy> s/an/and :p
[21:54]  * balloons expected elfy to quote shakespeare
[21:55] <elfy> meh
[21:55] <balloons> ROFL
[21:55] <elfy> have *you* read that stuff?
[21:56] <elfy> I believe that he was a hack - it's just no-one else's stuff lasted as long :p
[21:57] <balloons> elfy, at some point I had to read some of his stuff. Can't say it really left a large impression either way
[21:57] <thetoxicarcade> what about falstaff? poor falstaff, valiant falstaff, brave falstaff, noble falstaff
[21:57] <balloons> but I was laughing when I realized where my quote came from
[21:57] <elfy> :D
[21:57] <balloons> we'll stick with monty python for UK exports
[21:58] <elfy> well ...
[21:59] <elfy> bored with that I'm afraid - been watching that for too long
[21:59] <Letozaf_> balloons, when I run the test it runs launch_test_installed not launch_test_local...
[21:59] <Letozaf_> balloons, maybe I should uninstall filemanager from my desktop
[22:03] <balloons> Letozaf_, yes
[22:03] <Letozaf_> balloons, :( what a mess :-P probably uninstalling filemanager made a mess
[22:03] <Letozaf_> balloons, ah man
[22:04] <balloons> Letozaf_, heh.. might need to put back the depends
[22:04] <Letozaf_> balloons, :-P
[22:07]  * dkessel is back home
[22:07] <Letozaf_> balloons, it's getting late, I will fix the mess, test my test again and then push to the mp
[22:08] <Letozaf_> balloons, tomorrow :)
[22:08] <balloons> Letozaf_, kk
[22:08] <balloons> Letozaf_, buonosera
[22:08] <Letozaf_> balloons, see tomorrow, buona notte :)
[22:27] <balloons> elfy, left you some comments
[22:28] <elfy> I'll have a look in a few weeks then :D
[22:30] <balloons> perfect!
[22:30] <elfy> or tomorrow :p
[22:33]  * balloons not ready for that
[22:33] <elfy> balloons obviously forgets that xubuntu don't actually seed this thing and never test it ...
[22:34] <elfy> and elfy was just filling a need
[22:34] <elfy> ;)
[22:34] <elfy> obviously he looked today ;)
[22:36]  * balloons pictures elfy running out of fingers plugging the holes in the dam
[22:36] <elfy> balloons: you've commented "Test will require a USB stick that can be erased as well as a system that will boot from said USB stick"
[22:37] <elfy> not sure I'm understanding what you mean there
[22:37] <balloons> yea, lol, complex
[22:37] <balloons> you try and make things simpler
[22:37] <elfy> ok
[22:37] <elfy> but I still need to know what you think that sentence means first :)
[22:37] <balloons> elfy, my contribution is instead of pc or vm, just say system
[22:37] <balloons> we need a system and a usb stick
[22:38] <elfy> but shouldn't a *machine* with no OS boot it :)
[22:40] <balloons> machine that sounds fine too
[22:41] <balloons> tell you what, the next iteration gets a rubber stamp from me
[22:41] <elfy> ha ha - no, I would like it to be right :)
[22:41] <elfy> oic what you mean by system now :)
[22:42] <elfy> and yea I must have copy/pasted persistence bits in the wrong place too
[22:42] <elfy> I'll finish that tomorrow or Wednesday, then we can at least have a good testcase for people to use this cycle
[22:48] <balloons> we do have all cycle to mess with semantics!
[22:49] <elfy> lol
[22:52] <rbasak> https://jenkins.qa.ubuntu.com/job/vivid-adt-nagios3/lastBuild/ARCH=amd64,label=adt/ doesn't look right to me.
[22:52] <rbasak> Could somebody check please? Looks like a test runner failure.
[22:59] <elfy> balloons: quick one - why are big lumps of everyones jenkins ubiquity results fails?
[23:04] <balloons> elfy, right now there's fails?
[23:04] <balloons> I know on vivid images are a bit rocky in smoke testing
[23:06] <elfy> balloons: since days and days afaik
[23:06] <balloons> elfy, jibel as usual is a good one to poke on that
[23:07] <elfy> seems to be not all tests
[23:07] <elfy> ok - I'll try and remember first thing in the morning