[00:13] sergI was out, but looks like you sorted it. For the record it's currently 11,41 * * * * [00:14] oh, he's out now too :P [08:34] sil2100: sorry, I missed the weekly evening one. I was too devastated from my Qt5 efforts to remember that.. [08:35] Mirv: no problem, we were mostly dealing with the touch images anyway, so I'll poke everyone separately for some updates to send out to Didier some other time [08:39] hm, I see robru went ahead and switched to LP already [08:44] But he didn't clean up everything properly [08:44] * sil2100 sighs [08:45] yeah I saw the switch [09:23] hi :) [09:23] psivaa: morning [09:23] asac: morning, running the failed tests after swapping the maguro :) [09:23] plars didnt retry the failed job that would have been needed to get 100%? [09:23] or is the failure a realy one? [09:25] what a bummer :/ [09:25] psivaa: maguro and mako were down? [09:27] balloons: next one is flaki or broken test for rss reader i guess ... http://ci.ubuntu.com/smokeng/trusty/touch/mako/73:20131218:20131211.2/5532/ubuntu-rssreader-app-autopilot/ [09:27] asac: mako issue was to do with bzr error, i reran that one particular test with image 73. i think we are good on that. (i still need to figure out about the missing 1 test) [09:28] psivaa: oh cool. so we are still on 73 [09:28] thought the next image would have blown us away :) [09:28] asac: yes afaik :) [09:29] on maguro the device is flashing now with 73 for the rest of the tests [09:29] cool [09:29] psivaa: did we know why 74 didnt happen or fell over? [09:29] or did you kill it so we could finish 73? [09:31] asac: we dont have 74 yet: http://system-image.ubuntu.com/trusty-proposed/mako/index.json [09:32] interesting [09:32] Mirv: poooke [09:32] thought we had a cronned one [09:32] * asac comes [09:32] ev: pooooke [09:32] asac: pooooooke [09:32] sil2100: hi [09:32] oh right [09:32] :) [09:33] in [09:54] lool: hi! Do you have a minute? [09:55] om26er: could you take a look at https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1262127 please? [09:55] Ubuntu bug 1262127 in Ubuntu RSS Feed Reader App "test_rssreader.TestMainWindow.test_add_remove_feed_and_topic fails on #73" [Undecided,New] [09:55] it's the single fail on #73 [09:58] popey, ok, I would assume nothing changed in the app, just one of those unstable tests. [09:58] I think so, yes [10:26] om26er: also, could you validate #73 on maguro? [10:26] and update https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Ai33BkOcORLLdE4xLTFtSE80ZkpITXZ3aV85cWtPX2c&usp=drive_web#gid=0 [10:26] sil2100: #73 on mako looks good to me ^^ [10:26] (RSS reader fail aside) [10:29] popey, sure in a meeting. will test afterwards [10:30] popey: thanks! [10:36] thanks om26er [10:37] lool: hello! Could you please kick a new image once you're around? [10:37] lool: I guess it makes no sense to block on UITK [10:37] who can help me with constantly exploding autopilot on ci? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4168/consoleFull I haven't found out much but it's quite critical to solve that at this point since it affects all ui toolkit merges [10:37] cihelp: ^ [10:46] sil2100: block on UITK? is something broken? [10:49] timp: no no, all is fine with the component itself - it's just blocked in -proposed right now [10:50] timp: it seems webbrowser-app got seeded in the desktop, so it pulls in UITK and - since we're in Alpha freeze, we would need an exception to get UITK to the release pocket [10:51] timp: we might try getting it in anyway by asking the release guys, but it didn't make sense to wait with this image right now for this to happen [11:22] Can anyone help with "W: GPG error: http://ppa.launchpad.net trusty Release" - e.g. https://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/475/consoleFull (we have several like this) [11:25] psivaa: so the rerun of 73 didnt help it seems? [11:26] rssreader on mako that is [11:26] hmm. seems it was not retried [11:26] https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-ubuntu-rssreader-app-autopilot/ [11:26] asac: i did not re-run mako rssreader. i was running sdk which failed due to a temp bzr issue [11:27] sorry did not know if i had to re-run mako rss reader [11:28] psivaa: the goal was the 100% [11:29] psivaa: can you do that? [11:29] we had folks working long last night to get that [11:29] asac: i could re-run that, but i thought the last decision was not to re-run flaky tests. but i'll rerun that now [11:30] well, we want to know if tis a flaki or not [11:30] this one never failed [11:30] so we need to retry to know [11:30] well it failed a few tiems, bue rarely [11:30] psivaa: i think that decision was too black and white [11:31] it makes no sense to not rerun a test that succeeded and now is red [11:31] if its flaki its important. if its a regression its critical [11:32] asac: ack, running that now. [11:32] psivaa: you should really be in the meeting again [11:32] otherwise its unaligned [11:32] even if you dont say much :) === alan_g is now known as alan_g|afk [11:33] asac: will attend that tomorrow [11:37] asac: the rssreader in mako has become successful.. so it's not a regression but definitely flaky :) [11:41] kalikiana_: there appears to be a problem with the command that is being run [11:48] psivaa: good news, thanks [11:48] popey: yw :) [11:49] cjohnston: can you elaborate on that? [11:50] the command would be the same on any machine as far as I see… how would it break only on one? [11:56] kalikiana_: the fact that it seems like its trying to take every letter as an individual arg. === alan_g|afk is now known as alan_g [11:57] kalikiana_: -testability doesn't seem to be a valid option [11:57] cjohnston: it doesn't explain this failure as those errors existed before (I filed a bug for it because indeed it doesn't look healthy) [12:00] kalikiana_: I guess I don't understand? -testability doesn't appear to be valid and appears to be what's causing the issues. can you show me a job where it worked? === dpm_ is now known as dpm [12:03] popey, this should fix the issue: https://code.launchpad.net/~om26er/ubuntu-rssreader-app/strenghten_flaky_test/+merge/199447 [12:04] plars: just to give you a brief update of the touch runs: [12:05] plars: maguro-07 fell off the adb for some reason, not even showing as offline today. so i assigned a the latter parts of the touch smoke runs to use maguro-01 [12:06] plars: i did this change manually to get to the full results, sooner. [12:07] cjohnston: as a matter of fact I can't because jenkins erased all old successes I can find… [12:08] plars: i also understand that we are now re-running the flaky tests to see if they are real regressions [12:08] kalikiana_: with my limited understanding of the medium tests, I can only state what I see, which is that -testability doesn't appear to be an option, and it looks like its causing failures [12:09] om26er: testing.. [12:13] 13:12 on my lockscreen !!!! [12:13] * ogra_ hugs sil2100 [12:14] cjohnston: I get you. I can only tell you it's been there before :-( [12:21] anyone around that can confirm that in img 73 in th nexus 7 you cannot install click packages? [12:23] mandel: what happens? [12:23] (I only have n4, not n7) [12:24] balloons: mhall119 when you get a moment can you happrove https://code.launchpad.net/~om26er/ubuntu-rssreader-app/strenghten_flaky_test/+merge/199447 please [12:24] popey, hi, I'm trying to ensure that the new udm does work with the latests image, to do so I want to make sure that installing click packages work as expected but in my nexus 7 when I click on install the package is not downloaded [12:25] popey, and nothing happens, but that is with the img 73 and not installing udm from trunk, so I'd like to confirm that it is broken before I dig deeper [12:25] oh, well i just tested on 73 on nexus 4 and it worked.. [12:28] popey, hm.. sounds weird that it will only be a nexus7 issue.. and I have no nexus 4 to test with.. [12:29] * mandel shakes fist in the air [12:52] ogra_: ;p === alan_g is now known as alan_g|lunch [13:06] sil2100: Hey [13:06] sil2100: I am on leave today, but I can kick an image right now if you like [13:06] sil2100: While I'm at it: I'll be back Thursday but then on leave Friday inclusive til second week of jan [13:08] I see the last image is from 3:42am, so I'll kick one unless one is building [13:08] building [13:09] * rsalveti is sad to see that we're not dropping the landing plan spreadsheet this week [13:10] rsalveti: +1000 [13:11] sil2100 asac we should release #73 - it's 100% green [13:21] popey: thanks! Let's do so (just got back from errands) [13:21] lool: thank yoU! [13:21] lool: are you still around to do a promotion? [13:49] .... even at 100% it's not automatic?! =) [13:51] ;) [13:51] * sil2100 wonders who else has the powa to promote an image [13:51] xnox: do you have the powaaa to do so? [13:51] sil2100: no. [13:52] popey: are you aware who besides lool can promote an image? Can cjwatson (if he's around at all) [13:52] ? [13:52] In principle. I've never done it before [13:53] But the invocation is supposedly written down [13:53] So give me image numbers and I can try [13:53] hm [13:53] cjwatson: hello! Didn't want to bother you for no reason, just looking for anyone that can do it - I was only aware of lool in this timezone: the image needing promotion is #73 [13:54] It's anyone in the intersection of ~ubuntu-cdimage and ~canonical [13:57] sil2100: in progress [13:57] popey: you checked the new ubuntu-system-settings background changing on image 73? Just making sure if that was double-checked [13:57] cjwatson: big thanks for helping out :) [13:58] sil2100: yes, it works [13:59] ugh, now I have a crappy picture as my background. [13:59] sil2100: there's an import-images job running at the moment, so it'll hopefully copy after that's done [13:59] how do I revert this? [13:59] Waiting for other process to release the global lock === retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [14:01] popey: I didn't upgrade to the latest yet, so I don't know! Only Ken would know! [14:01] ;) [14:03] psivaa: ack, they were still running when it was late for me last night, but I saw there were some new failures on the way [14:03] asac, psivaa: is that true? We are rerunning flaky tests again now? Last I was told, we don't do that now. [14:05] psivaa: dialer-app stil crashing it seems on mako, but otherwise totally green [14:06] psivaa: but sounds like there was still some rssreader flakiness there? === alan_g|lunch is now known as alan_g [14:08] fginther: can you help with "W: GPG error: http://ppa.launchpad.net trusty Release" - e.g. https://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/475/consoleFull (we have several like this) [14:10] plars: we have to knoww hwether we have a regression [14:10] we cant tell it without rerunning them [14:10] we must record and escalate every single flaki test though [14:11] asac: ok, we are getting a mixed message then, previously we were specifically told NOT to rerun [14:13] plars: i think the difference is that you were told by didrocks not to _arbitrarily_ re-run them. asac is specifically saying we need to record (and thus fix) the flaky ones (which we have) [14:13] .. _then_ re-run [14:13] right. i need a summary of flaki tests at each end of the day [14:13] in this case it was not clearly flaki... we had like 5 days green [14:14] today red... so knowing whether its a rare flaki one etc. also helps [14:16] asac: understood, just wanted to make sure I was clear on the change. I'll plan on going back to staying up later to rerun if the tests aren't done. At least for this week... do we need any kind of coverage for this over the holiday shutdown? or do we just let things roll and see what happens on the other side [14:17] retoaded: can you help with "W: GPG error: http://ppa.launchpad.net trusty Release" - e.g. https://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/475/consoleFull (we have several like this) [14:18] morning [14:19] * alan_g discovers that his 32bit machine exhibits the same problem cross building for android. [14:20] fginther: morning. Did you see my question? [14:21] alan_g, yes, looking [14:23] alan_g: ppa:phablet-team/ppa doesn't appear to have trusty [14:23] also, why is that looking at http://archive.ubuntu.com/ubuntu for armhf, rather than http://ports.ubuntu.com/ubuntu-ports? the whole thing looks misconfigured. [14:24] correct, there's is basically nothing in ppa:phablet-team that you would need [14:24] ah, it's because you need [arch=i386] on that sources.list line [14:24] (the archive.u.c one) [14:28] cjwatson: is that something I can fix? [14:29] Don't know [14:30] I guess you could do it in the same way that you're evidently already echoing lines onto the end of sources.list [14:30] + echo 'deb [arch=armhf] http://ports.ubuntu.com/ubuntu-ports/ trusty main restricted universe multiverse' [14:30] + echo 'deb [arch=armhf] http://ppa.launchpad.net/phablet-team/ppa/ubuntu trusty main' [14:30] alan_g, the test is using a trusty-i386 chroot used by the regular i386 builds [14:31] alan_g, cjwatson, we can try it that way [14:31] so sed -i 's/$deb $$http://archive.ubuntu.com/ubuntu$/\1'"$(dpkg --print-architecture)"'\2/' /etc/apt/sources.list [14:31] or some such [14:31] er [14:32] sed -i 's/$deb $$http://archive.ubuntu.com/ubuntu$/\1 [arch='"$(dpkg --print-architecture)"'] \2/' /etc/apt/sources.list [14:32] adjust paths etc. as appropriate [14:35] fginther: something you can fix? [14:36] alan_g, should be able to, working on it now [14:36] sil2100: I believe it's promoted now [14:36] fginther: cjwatson thanks [14:36] I got a traceback, but it seems to have published anyway [14:36] Traceback (most recent call last): [14:36] File "/srv/system-image.ubuntu.com/bin/copy-image", line 299, in [14:37] os.remove(lock_file) [14:37] OSError: [Errno 2] No such file or directory: '/srv/system-image.ubuntu.com/state/global.lock' [14:39] cjwatson: \o/ Thanks! [14:39] plars: sorry, just came back from lunch. guess you had the answers already? :) [14:41] psivaa: yep, thanks [14:46] alan_g, how does this look so far? http://s-jenkins.ubuntu-ci:8080/job/mir-android-trusty-i386-build-fjg/5/console [14:46] plars: i have not fully converted all the jobs to use maguro-01 again [14:47] plars: is that by changing the production.py and then run the setup again.. or is there a specific way to run setup just for this device? [14:47] psivaa: actually, you don't have to change production.py, just go with the default in it - only make sure no other jobs are running at the time [14:48] psivaa: when I changed it yesterday, I created a custom config file for *just* that line of jobs moving them over [14:48] psivaa: that way none of the other running jobs would be impacted [14:49] plars: ahh that's what i was looking for [14:49] plars: would be helpful if you could send me that if that's handy [14:50] psivaa: just copy/edit production.py, but if there's nothing else running, there's no harm in running through the full set [14:50] plars: ack, thanks. will do that. [14:50] fginther: it seems that wasn't the real issue - as the build is failing anyway. [14:50] ah, that reminds me... [14:51] but cwayne isn't here :( [15:09] popey: top-approved, what do we need to do to let you do that? [15:10] mhall119: I don't want to [15:10] I approved, I dont think its appropriate that I approve and happrove. [15:10] I *can* already [15:17] * balloons checks landing asks [15:17] you going to have sergio pull the rss update? [15:19] we need to [15:25] popey, just make sure you frame this: http://ci.ubuntu.com/smokeng/trusty/touch/mako/73:20131218:20131211.2/5532/ [15:30] popey: the rssfeed app flaky test got fixed \o/ ? [15:33] sergiusens: can you release rss to the store please? [15:33] once that lands. [15:35] popey, sure [15:39] Damn, something's wrong with me and testing on devices [15:40] [Wed Dec 18 15:38:32 2013] Buffer I/O error on device loop0, logical block 424267 [15:40] [Wed Dec 18 15:38:32 2013] lost page write due to I/O error on loop0 [15:40] thats bad isn't it? [15:40] [Wed Dec 18 15:38:32 2013] loop: Write error at byte offset 1716699136, length 4096. [15:41] http://paste.ubuntu.com/6594839/ [15:43] popey: I have no problem with an approver top-approving, as long as they aren't the author or submitter [15:55] ralsina, lool all udm branches are in trunk, code was tested and re-tested on devices, so we are ready to land it in the new img, as ralsina told me with risk because of course if we break we break the update path [15:55] but I have tested that path too :) [15:55] psivaa: gallery-app had some problem on maguro, did you move them all back to 01 already? [15:55] lool: of course mandel *did* try an manual update with this version isntalled but... [15:55] lool: just being careful [15:58] did something bad just happen to jenkins? [15:58] all the logs linked here give me a 404 https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/headerHeightInit/+merge/199468/comments/463176 [15:59] timp: it might not have been published yet, if you have VPN access you can use the s-jenkins versions of the links [16:01] timp: i.e. replace https://jenkins.qa.ubuntu.com with http://s-jenkins.ubuntu-ci:8080 [16:07] popey, balloons https://myapps.developer.ubuntu.com/dev/click-apps/155/ [16:07] sergiusens, "You just tried to access a feature which you don't have permission to use." [16:07] hah [16:07] balloons, sorry, it was an fyi for you ;-) [16:08] :-p [16:09] just fyi sergiusens I have a music app pull for you too in landing asks [16:10] sergiusens: ack [16:10] balloons, if these asks were bugs assigning to me would make me notice [16:10] pun :-) [16:12] plars: not all of them.. but gallery-app was rerun once more on maguro-01 [16:15] psivaa: what do you mean not all of them? we can't have a situation where some tests are on one phone another others on a different one [16:16] kenvandine: hello! :) [16:16] howdy sil2100 [16:16] kenvandine: can you approve? https://code.launchpad.net/~sil2100/cupstream2distro-config/missing_extra_pkgs_unity8/+merge/199495 [16:17] plars: i know. but i earlier changed the jobs that failed on 73 to use maguro-01. got distracted in the sprint before converting all of them [16:17] sil2100, done [16:18] psivaa: those are likely not running on the right version then... [16:18] kenvandine: thank you! [16:20] plars: yea, they are not..sorry. [16:21] plars: i'll abort them, reassign them to maguro01 and rerun them [16:21] psivaa: I was just going to suggest that - if you are busy with the sprint stuff, I'm happy to do it [16:21] psivaa: I know you're kinda tied up right now [16:22] plars: yea, concentrating on both does not help do either of them right :) [16:22] plars: so would help you do that [16:22] sil2100: i wont be at the landing meeting this evening. I have a train to catch [16:22] if you could do that [16:22] psivaa: absolutely, I'll take care of it now [16:22] plars: thanks [16:22] popey: ok, no problem - thanks for testing the image green! [16:30] psivaa: it's rerunning now [16:37] thanks plars [16:38] sergiusens: approved [16:39] balloons, btw, have you been doing manta on these? [16:39] cihelp is there an ETA to enable manta tests or is that waiting on definitions of other things? [16:40] sergiusens no ETA that I'm aware of atm; fginther? ^^^^ [16:40] sergiusens, both manta and maguro are likely to have some fun twists [16:40] sergiusens: as far as I know, they can be turned back on whenever they are needed, I'll need to confirm that the devices are still physically connected [16:41] sergiusens, I haven't seen any formal requests for this [16:41] plars, they are not connected atm unless rfowler has done that in the past day or so [16:41] sergiusens: and since we've made a lot of changes since the last time they were run, I'll need to add them to the job configs, but for smoke at least, I don't think it should be a huge problems [16:41] which I doubt [16:41] oh [16:41] just some "it would be nice to have" discussion [16:42] * plars is entirely too optimistic :) [16:42] oh, I'm just saying that since tablet was supposed to be one of the development focuses [16:42] nothing to stress about until next year ;-) [16:42] sergiusens, then it should be something we need to add. We'll probably need to order some hw, I doubt we have enough to cover all the testing [16:43] yeah, makes sense [16:44] sergiusens, do you know who is driving the platform definition? [16:49] fginther, upper management i think [16:49] sergiusens, ack [16:58] ricmm: in https://wiki.ubuntu.com/Process/Merges/Checklists/Common, why are we privileging pbuilder? Foundations generally recommends the use of sbuild, especially for cross-building [16:59] ricmm: there may well be a mismatch here between different teams' tools, which may be fine, but if so we should use more neutral language [17:01] asac, robru, kenvandine, cyphermox: meeting! [17:01] cjwatson: legacy brain [17:01] please change accordingly [17:01] balloons: ^ [17:02] ricmm: ok, neutralised slightly [17:03] sil2100, coming, running over [17:04] sil2100: latish [17:04] will check here for pings [17:05] asac: ok [17:05] cyphermox: hangout if you have a moment :) [17:10] cjwatson: thanks! [17:22] sil2100, feel free to assign me a bug about qtorganizer. my edit rights on the spreadsheet have been revoked, which means the only way for me to track my progress is with bugs. [17:24] sil2100: are you still on? [17:24] in the HO? [17:24] seems not [17:24] damn [17:26] we just finished [17:26] like, 2 minutes ago [17:47] balloons: do we have confirmation that the rssfeed app fix is in? [17:47] (by in I mean in ready to be fetched by an image) [17:53] sil2100, looks like sergio dropped.. so let's see === retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - === barjavel.freenode.net changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: - [18:13] balloons: ok, let's not wait on this any longer, let me ask cyphermox to kick a new image [18:13] cyphermox: could you press the 'build new image' button for us? :) [18:14] sil2100, sorry for the delay. I confirmed the version instore is the new one from this morning [18:14] afaict, it's in and ready [18:14] so you should be good.. I literally just found the info I needed ;-p [18:16] :D [18:16] And Sergio just appeared when you did ;) [18:19] sil2100, did you get a ping form ralsina about ubuntu-download-manager? [18:20] mandel: hi! hm, no, I don't think so - but maybe I missed the ping inbetween things [18:20] mandel: what is it about? [18:21] sil2100, we have finally landed all the bug fixes we wanted in trunk (it is in the spreadsheet already) and everything was reviewed and tested [18:21] sil2100, is a 'critical' update because if the ubuntu-download-manager is not working properly , well system image updates wont work, I'm mentioning that even though it is very well tested [18:22] sil2100, tomorrow is my last day before the xmas break and I'd love to go knowing that it is in the image :) [18:22] and workin [18:22] g [18:23] mandel: thanks for the heads up! Let me check the spreadsheet, maybe we can land it today even - is this change has a high-risk-factor? [18:24] sil2100, that would be perfect, that way if there is an issue I'll be around to get it fixed :) [18:24] sil2100, the bugs are mainly performance related (faster and less memory) [18:33] sil2100, wrt to music app, I'm testing the click and uploading [18:33] mandel: ok, so you're 100% sure that ubuntu-download-manager things are ready to land, yes? [18:33] sergiusens: thanks :) [18:33] sergiusens: let me add it to the spreadsheet then [18:34] sil2100, yes, unit-tested, tested, re-tested, got scared, re-tested sure [18:34] ;) [18:34] mandelm sil2100: sorry did not ping yet, was on a meeting :-) [18:35] sil2100: mandel has sworn on a stack of bibles [18:35] sil2100, it was already on the spreadsheet iirc [18:35] sergiusens: yes, but not in Landing Plan - only in Asks [18:36] But I added it and assigned to you [18:36] kenvandine: hi! How busy are you today? ;p [18:36] sil2100, ack, the deal I made with didier was that as long as a click is in asks I'm free to update the status from there; I can work this way as well [18:37] mandel, ralsina: could you guys give us some good testing ideas for this? [18:37] sergiusens: oh, ok, wasn't aware of that ;) I don't mind! [18:37] It's just paper-work [18:37] sil2100, sure, I have two really good ones, do you want me to send you an email? [18:37] sil2100, or over here? [18:37] sil2100, well i'm trying to avoid distractions to nail some stuff down before the holiday [18:38] sil2100, but i can help out where needed [18:39] kenvandine: could I assign something to you? You could also ask robru for some help and/or just re-assign it to him ;) (just he doesn't have write rights to the spreadsheet) [18:39] kenvandine: it's ubuntu-download-manager, it's in the plan [18:39] ok [18:39] sil2100: well, one is downloading and installing an app [18:39] mandel: could you send those test-cases to kenvandine and robru ? Thanks! [18:39] sil2100: the other is much trickier which is testing an image update. You surely see how that's hard to test :-( [18:41] sil2100, sure, will add you too [18:41] sil2100: are we promting 74? [18:41] did this image come out 100% without retrying? [18:41] plars: ? [18:42] asac: 74 I still don't see maguro final results [18:42] ralsina, mandel this may be an aproximation: mount -o remount,rw / && dpkg -i udm.deb && reboot && system-image-cli [full update download options] [18:42] asac: on mako, I haven't tried anything yet, I'm rerunning all of maguro right now because there was some doubt about the device it was running on [18:42] sil2100: ic... but we have testing done? [18:42] plars: mako seems 100% without retry... wow :) [18:42] asac: so I wouldn't promote that, also popey didn't test-ACK that yet manually [18:42] asac: there were 2 crashes on mako though [18:43] asac: since I guess he's still driving somewhere, so he's off [18:43] sil2100: right, are we trying to get the test feedback on 74 and promote or are we going for 73? [18:43] asac: one of which was in system-settings tests [18:43] sergiusens, ok, that is actually a quite good one [18:44] plars: right. [18:44] crashes are not good [18:44] havent [18:44] are they new? [18:44] or flaki/before? [18:44] asac: calendar is still failing on maguro (has been for a while now) and music hit a failure that seems to be on and off.it's running the calculator tests now so a bit more than 50% of the way through it seems [18:44] asac: 73 we promoted already, as mentioned in the update e-mail [18:44] ah cool [18:44] then lets ensure we get the issues with the current image sumamrized [18:44] asac: the dialer-app crash is definitely not new, the systems settings one is though [18:44] SInce it had 100% green on mako and no issues in manual testing ;) [18:44] so we can escalate and have folks look [18:45] Indeed! [18:45] * sil2100 needs to go soon [18:45] plars: right. and we got a new system-settings? [18:45] sil2100: do the system settings folks know about the regression? [18:45] and are working on it? [18:45] sil2100: after thats kicked off, call it a day :) [18:45] hehe [18:46] I don't think so, but there was one recently [18:46] mandel, glad to help [18:47] sil2100: still need a rebuilt? [18:48] cyphermox: yes, I mean, we need a new image kicked ;) If you didn't kick one yet of course! [18:48] asac: which regression? We don't run system-settings tests on smoketesting? [18:48] sergiusens, one question, should I specify where to find the .deb or it is assumed that it is from trunk? [18:49] done [18:49] cyphermox: thank you [18:50] mandel, for a landing request I would assume trunk, and if it's in daily release it may be the daily release ppa or if you get stuck on proposed the one in proposed [18:50] sil2100: plars was talkinga bout system settings crashes [18:50] those i refer to [18:51] mandel, really depends on how your project was setup [18:51] sergiusens, ok [18:51] mandel, which sadly isn't really consistent [18:51] sergiusens, afaik there is a daily ppa, I need to check that [18:53] mandel, this one perhaps https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=download&field.status_filter=published&field.series_filter=trusty ? [18:54] sergiusens, it is that package, but not that version, that is very old... [18:54] I wonder what has happened :-/ [18:55] ralsina, I'm sorry to do this.. but can you take a look, is close to 20:00 here and I should stop working soon [18:56] cyphermox, sil2100 when you daily release ubuntu download manager does it get stuck in the daily build ppa until someone promotes it? [18:56] mandel: of course [18:56] ralsina, thx, I really appreciate it [18:56] ralsina, then EOD for me [18:57]