[00:50] Saviq, was it you that mentioned the MP hover urls are hard to click in the dashboard? I changed it so the hover behavior only appears when there's no search term in use. If you search for something, all MPs unhide for easier clicking. http://people.canonical.com/~platform/citrain_dashboard/#?q=mir === robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #119 promoted | Need CI Train help? Ping: robru, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [01:21] stgraber, hey, can you set up the lp project so that lp:queuebot points at the right place? [01:23] robru: sure [01:23] stgraber, also it looks like lp:~ubuntu-archive/queuebot/queuebot doesn't have the latest code that's in production? it seems like you pushed the revert but then didn't push the final code that went into production [01:23] stgraber, thanks [01:24] robru: should be all fixed now [01:24] bah popey you're asleep by now. i'll push fm [01:24] stgraber, sweet, thanks. I'm about to make a small tweak to help future-proof it a bit [01:27] popey, mmm.. scratch that.. the version is com.ubuntu.filemanager_0.3.latest_armhf.click. I don't like that, not going to push it [02:05] === trainguard: IMAGE 134 building (started: 20140716 02:05) === [02:09] I'm assuming that's some kind of test? :) [02:10] yep ;-) [02:10] testing my queuebot changes actually [02:12] hehe, ok, looks good. [02:18] stgraber, https://code.launchpad.net/~robru/queuebot/future-proofing/+merge/226948 when you get some time ;-) [02:27] robru: yep, got the e-mail, will look at it tomorrow [02:27] stgraber, cool, thanks [02:37] ogra_: popey: in the ubuntu/silo-003 there is new upstart. Can you please install upstart from it onto mako & flo and check that things generally work? e.g. try out a few auto-pilot tests, starting/killing apps, booting etc. [02:37] the testing has passed everywhere, so testing on normal flo and normal mako are the last things to try out. [02:37] i've tested on mako - dualboot install already. [02:38] plars: psivaa-off: if you can try out upstart from ubuntu/landing-003 on phones that would be great. [02:57] d'oh [02:57] * veebers fixes [03:40] === trainguard: IMAGE 134 DONE (finished: 20140716 03:40) === [03:40] === changelog: http://people.canonical.com/~ogra/touch-image-stats/134.changes === [07:34] robru: can you get this landed? https://code.launchpad.net/~pete-woods/u1db-qt/transaction-around-schema-init/+merge/226221 [07:48] kalikiana: I guess u1db-qt is a bit special case with rare landings and no designated lander. let's start by me adding a line for that, and putting you as the lander by name [07:48] kalikiana: what kind of test plan there would be for u1db-qt? [07:49] Mirv: running the unit tests. there's no gui bit, any known bugs are added as unit tests [07:50] kalikiana: it seems archive is not in sync with trunk, build failed [07:50] oh wow, it hasn't changed in a while, though [07:50] fixing, just some small direct upload === psivaa-off is now known as psivaa [07:52] fixed, rebuilding [07:52] much appreciated! [07:53] kalikiana: there are certainly some gui bits that use u1db-qt? manual testing of those would sound like a good idea, so that there wouldn't be surprises. [07:54] Mirv: oh apps yes, such as clock app [07:54] sorry for the confusion [07:54] it seems there is no formal test plan for clock either :( (looking at https://wiki.ubuntu.com/Process/Merges/TestPlan/) [07:54] but it might be the only one core app; not sure if community stuff can be used for testing [07:55] ok. manual testing of clock app at least should be done, then. [07:57] * cjwatson yawns === cjwatson changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #119 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [07:57] (unity is also making use of u1db now but… not sure if I want to suggest that as a test case :-o) [07:58] So how's image 134 looking? [07:58] Oh, Selene wasn't too happy with it, hmm [07:58] it looks bad, for whatever reasons [07:59] 133 was almost normal [07:59] And only one free silo [07:59] qtcreator plugin should probably migrate soon [08:00] Well, 9 will free up shortly, yeah [08:00] Was just checking that [08:03] bzoltan1: ran it for you [08:04] Mirv: thanks! [08:10] What the heck happened with 134?! [08:10] psivaa: do you have any idea what's going on with the smoketesting there? [08:11] sil2100: yea.. looking at that. one flashing failed (adb wait-for-device dint comeback detecting the device) [08:12] sil2100: the other is with dropping-letters tests. the step 'Selecting objects of type QQuickRectangle with attributes: {'objectName': 'gametilebox'} is repeating infinitely [08:13] it got addicted and cant stop playing ;) [08:13] sil2100, there is also the mail from ToyKeeper [08:13] :| [08:14] I give up :| [08:14] ;) [08:14] what she describes looks suspiciously like an oversight in https://launchpad.net/ubuntu/utopic/+source/unity-system-compositor/0.0.4+14.10.20140715-0ubuntu1 [08:14] iirc the dailer-app has "special access" to power mgmt [08:19] I think we need someone looking at it ASAP [08:20] It's like damn, can't we get an image that doesn't get stuff broken? [08:20] When did we have that unity-system-compositor upload? [08:20] * sil2100 checks [08:22] It was in 134 [08:22] So I would suppose we can still think of 133 as a promotion candidate, in case it's free of this regression [08:22] ToyKeeper: hey! Are you still around? :) [08:23] Wasn't there a blocker in 133? [08:23] Tablet support? [08:23] cjwatson: it got fixed in 133 [08:23] Ah, right [08:24] cjwatson: 133 had the fix for the tablets already, then 134 landed unity-system-compositor that 'might' be responsible, we need to check that and maybe revert/have someone working on it [08:31] ogra_: I'll be there in a moment [08:58] Any objection to publishing 11? [08:59] sil2100: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1342602 [09:00] Ubuntu bug 1342602 in telephony-service (Ubuntu) "Cannot make or receive calls on #133 (and possibly before) mako" [Undecided,New] [09:01] popey: thanks! :) [09:01] ricmm: hey! [09:02] ricmm: we noticed strange stuff happening on 134, we're thinking if your unity-system-compositor upload is not to blame [09:03] sil2100: i can flash back to a previous image if you like, to see how far back it goes before phone calls work... [09:03] if so, do you have a suggested image to start from? [09:03] sil2100, a lot of the failing suites seem to have an associated unity8 crash [09:05] popey: could you maybe revert back one more image then? [09:05] popey: like, to 132? [09:06] ok [09:06] We'll know then if telephony-service was at fault === vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: vila | CI Train Status: #119 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [09:08] sil2100: silo 11 isn't likely to interfere with this, is it? it looks fairly innocuous aside from being a transition [09:09] And I'm sure it'd be nice to have one less big silo to conflict with [09:11] cjwatson: hm, I'm always weary of big landings with many components, but I guess in this case it's just a lot of rebuilds against the new dbus-cpp, right? [09:12] Right [09:12] cjwatson: the change in dbus-cpp itself doesn't seem to be super risky, just hope they rebuilt all rdeps [09:12] cjwatson: I would say publish [09:12] sil2100: brendand: i saw 'Selecting objects of type QQuickRectangle with attributes: {'objectName': 'gametilebox'}' being repeated in the dropping letters test on manta too.. [09:12] so this doesn't look like a one off one [09:12] uh [09:12] Not really sure why because it only added ABI, it wasn't a soname change [09:13] But C++ :-P [09:17] sil2100: #132 broken too [09:17] What the... [09:17] Ok, let me try getting a sim card for my phone maybe [09:17] Since it obviously worked for Selene [09:18] wut [09:18] oh, arm64. I think that test is flaky, will retry [09:18] sil2100: going back further, to 127 [09:18] ogra_: I'll have to jump out for a train in some moments (and will not have connection for some time) - if Omer appears, could you ask him to check if 133 works connectivity-wise? [09:18] sil2100: before urfkill was updated [09:18] mandel: I'll coordinate publishing of 11, will just take a little while [09:19] cjwatson: thanks o/ [09:19] popey: good idea, thanks :) [09:19] cjwatson, you are my hero! [09:20] cjwatson, I need to take a look at those flaky tests, we cannot be dealing with them all the time [09:20] Yeah [09:21] cjwatson, lord.. it looks like conectivity api was not built.. again :-/ [09:21] Right, I've retried and am waiting [09:21] cjwatson, ah, ok, I can see the following => https://ci-train.ubuntu.com/job/landing-011-1-build/120/console [09:21] cjwatson, looks like it was built, right? [09:22] I don't know why that didn't notice, but it's lying [09:22] * sil2100 goes for the train [09:23] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-011/+build/6184387 is the previously-failed build in question, currently retrying [09:24] cjwatson, ack [10:01] cjwatson, i think keeping access to proposed blocking vs image building distinct through different teams makes sense ... even if it is extra ovehead [10:04] ogra_: any idea how to debug the modem issue on my device, until awe wakes? [10:04] ogra_: I'm fine with that, just needs Stéphane to mangle the tracker [10:04] i reverted all the way back to #119 and it's still broken [10:04] popey, check the urfkill states ... [10:04] I suspect I broke the modem by flipping flight mode on/off too agressively [10:04] (now dont ask me how, the package ships some scripts somewhere) [10:04] k [10:06] bah [10:06] name: Fake Manufacturer Fake Modem Model [10:06] that looks wrong [10:06] just got my flo lightdm die [10:16] boom ... and again [10:17] doesnt look very stable :( [10:17] gar [10:18] anyone know why even a watch-only build (https://ci-train.ubuntu.com/job/landing-011-1-build/121/console) doesn't want to see connectivity-api in that silo? [10:18] the backend seems to have the right contents according to http://people.canonical.com/~platform/citrain/landing-011 [10:21] ogra_: how about the new upstart on flo? =) [10:21] xnox, well, with that crashyness i doubt i can tell much about the quality of upstart ... i can indeed check if it still boots [10:21] (in case thats enough for you) [10:22] ogra_: that would be more than enough. E.g. boots and can open any click based app. [10:22] ok [10:25] rebooting ... [10:25] session starts fine [10:26] running dekko annd g* works fine too [10:26] xnox, looks ok to me [10:26] (G+) [10:27] ogra_: \o/ [10:27] ogra_: do you have a mako as well? [10:27] only a production one atm ... not writable [10:27] probably popey has some time to test ... or om256er (once he is here) [10:29] am debugging my phone issue here at the moment [10:29] still can't get it working [10:30] wow [10:30] i can only run one app at a time it seems [10:30] i dont know what I've done to break it. [10:30] xnox, ^^ [10:30] argh [10:30] popey, try a wipe flash ? [10:31] ☹ [10:31] attempted a no-op reconfigure on 11 to unconfuse it, and now it thinks *none* of those packages are built, and a watch-only build does nothing, even though they're blatantly all in the PPA [10:31] can anyone dig me out of this hole? [10:31] was avoiding wiping [10:31] * ogra_ cant ... i guess you need to wait for eil2100 [10:31] lose all my installed apps and data [10:31] *sil [10:32] popey, anything blocked in /var/lib/urfkill/saved-states ? [10:33] popey: ogra_: well i tested on my mako, but it's in writable & dual-boot install. [10:33] http://paste.ubuntu.com/7802816/ [10:33] xnox, yeah, i dont think it is upstarts fault ... seems the backgrounded apps just die very fast ... [10:33] what does that even mean? ☻ [10:33] o/ [10:33] popey, that you blocked GSM and BT [10:33] I also tried a watch-only build with an explicit package list, but that caused it to try to rebuild everything so I was all NOPE DO NOT WANT NOPE NOPE NOPE [10:34] ogra_: how do I unblock? [10:34] If I wanted to drop an MP from a silo, what is the process? [10:34] popey, looks like a flight-mode flaw ... not sure if oyu can, but i would try to edit the file and reboot [10:34] * popey tries [10:35] cjwatson, might be that the versions need to be bumped to have it pick them up [10:35] uh, read only file [10:35] ogra_: bah, no, badness [10:35] popey, shouldnt [10:35] ogra_: it's been tested, definitely don't want to rebuild [10:35] "/var/lib/urfkill/saved-states" [readonly] 26 lines, 168 characters [10:35] cjwatson, only guessing though [10:35] yeah, thanks but that's not an acceptable solution in my book [10:36] camako: sorry, this is a bit of citrain I'm fuzzy on - I *think* the answer is just reconfigure and build, but would rather wait for somebody more experienced [10:36] popey, [10:36] root@ubuntu-phablet:~# grep urfkill /etc/system-image/writable-paths [10:36] # needed for urfkill persistance [10:36] /var/lib/urfkill auto persistent transition none [10:36] popey, it should be writable ... :/ [10:36] on #119? [10:36] -r--r--r-- 1 root root 168 Jul 16 10:25 saved-states [10:36] root@ubuntu-phablet:~# mount|grep urfkill [10:36] /dev/mmcblk0p30 on /var/lib/urfkill type ext4 (rw,relatime,discard,data=ordered) [10:36] that's probably why then? [10:37] i can touch files in that directory [10:37] root@ubuntu-phablet:~# ls -l /var/lib/urfkill/saved-states [10:37] -r--r--r-- 1 root root 152 Jul 16 12:25 /var/lib/urfkill/saved-states [10:37] hmm [10:37] hmm, i got the same [10:37] can you edit it? [10:37] no [10:37] cjwatson, I guess, equivalent to getting a new silo... not surprisingly... [10:37] let me see if it changes when i switch on flight mode [10:38] camako: well, no, shouldn't need to be that drastic [10:38] popey, toggling flight mode toggles the content (al items have soft=true) [10:38] cjwatson, so basically requires a reconfigure, rebuild, retest [10:39] nt sure how it does that [10:39] camako: I would hope that it does not require rebuilding other packages in the silo, if there's more than one [10:39] Well, unless they build-depend on the changed package [10:40] ogra_: i am on 19 now so i dont have flight mode button ☻ [10:40] *119 [10:40] will upgrade [10:41] /usr/share/urfkill/scripts/flight-mode 1 [10:41] or [10:41] /usr/share/urfkill/scripts/flight-mode 0 [10:41] * cjwatson tries praying re silo 11 (i.e. asking didrocks for help) [10:41] that should toggle it [10:41] and fix the file [10:41] cjwatson, ok that sounds a bit better than a new silo, thanks [10:42] camako: this is silo 18? which MP do you want to drop? [10:43] cjwatson, yes 18... But don't wanna drop at this time... Just in case it came to that, I wanted to know, how much the setback would be.. [10:55] who is working on qtubuntu and can confirm this bug? https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141 [10:55] Ubuntu bug 1329141 in qtubuntu (Ubuntu) "qmlscene crashed while running test_can_launch_multiple_applications" [Undecided,Incomplete] [10:57] popey: hey! How did the back-tracing go with the cellular issue? [10:57] Oh, I don't see Omer around still [10:58] he isnt ... and popey has urfkill issues [11:01] flipping flight mode on and off makes no difference [11:03] Strange, since last urfkill upload was 5 days ago, so it should have been broken for longer [11:04] sil2100, i'm pretty sure it is an issue with upgraded systems only ... [11:04] leaving some devices in a weird state [11:05] popey, "no difference" as in the file contents did not change ? [11:05] yeah, updated the bug [11:05] are you still on 119 ? [11:05] if i enable flight mode the file changes so everything is "true" [11:05] no, moved to 134 [11:06] if i disable flight mode they all go false except WWAN and BLUETOOTH which stay true [11:06] this is weird ... i fear we need cyphermox_ [11:06] ya [11:13] sil2100: Ah, you're around. Can you help me with silo 11? The publish step incorrectly didn't think connectivity-api was built, so after fiddling around a bit I tried a no-op reconfigure, but now it thinks nothing is built, and a watch-only rebuild doesn't find anything [11:13] sil2100: There must be a way to dig out of this without having to unnecessarily rebuild and retest everything? The contents of the silo are good, I just need to convince citrain that they're all there [11:18] cjwatson: maybe you'd need to run the prepare-silo job with reconfigure instead? [11:19] Is that different from running the reconfigure job? [11:19] cjwatson: yes [11:19] OK - how do I run that job? [11:19] reconfigure job is meant for landers, so that the can't do a "full" reconfigure [11:20] cjwatson: https://ci-train.ubuntu.com/job/prepare-silo/ , in build insert the request_id from spreadsheet, series to utopic, and tick RECONFIGURE_SILO [11:20] after that probably the watch_only build will succeed [11:20] cjwatson: one moment [11:21] Ah, right, Mirv might be right [11:21] OK, I'll give that a go ... [11:21] But I'm afraid that the state of the silo might have been swiped [11:21] Let's first try a full reconfigure though [11:21] I guess if all else fails I can copy the packages into -proposed manually [11:22] so in this case it'd be 1404215234499 === MacSlow is now known as MacSlow|lunch [11:22] Trying [11:22] cjwatson: ok, you'll need the same again but with ignore_conflicts [11:23] Yeah, just noticed [11:23] because of dbus-cpp in landing-002. so, reconfigure_silo + ignore_conflicts [11:23] Half-expected [11:24] ok, now a watch only build should probably work. (at least it often does in these problem cases) [11:25] https://ci-train.ubuntu.com/job/landing-011-1-build/125/console doesn't look right, sadly [11:25] but nope it didn't... [11:25] I think I'll just copy manually to -proposed [11:25] Any objections? [11:25] no objections if the packages are right, merge & clean can be run with ignore_step [11:25] Yeah [11:26] Merge and clean won't know which packages to merge, though, will it? [11:26] sil2100: is it possible the so called "lesser" reconfigure actually requires a rebuild after using it? [11:26] ah.. [11:26] I suspect this is just that the project config file is wrong and if we could only write to it directly ... [11:28] om26er, we are looking for someone who can compare ToyKeeper's issues (see the ML) with image 134 and check if 133 behaves properly [11:28] s/compare/confirm/ [11:28] ogra_, ok I'll flash to 133 and will see [11:29] at worst we can to manual sync of the packages from archives and mark the branches as merged [11:29] s/to/do/ [11:29] Will somebody be able to help me with the manual merge if necessary? [11:30] sure, I can or sil2100 can [11:31] cjwatson: yeah, so the state files must have gotten all wrong, we can't really edit them manually though ;/ [11:31] cjwatson: the only way to do that is hacking through jenkins jobs and running commands from there, as we have no access to the citrain machine [11:31] (it's in prodstack) [11:32] cjwatson: let me take a quick look on what happened [11:32] sil2100: I have the copy-package command queued up - let me know when I'm safe to run it [11:32] hmmm [11:35] sil2100, finished testing landing-018 - tested well. Do we have any blockers before Mir 0.5.0 can land? [11:36] camako: I would wait for us to get a promotable image, and there seem to be some regressions that we need to fend off first [11:36] om26er: hi! [11:36] sil2100, ho ho [11:36] om26er: how's the testing proceeding? [11:36] sil2100, I am downloading 133 [11:38] cjwatson: ok, so it seems that something went wrong and the reconfigure wiped the whole silo build state, sadly... [11:39] cjwatson: I just hope that the packages are all up-to-date in the PPA? [11:39] Yeah [11:39] cjwatson: i.e. no missing versions etc.? [11:39] So I'll just copy-package it and we'll merge [11:40] ok [11:40] If that's so then let's do that, it will be a dirty job but yeah, easiest [11:40] We could, of course, just re-build those instead, but then probably some retesting would be needed or such [11:40] I've done worse things to the archive [11:41] hah ;) [11:41] Yeah, I don't want to do unnecessary rebuilding if I can possibly help it [11:41] Ok, need to change locations, will soon be back from a different place [11:41] I'm happy to do the manual syncing plus merges [11:42] I've done the syncing; we'll see if m&c works by itself, otherwise I'll ask [11:42] ok [11:42] I think most of the branches in question are already on ~ps-jenkins//utopic-proposed, but possibly not all [11:44] Everything except connectivity-api is there [11:45] Which is to be expected since that's the one for which the first publish attempt failed === alan_g is now known as alan_g|lunch === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #119 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [12:09] ogra_, which email were you referring to ? [12:10] Landing team 10.07.14 or Landing team 15.07.14 [12:10] the last one she sent ... about the screen not turning on in 134 on incoming calls [12:10] we see that there was a unity-system-compositor change that touched display wakeup stuff ... we want to nail it down to this package but for that we need to know if it works on 133 [12:10] om26er: https://lists.launchpad.net/ubuntu-phone/msg09068.html === psivaa is now known as psivaa-lunch [12:30] cjwatson, hey there :) do we have debug symbols for silos available somewhere? [12:31] tvoss: They should be on ddebs.ubuntu.com [12:33] cprov: do you know why filemanager on s-jenkins is using a screwy version number (other click packages use bzr build in the version number) see http://s-jenkins.ubuntu-ci:8080/job/filemanager-app-click/ versus http://s-jenkins.ubuntu-ci:8080/job/clock-app-click/ ? [12:34] tvoss: (if not there, then nowhere else) [12:36] cjwatson, only archive version symbols available there [12:38] tvoss: -> pitti. this should work, the PPAs seem to be configured properly [12:39] That is, their debug symbols configuration matches that for ~ubuntu-security-proposed/ppa, which should be a good reference here [12:39] cjohnston, hah, apparently just got synced :) [12:39] that will make cjohnston happy :P [12:39] cjwatson, cancel that, queried policy for wrong package :/ [12:40] tvoss: Please can you give me details? [12:41] popey: no, I don't, but I can figure out why === alan_g|lunch is now known as alan_g [12:42] cjwatson, so I've got the packages from silo 18 installed and would need the debug symbols for libmirclient8 [12:43] cjwatson, I followed https://wiki.ubuntu.com/DebuggingProgramCrash [12:43] cjwatson, but apt-cache policy libmirclient8-dbgsym only shows the archive version [12:45] cprov: thank you. I'd like to push a new file manager to the store, but can't with the wonky version number [12:47] * cjwatson checks whether he has his idea of the *_debug_symbols options backwards [12:47] ogra_, it only happens on 134 [12:48] 133 does not have this issue [12:48] cjwatson, ^ [12:48] om26er, could you try to roll back unity-system-compositor to 0.0.4+14.10.20140703.1-0ubuntu1 ? [12:48] and see if that fixes it [12:48] heh [12:48] om26er, could you try to roll back unity-system-compositor to 0.0.4+14.10.20140703.1-0ubuntu1 ? [12:48] and see if that fixes it [12:49] ogra_, ok [12:49] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-003/+build/6153271 [12:49] there is the deb [12:54] ogra_, that helps [12:54] om26er, thanks [12:54] bah, no sil2100 ... [12:55] tvoss: It's in http://ddebs.ubuntu.com/pool/main/m/mir/, it's just not in the indexes [12:56] tvoss: (Because we don't publish indexes for things only in PPAs at the moment, apparently) [12:57] cjwatson, ack, so that would be libmirclient8-dbgsym_1.0+1771-mirdevstaged~1771~ubuntu14.10.1_armhf.ddeb then? [12:57] popey: fginther pointed that the 'version' key was changed in manifest.json from "0.3.@BZR_REVNO@" to "0.3.latest" in revno 224 of filemanager. [12:57] cjwatson, ah no: libmirclient8-dbgsym_0.5.0+14.10.20140715-0ubuntu1_armhf.ddeb seems to be the one [12:57] tvoss: I would have thought that libmirclient8-dbgsym_0.5.0+14.10.20140715-0ubuntu1_armhf.ddeb would be more appropriate [12:57] Yes [12:57] popey: you can take the opportunity and *fix* it too in your new upload. [12:58] tvoss: So you have to do apt by hand, I'm afraid, but looks like all the data is there for you [12:58] cjohnston, yup, got it [12:58] cprov: aha! [12:59] cprov: thanks for looking [12:59] popey, cprov, I have an MP if you need one - https://code.launchpad.net/~fginther/ubuntu-filemanager-app/use-bzr-revno-in-version/+merge/227018 [12:59] check you out! [12:59] popey: fginther is the star on this ;-) [13:00] indeed [13:00] you can go now ㋛ [13:00] * cprov leaves, heads down [13:01] thanks cprov === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #119 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [13:01] no no, too late, I mean it! ;-) [13:04] AlbertA, hey [13:05] ogra_: hi [13:05] AlbertA, seems your last u-s-c upload causes some trouble https://lists.launchpad.net/ubuntu-phone/msg09068.html === greyback is now known as greyback|lunch [13:06] AlbertA, we just confirmed that rolling back to the former u-s-c fixes that behavior [13:07] ogra_: oh, I'll take a look [13:07] thanks :) [13:08] Mirv: OK, the seven packages from silo 11 have all been migrated to the release pocket and are publishing. M&C fails as predicted. Could you please merge by hand? For all but connectivity-api, the ~ps-jenkins/FOO/utopic-proposed branches are up to date and can just be pulled; you might have to be a little more creative for connectivity-api as I'm not sure if the silo branch is available anywhere. [13:08] fginther: will jenkins merge that? [13:09] cjwatson: ok, handling those [13:09] Thanks [13:09] Let me know when that's done and I'll forcibly clean [13:13] popey, lets try it. I top approved it [13:13] thanks [13:23] fginther: looks like it passed, but not merged.. https://code.launchpad.net/~fginther/ubuntu-filemanager-app/use-bzr-revno-in-version/+merge/227018 [13:24] popey, the autolanding tests are still running [13:25] I should get some patience ☻ [13:28] cjwatson: trunks updated, tagged and branches marked as merged [13:28] sil2100, yo [13:28] o/ [13:29] I'm home now, so stable connection all around [13:29] sil2100, so om26er confirmed it is the u-s-c package that breaks incoming calls ... [13:29] ogra_: excellent [13:29] ricmm: ^ [13:29] sil2100, and AlbertA is already looking into it [13:29] Ah [13:29] if we cant get a fix today i would say we roll back [13:29] ogra_: awesome, thanks - I would even consider a roll-back if we won't get a fix in ~1 hour [13:29] to avoid TRAINCON-0 [13:30] Yeah [13:30] well, ask AlbertA if he can fix it in 1h :) [13:30] looking at the 134 smoketests it seems to affect a lot more than just dialer [13:32] Mirv: Great, thanks [13:32] Right, just in case I would try looking at 133 as a promotion candidate, in case something else is broken [13:32] ogra_: sil2100 we are looking into it [13:32] will fix in under 1h [13:32] cool [13:32] ! [13:33] * cjwatson cleans 11 [13:33] #133 looked 'okayish' from the smoketesting side, and if popey identified the problem being urfkill (which seems to be aorund since longer), I would say it should be good as well [13:33] ogra_: give me a team name and I can update the tracker config [13:33]