=== chihchun_afk is now known as chihchun [04:29] * jose jose === chihchun is now known as chihchun_afk [06:46] Good Morning all [06:47] hi === chihchun_afk is now known as chihchun [06:53] elfy hey :-) [06:53] boomtown rats definitely got it right ... [06:54] lol :-) === chihchun is now known as chihchun_afk === _salem is now known as salem_ [12:54] pitti, about this apport issue, I reported bug 1226030 [12:54] bug 1226030 in apport (Ubuntu) "apport refuses to report a crash from another machine if package is not installed locally" [Undecided,New] https://launchpad.net/bugs/1226030 [12:59] thomi: https://code.launchpad.net/~thomir/autopilot/fix-state-not-found/+merge/185675 reviewed [13:00] jibel: merci [13:03] thomi: https://code.launchpad.net/~thomir/autopilot/fix-select-single/+merge/185678 reviewed [13:56] good morning team! [14:08] hey elopio 0/ [14:08] hello cgoldberg. I'm looking at your branch. [14:09] elopio, cool. it's just some general cleanup removing older idioms that won't port to py3 nicely [14:10] cgoldberg: new things to learn there. I'll take some time. [14:12] Hello everyone [14:12] jibel: I take it you already tested the new script with xvfb and xephyr, right? I'm just doing eyeball review of the MP [14:13] so with all that option parsing it became quite a bit more complex than we originally intended to :) [14:13] hello :-) Feeling a bit sore anyone?> [14:13] pitti, I did [14:13] balloons: A tiny bit sore in the legs, but otherwise OK :) [14:13] +export DISPLAY=:${SERVERNUM}.0 [14:14] jibel: ^ is that .0 actually necessary? I never append the .0 and it works anyway [14:14] (just curious) [14:14] jfunk: at what time is the next stand up? [14:15] pitti, no it is not necessary as we don't use multiple screens in Ubuntu [14:15] jibel, thomi: LGTM, approved (also if you want to re-target to 1.30 [14:15] but it doesn't hurt either [14:15] jibel: oh, that's for multiple screens? I never knew what that was [14:15] jibel: thanks [14:15] jibel: please re-target to 1.3, link a bug report, and approve [14:16] I need to AFK for a bit, talks starting now [14:16] (bug report is required since 1.3 lands in saucy) [14:16] o/ pitti [14:17] elopio, 21:30UTC [14:17] jfunk: oh, great, I'll attend that one. [14:18] jfunk: I think it will make sense to do the stand ups here instead of ##qa. [14:18] cgoldberg: why there is no xrange on python3 ? [14:19] oh, range is now a generator. That's nice. [14:21] cgoldberg: approved. [14:28] elopio, thanks.. merging [14:29] so jibel I am going to try and write everything up on the manual exploratory testing into https://wiki.ubuntu.com/Touch/Testing/Manual [14:31] balloons, okay, I started https://wiki.ubuntu.com/QATeam/TouchTesting can you move it to https://wiki.ubuntu.com/Touch/Testing/Manual ? [14:31] Heyas balloons [14:32] jibel, it matters not.. I'll use yours [14:33] link updated, https://wiki.ubuntu.com/Touch/Testing/Manual is no more :-) [14:33] balloons, would you know how to report bugs against click packas? [14:33] *packages [14:34] jibel, mm.. good question. I should make sure I can [14:34] balloons, for example I broke the sudoku, and it went all black, that's highly critical :) [14:34] hi everyone [14:35] hello rigved [14:35] balloons: hello [14:36] yesterday, i also filed these two bugs. bug #1225810 and bug #1225812 [14:36] bug 1225810 in Ubuntu Manual Tests "Duplicate tests in the Nautilus package testcase" [Undecided,New] https://launchpad.net/bugs/1225810 [14:36] jibel, well does omer's script still work in that case? [14:36] bug 1225812 in Ubuntu Manual Tests "Incorrect command given in the testcase for the Nautilus package" [Undecided,New] https://launchpad.net/bugs/1225812 [14:36] balloons, I don't think so, where is the script? [14:36] thomi, how do I retarget for 1.3, should I resubmit a new MP? [14:37] good afternoon all [14:37] rigved, those look like straightforward bugs to fix, you interested in submitting a merge to do so? I can help ;-) [14:37] i was not sure where to file the bugs to, so i just filed them against "Ubuntu Manual Tests". [14:37] balloons: that would be wonderful! [14:37] slickymaster, afternoon [14:38] balloons, hi, hope everything is fine with you [14:39] jibel, I'd have to dig it out.. remind me in a few mins to do so :-) [14:39] balloons: but i have to go out now. can i come back in a few hours? i will do propose the merge then [14:41] rigved, yes, let me leave you with a link: https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual [14:41] rigved, well might be best to start here: https://wiki.ubuntu.com/QATeam/ContributingTestcases/ [14:41] rigved, I should be around, ttyl [14:42] slickymaster, yes, everything is wonderful.. now is the most exciting time to be in QA each cycle.. it's the countdown to release and lots of things to do :-) [14:42] balloons: ok thanks. be back in a few hours. [14:46] afternoon balloons [14:47] afternoon DanChapman [14:51] going for a walk with the dog. BBS. [14:51] DanChapman, afternoon [14:53] balloons, yeah, I know, and after my three weeks off the grid, enjoying my vacations, I'm coming back fully pumped [14:54] slickymaster, wonderful! do you happen to have a device that can run ubuntu touch? [14:55] balloons: no, I've an IPhone and nothing else [14:56] slickymaster, ahh [15:07] jibel: yeah, you need to resubmit [15:07] afternoon all [15:07] elfy, hi. Nice to "see" you [15:08] hi slickymaster - good vacation I hope and it's good to see you too :) [15:08] elfy: yes, three fabulous weeks. Back again, full with energy [15:09] nice one [15:09] you'll like this - http://tinyurl.com/qf34tbx [15:10] elfy: just putting my email in order and a I'll start where I left [15:10] the list of required testcases with a xubuntu tag [15:11] om26er, if you are about, got a link to the bug reporting script you created last week for pulling bugs off the touch devices? [15:11] elfy: it's an empty list, there are no records retrieved [15:12] slickymaster: \o/ [15:12] elfy: more, at https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?field.tag=todo there is no xubuntu tag [15:12] all done :) [15:12] elfy: silly me. No I see what you meant [15:13] balloons, http://paste.ubuntu.com/6098563/ [15:13] xubuntu team is something else [15:13] slickymaster: yep but they aren't xubuntu ones - I'm not worried about those - or rather I'm as worried about them as other QA leads were opf getting xubuntu ones done [15:13] slickymaster: we won :) [15:13] balloons, which channel are we supposed to test ? what comes through phablet-flash ubuntu-system is fine ? [15:14] om26er, that's what I've written up :-) [15:14] elfy: well, that leaves me more time to work on the Xubuntu Documentation translation [15:14] nice [15:14] elfy: or do you have something that needs to be addressed? [15:14] not atm [15:14] om26er, we're building the wiki here: https://wiki.ubuntu.com/QATeam/TouchTesting [15:15] slickymaster: need to look again at autopilot at some point soon - but that's not something I can actually do [15:15] okie dokie, I'll work on the translation and helping in the forums [15:16] elfy: me too, I'll have to catch up with python, though [15:16] slickymaster: mostly it's just going to be calls for testing now - both iso's and pacjkages - and the bug with the package site is fixed - no archived testcases now [15:16] slickymaster: I don't code nor dance [15:17] elfy: well, I do code, but I would love to know who to dance :) [15:17] slickymaster, if you are interested in trying to learn autopilot there's folks here who are happy to help :-) [15:18] balloons: it's about getting autopilot to work with us still I think [15:18] I've got time now to dig a bit deeper [15:18] if you want to learn about gtk test writing DanChapman is the resident expert :-) For qt/qml stuff I guess you get me :-p [15:19] not to mention all the support of the autopilot team and others :-) [15:19] Anyone want to scan the autopilot 1.4 MP for stupid things? https://code.launchpad.net/~autopilot/autopilot/experimental/+merge/185672 [15:19] elfy: yes, I know, I'll ask for it after the I've finished my editing work in the saucy manual [15:19] hmmm [15:19] * thomi fixes conflicts [15:20] * balloons sees conflicts [15:20] lol [15:20] balloons: I'm still not sure how the autopilot 'system' works - once we've got tests for the things we want testing what do we do with them then? [15:20] is it down to asking people to test things - or is there a central setup that just does them once they are there? [15:21] elfy: we run them as part of the CI infrastructure. [15:21] om26er, balloons: for the phablet flash is it meant to test daily or the stable image? [15:21] thanks thomi - what's CI ? [15:21] davmor2, that command tests "stable" [15:21] rather flashes [15:21] elfy: Continuous Integration. Essentially "run tests for every merge proposal, and for every release to distro [15:21] davmor2, the stable images.. which a new one should land each day :-) [15:22] thomi: ok - thanks [15:22] elfy: oh, and every time we spin a new image :) [15:22] ta :) [15:22] that seems simple enough for me to understand lol [15:23] so basically, if you write automated tests, we'll make sure they get run in the right places. [15:23] Well, I say "we", but I really mean the CI team, who hang out in #ubuntu-ci-eng [15:23] yep - that makes it seem a lot more useful to me knowing that [15:25] balloons, om26er: no then you want to test daily not stable. there are two now. Stable is like alpha1/beta/rc/final and proposed is the daily. phablet-flash ubuntu-system (gets the stable which is about a week or so old now) phablet-flash ubuntu-system --channel=daily-proposed (gets the twice daily image 8 am and 8 pm utc) and --no-backup (added to the end give you a fresh image no data retained) [15:25] elfy, yep.. if there's any spare time, hah, I want to do a writeup to bring the big picture that is coming together in qa, so everyone can understand how there contributions help and what happens with the tests written [15:26] davmor2, no, for me its downloading 20130914.1.full.tar.xz [15:26] elfy, if you hear the name "Jenkins". he is the handy butler that runs tests :) http://jenkins-ci.org/ [15:26] which is pretty new [15:26] davmor2, the current stable is from 9/14 [15:26] and yes, per your description, we want stable.. the ci team is driving to release a stable once a day [15:26] balloons, om26er: then there has been another stable release [15:26] cgoldberg: I've heard that name - but didn't take much notice [15:26] davmor2, we had 3 last week :-) [15:27] * om26er would prefer for us to call it "tested" rather than stable [15:27] balloons: ah nice I'm on daily proposed and the occasional stable so I lose track of what and when :) [15:28] balloons: yep - understood [15:35] balloons: your requested features have landed in 1.3 trunk [15:35] thomi, <3 ty sir [15:38] balloons: actually, i had a few minutes now. so, i have put a branch up with the fixes here: https://code.launchpad.net/~rigved/+junk/ubuntu-manual-tests-1225810_1225812 [15:38] balloons: how do i propose it for merging now? [15:39] rigved, push it to lp:~rigved/ubuntu-manual-tests/1225810_1225812 [15:39] rigved, you can propose it for merging against the project if you have the project name instead of +junk. make sense? [15:41] balloons: could you run your eyes over this review of the current ubuntu_ap_tests http://pad.ubuntu.com/8ewWk1VpVc before i file some bugs [15:42] pitti: cgoldberg: would one or other, or both of you like to eyeball https://code.launchpad.net/~autopilot/autopilot/experimental/+merge/185672 [15:45] jibel: btw, waiting for the PS bot to approve before I set the branch to approved for landing [15:46] thomi: wohoo [15:46] thomi: still in a talk, but I've some non-talk time afterwards, queueing [15:46] pitti: thanks [15:47] thomi: but the individual bits got tested, so I guess it's mainly a question of keeping -qt and -gtk in sync and getting signoff from the bot? [15:47] I'll still have another eyeballing go at it [15:47] brb [15:48] balloons: oh ok. understood. [15:48] one moment. doing that. [15:49] jfunk: have we got any test cases from the manual test team yet? or is it too early? [15:49] thomi, still too early, I expect weds there should be something [15:50] ok [15:50] ok I think the literal bare minimum of what we are doing is in https://wiki.ubuntu.com/QATeam/TouchTesting now [15:52] DanChapman, having a look now [15:52] balloons: done. thanks a lot for your help! [15:53] DanChapman, pad's aren't liking me today [15:54] balloons: http://paste.ubuntu.com/6115478/ [15:57] cgoldberg: pitti, or anyone else, there's also the other autopilot 1.4 branches that need reviews: https://code.launchpad.net/~autopilot/autopilot-qt/experimental/+merge/185843 https://code.launchpad.net/~autopilot/autopilot-gtk/experimental/+merge/185845 and https://code.launchpad.net/~autopilot/xpathselect/experimental/+merge/185846 [16:03] thomi: I removed the things you didn't like, and I'm trying to figure out how does the qt-creator plugin works to move them there. [16:03] can you leave your approve? https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/base_autopilot_class/+merge/185170 [16:04] DanChapman, this list looks good. I think I agree on the apps that can't be added to [16:06] DanChapman, I know everything keeps changing but I'd like to talk about the role of ubiquity tests and our upcoming iso testing :-) [16:06] we'll also need to think about how much of the ubuntu-autopilot tests project goes upstream [16:07] I'm really happy with how the emulator turned out [16:08] balloons: I plan to move onto sorting ubiquity next. Should start that in the morning, So whats the plans with it. Yeah the emulators i actually think are quite cool, and rather simple from an author point of view. Just need it reviewed ;-p [16:11] DanChapman, Well long term I'd like to scope down the repetition in our iso testing as we push that into autopilot. Thus the goal is to have less manual repetition and more along the lines of new features and exploratory testing (trying to break things :-) ) [16:11] that's just been my thought process for all of the manual testing, since we're able to scale up autopilot testing now :-) [16:11] it's something to talk about with everyone [16:17] balloons: I agree, testing new features is always more enjoyable. So passing the burden of repetitive iso testing over to autopilot i think is ideal, especially with some flavors having a hard time getting testers. [16:19] DanChapman, exactly.. [16:20] wholehearted agreement from this corner ;) [16:20] DanChapman, elfy do you think starting this transition with iso testing is a good way to start? [16:21] eventually we'll want to also incorporate packages :-) [16:21] yea I'd think so [16:21] balloons: +1 [16:22] easier to find time for teams like ours for package testing - easy - quick - results for us - and a positive experience for testers [16:22] 20 minutes to fiddle about with an iso test can be a less than rewarding experience [16:23] more or less what knome was saying on the pad for qa flavours [16:23] so we should look at what we haven't automated on the ubiquity side [16:23] err, the iso testing side [16:24] basically the same review you did for each gtk app [16:25] balloons: ok no probs :-) I'll get something together and get everyone to take a look and see if there is anything else wanted. [16:26] DanChapman, sounds great.. I'm really pumped about this [16:27] At the sprint last week we spent some time putting together a plan to test the phone and essentially arrived at the idea of doing manual tests for new things, then automate them, using bugs found as a great way to add testcases. I think that basic workflow can be applied on the desktop side as well [16:28] Since we have a really nice foundation and base put together now, I think moving forward we can adopt that workflow and start the transition to more and more automation [16:29] balloons, DanChapman, elfy: I couldn't agree more with the idea of starting the transition of ISO testing to autopilot [16:30] slickymaster, so ideally for instance, the manual iso tests I'd like to see happening this cycle would be around the new ubiquity feature, ubuntu one integration., and trying to break things. Everything else ideally would be automated and looking for regressions. [16:31] we don't have ubuntu one integration [16:31] balloons: one advantage of using the autopilot would also be the accuracy of the tests [16:32] elfy: yes, exactly [16:49] balloons: thats sounds like a great idea! [16:51] balloons: i removed _build [16:51] DanChapman, I saw that, thanks.. much easier diff to look at now [16:52] anyone else seeing the battery not fully charge after hours of plugin time? [16:53] not here. [16:53] jfunk, yea, the indicator shows red [16:54] jfunk, that said the image from 9/14 I flashed this morning seems to be correct [16:55] jibel: approved your branch, should autoland now [16:55] pitti, danke [16:55] pitti, is that the autopilot-sandbox-run? [16:56] DanChapman: yes [16:56] pitti, jibel awesome! [16:56] thomi: the -gtk MP failed, I guess because it requires the main ap merge to be done first? [16:56] * pitti starts with the xpathselect one [16:58] pitti: almost, it depends on the xpathselect one [16:58] pitti: oh, actually, yeah, it'll depend on both [16:59] balloons, did you find om26er's script? [16:59] * pitti grumbles a bit about soname being independent from software version, but that's more or less stylistic [16:59] I forgot about the autopilot tests [16:59] pitti: feel free to tie them together, we never bump one without the other [16:59] but our upstream versions get mangled by the release team, so..... [17:00] jibel, yes I linked him, perhaps we also want a "take screenshot script" I wrote one of those and seems popey have a similar one as well [17:00] well in my case I upload to imgur [17:00] thomi: hm, so where in https://code.launchpad.net/~autopilot/xpathselect/experimental/+merge/185846 does it actually change the soname? shouldn't that be in some cmake-ish file? [17:00] jibel, om26er yes, I added it to the wiki, but it needs some info.. and as mentioned, popey has some stuff we should look at [17:01] pitti: yes, it is [17:01] thomi: oh, does the "set (VERSION 1.4)" apply to the SONAME? [17:01] pitti: yes, exactly [17:01] ugh, I should use the one piece of german I know and say "ya, genau" instead ;) [17:02] thomi: ok; so essentially this is the soname, and we don't care about a "release version" as we don't really release? [17:02] thomi: "ja" :) [17:02] nuts [17:02] pitti: yeah, but more like "we release every day, and the release version is mangled by the release team: [17:02] " [17:03] I guess we set the first three characters of the release version ("1.4") [17:03] but everything after that is outside our control [17:04] so, let xpathselect land [17:05] doing ap now [17:05] thomi: after that we should forward-merge 1.3 into trunk again for your fixes from this morning [17:05] hey team, I flashed this morning, but perhaps there is a command I can run to verify that the version I am running is the same as current? [17:05] pitti: yes [17:06] jfunk: there is, but I can never remember it... let me find out quickly [17:06] jfunk, adb shell cat /etc/media-info [17:06] and check the build number [17:07] that works :) [17:07] easier than what I can was going to suggest :) [17:07] nice [17:07] thx guys [17:07] balloons, ^^ one for the wiki perhaps? [17:08] jfunk, perfect, yes [17:08] balloons, and if you still have it, the link which shows current may be useful [17:08] jfunk, what do you mean? [17:09] there is a URL that shows us the current build [17:09] we passed it around last week [17:10] thomi: so, ap merge looks mostly fine, but CI fails on PEP-8 errors so you need to push some fixes [17:10] pitti: oh, which one? [17:10] autopilot? [17:10] thomi: after that I suppose it would fail for a too old xpathselect, but as that has been approved it ought to land soon and thus one of hte next ap test runs should pick it up? [17:10] pitti: yes [17:10] thomi: oh wait, that depends on actually landing xpathselect in some PPA or the distro, doesn't it? [17:10] thomi: yes, https://code.launchpad.net/~autopilot/autopilot/experimental/+merge/185672 [17:11] pitti: no, it doesn't need to land in distro [17:11] the builders have a local repository [17:11] thomi: are they using the exp PPA? [17:11] pitti: no [17:11] pitti: it's some internal archive [17:11] hey team, is there anyone who specifically has responsibility to execute a test plan that includes updating and rebooting? [17:12] pitti: if you comment-approve each MP once you're happy with it I can make sure they land in the right order [17:12] om26er? ^^ [17:12] thomi: yep, that's what I'm doing now (already done for ap itself) [17:12] awesome [17:12] reads backlog [17:13] jfunk: you mean for testing the phone image-based updates, right? [17:14] +1 [17:14] thomi: can you trigger re-runs? i. e. that magical https://s-jenkins/ link? [17:14] pitti: yes [17:14] don't get me started [17:15] that link is so totally braindead [17:15] jfunk, I don't think anyone is doing that. we do flash images in CI whenever a new image is available on which our touch testing infrastructure is based [17:16] I flash my phone daily to the latest image if that matters [17:16] jfunk, et la gema was intended to test upgrades [17:16] thomi: wrt https://code.launchpad.net/~autopilot/autopilot-gtk/experimental/+merge/185845, how are uints and doubles handled now? that parsing code went away [17:16] balloons, thx [17:17] pitti, which packages gives ubuntu-bug ? [17:17] om26er: apport [17:17] *pacakge [17:17] pitti, ack [17:18] pitti: we only support signed ints on the server side [17:18] pitti: there's code on the client side that checks the matching value, and only sends it to the server if the value is within range [17:18] balloons, here's the URL which shows current I mentioned earlier - http://people.canonical.com/~ogra/touch-image-stats/current/ [17:19] jfunk, ohh yes, that's in the wiki now [17:19] thomi: ah, and doubles are filtered on the test side? (is that client or server) [17:19] pitti: test side is client, and yes [17:20] pitti: all incompatible types are filtered client-side [17:20] this is how matching for complex types work [17:20] for example you can say: [17:20] self.assertThat(mywidget.glibalRect(Equals(Rect(1,2,3,4)))) [17:20] and it'll "just work" (tm) [17:20] cos.. magic [17:20] thomi: https://code.launchpad.net/~autopilot/autopilot-gtk/experimental/+merge/185845 reviewed, needs some dependency fixes [17:21] pitti: OK, I'll need to make a similar change for ap-qt as well [17:21] pitti, reported that as bug 1226140 -- not urgent but good-to-have [17:21] bug 1226140 in apport (Ubuntu) "apport-gtk crashes when reporting a bug for saved crash file" [Undecided,New] https://launchpad.net/bugs/1226140 [17:22] thomi: pushed another comment to that; yes, same issue for -qt [17:22] ok [17:22] brb [17:22] thomi: also this reminds me that p-autopilot needs these breaks, too; updateing that MP [17:23] hmm, they recommend >= 1.4 [17:23] that's not strictly correct, but will probably help in most cases [17:24] ^ added a comment, but not setting to "needs fixing"; add it if you like, or use it as a means to re-trigger tests later on :) [17:25] thomi: need to afk again for a bit; perhaps you could ping me with the remaining oustanding (re)reviews, and I mop them up in an hour or so? [17:26] om26er: thanks [17:27] thomi: the logging annotation: https://code.launchpad.net/~elopio/autopilot/loggging/+merge/185870 [17:35] elopio: thanks, will check it out in a second [17:35] jfunk: just a heads up, we just discovered that the autopilot libraries don't load on the phone when running with the mir shell [17:35] jfunk: however, we've pretty much ruled out any blame on the autopilot side. Gerry Boland is looking in to it [17:36] jfunk: but that's going to be a *huge* issue very soon, so we may want to suit up :) [17:40] elopio: I'm not sure you want to be using %r in your log message, do you? [17:41] thomi: what would you prefer? [17:41] %s [17:41] %r is the same as repr [17:41] thomi, I believe you, perhaps you help me suit up by explaining the issues we'll run into [17:41] whih adds quotes to the log message [17:42] jfunk: sure - want a hangout call? I happen to have some time now [17:42] thomi: both are fine for me. I'll change it. [17:42] elopio: thanks. ping me and I'll approve it once the new revision is up [17:42] thomi, is PM out of the question? [17:43] jfunk: not at all, just thought it would be easier to talk [17:45] thomi: pushed. [17:47] elopio: ok. did you run the tests with python 3 as well as 2? [17:47] elopio: I've approved anyway - it won't land if the tests don't pass :) [17:48] thomi: no. Just python2. [17:48] that's nice. [18:18] thomi, are the sphinx generated docs for AutoPilot posted somewhere? got a link? [18:18] cgoldberg: http://unity.ubuntu.com/autopilot/ [18:19] ta [18:25] jfunk: you may want to join #ubuntu-touch on freenode [18:25] * jfunk nods thx [18:26] jfunk: I didn't realise that autopilot is in "ask mode", which means all my bugfixes aren't getting released to distro [18:26] which is going to be a real PITA [18:26] apparently I need to ask my manager to get things released now, or something equally frustrating [18:27] I heard your manager is really smart and charming [18:27] but yeah, that is true, it's for a good reason [18:28] asac, how would you suggest we coordinate thomi's AutoPilot fixes to land? [18:29] I understand the reason, I don't agree that the process decided upon is a good solutioin [18:29] but.. [18:29] * thomi shrugs [18:29] jfunk: there's now at least 4 fixes to land, and I'm looking in to another one today/tomorrow [18:29] thomi, you will need to provide a good story as to how they are helping this release [18:30] jfunk: just update the landing spreadsheet [18:30] jfunk: it has it already in the Ask sheet [18:30] but it currently says: "needs FFe first" in the comments [18:30] just say its ready and what it fixes [18:30] jfunk: hey, can we have a call about this? this is totally borked. [18:30] jfunk: also if it requires us to update tests etc. at the same time to not breka them [18:31] if we're going to keep this process, then I need write access to that SS at the very least [18:31] otherwise jfunk becomes my PA ;) [18:31] i want to coordinte the asks [18:31] because we might throw stuff out [18:31] we use leads [18:32] if jfunk wants you to be that, thats fine... but please dont add every developer [18:33] asac thank you - will work this out [18:33] thomi let's mumble [18:33] sure, one sec [18:34] jfunk: is there a list of test cases that need to be automated started, where do I look to find it? [18:34] jfunk: i can't connect to mumble, has the password changed recently? [18:35] robotfuel, not quite yet, the person coordinating that is offline until weds, may get balloons to step in to mediate in his absensce [18:36] thomi, we can do GH [18:36] jfunk: I may have figured it out, one sec [18:37] jfunk: got it now - can do either mumble or GH, whichever you prefer [18:46] asac, hey, so I've talked with Thomi, we're going to give him 'lead' responsibility for the time being, he will shepherd any changes the QA team needs for this release - I'm sure he has a few questions about the ideal way to notify/update the doc with his changes which he has assured me are all bug fixes for landed code and not new features [18:46] thomi: ah, so xpath landed; how does that make it into the mystical private archive for the other tests? [18:49] pitti: should be automatic [18:54] asac, I don't have write access to the landing sheet, and as such cannot grant thomi access [18:57] asac: hm, as core devs we can just upload any bug fix without process; can't we do that with autolanding on stable branches like the ap 1.3? [18:57] elopio, can I ask you to be the click testing guy [18:57] thomi, asac: I mean, if it helps I can just take current branch and upload it manually [18:58] then I'd need to craft the changelog myself, but that's not too hard [18:58] pitti: asac asked me to not do that earlier in #ubuntu-touch [18:58] I know you've got a phone and it's come to my attention that clickpackages are suffering at the moment and we need someone committed to testing clickpackages on every current that is realeased [18:58] elopio, ^ [18:58] ack [18:58] since you're close to click anyhow.. [18:59] pitti: I'm emailing didier to find out what's going on, so I should have an answer tomorrow morning. [18:59] thomi: I guess not releasing trunk is not a bug, but a deliberate setup due to that "ask" mode? [19:00] pitti: genau [19:00] thomi: perhaps you can CC: me, then I'll send my "+1" with my core dev hat on [19:00] pitti: OK :) [19:01] pitti: email sent! [19:05] thomi: replied [19:07] pitti: wait [19:07] dont do it please [19:07] if it has impact on autopilot tests [19:07] run all autopilots first locally [19:07] if you want to do that on your own as core dev [19:07] go ahead [19:08] all that pass on current image [19:08]