[02:04] === trainguard: IMAGE 143 building (started: 20140722 02:05) === [02:08] robru: still around? [02:09] rsalveti, sure [02:10] robru: someone from the mir team changed the changelog version for silo 4 with a lower one, but we already had a package built with the previous version in there (5.1 that got changed to 5.0 again) [02:10] robru: not sure if we had a way to make sure the package was completely removed before trying to build the new version [02:11] so I just released the silo and will allocate another one, was that the right thing to do? [02:11] rsalveti, hrm, yeah this is a tricky problem, i've seen this once before, with mir as well actually ;-) [02:11] yeah :-) [02:12] was landing that mr at the same time someone changed it again [02:12] rsalveti, you might need to poke an archive admin to go in a more completely delete the wrong-versioned packages, but starting over in a fresh silo was a good first step. [02:12] but creating this issue [02:12] right [02:12] robru: mind allocating a new silo for 32 then? [02:12] it's currently releasing silo 4 there [02:13] rsalveti, k, it's got silo 12 now [02:14] robru: thanks! [02:14] rsalveti, you're welcome! [02:45] rsalveti: robru so why'd my stuff move ? [02:45] kgunn: because daflu rejected 5.1 [02:45] and moved back to 5.0 [02:46] so we had to clean up and start fresh, because of version changes [02:46] wtf [02:46] kgunn: check the mr [02:47] kgunn, PPAs reject uploads of a lower version once a higher version has been introduced. So 0.5.1 was already in the PPA, you can't upload 0.5.0 there anymore [02:47] rsalveti: its just that i actually could have guessed that was why w/o asking [02:47] he rejects stuff b/c it exists [02:47] right [02:50] rsalveti: per the comment in them mp...the reject/change that was made was optional [02:51] so i'm not really sure i tested nexus10 correctly or not [02:51] it moved right in the middle [02:51] right, but didn't want to decide what to do there, just wanted to land it :-) [02:51] yeah i know [02:51] :-/ [02:51] I tested it already, was already good to be landed [02:52] rsalveti: i tested it on n4 and n10 (i think) [02:52] rsalveti: i was working on testing it on n7 [02:53] I tested the previous one with mako, flo, manta and nexus 5 [02:53] all good [02:53] as only the changelog itself changed, we should be good once the build is done [02:53] rsalveti: yep, n4 and n10 were good for me too [02:53] great [02:54] are you on for much longer ? [02:54] yup, can watch that [03:34] === trainguard: IMAGE 143 DONE (finished: 20140722 03:35) === [03:34] === changelog: http://people.canonical.com/~ogra/touch-image-stats/143.changes === [03:49] rsalveti: beat me to it...i just did sanity boots on all of them [03:49] just in case [03:49] all good [03:49] yeah, same her [03:49] great [03:49] ok bed for me [03:50] rsalveti: do you know anybody around who could review an MR for the ubuntu-seeds? [03:51] bzoltan: which mr? [03:51] rsalveti: This -> https://code.launchpad.net/~bzoltan/ubuntu-seeds/add_telephony/+merge/227665 [03:51] rsalveti: I just added a QML plugin to the SDK [03:52] sure, let me get that to the archive [03:54] rsalveti: Thanks a lot! [04:11] bzoltan: done [04:12] rsalveti: thank you a lot! [06:40] davmor2, ping [06:47] davmor2, when you are available: we rebuilt two packages in silo 8, pay service and media hub. Could you give it another spin with a focus on payments and media playback, respectively? [07:28] sil2100: can I get silos for line 15 and 23? [07:29] thostr_: let me assign those, but later cjwatson will be your train-guide :) [07:29] sil2100: ack. thanks === cjwatson changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #133 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is incoming! Don't release anything that conflicts with it! [07:35] ... except that I'm going to need to reboot my home server soon as it's throwing worrying filesystem errors [07:35] (new disk on order) [07:37] actually, let me do that now. back in a bit [07:47] grrr [07:51] hey, could anyone have a look at bug 1344047 ? it is a very frequent crash. [07:51] this is problem https://errors.ubuntu.com/problem/7fbb29cd16437f0b85c68abcc20d4d0b6cea0c13 [07:52] thostr_: ok, so... [07:52] thostr_: let me just consult this with tvoss [07:53] thostr_: since the silos haven't been assigned because they conflict with silo 008 which is scheduled for landing soon [07:53] tvoss: ping [07:53] sil2100, yup, waiting for davmor2 to do a final round of testing [07:59] thostr_, ping for https://code.launchpad.net/~charlesk/indicator-datetime/make-gcc-version-explicit/+merge/224467 === renato is now known as Guest59288 [08:06] tvoss: what's the ETA for this to be ready to land then? [08:19] sil2100, before lunch hopefully [08:19] davmor2, ping [08:28] Morning all [08:28] tvoss: pong already ;) What payment services do we have in play I didn't know we could currently [08:29] tvoss: oh and by the way, 09:30-10:00 I'm online for a meeting but 11:00-20:00 are my actual hours BST currently [08:30] davmor2, ah okay :) [08:30] davmor2, so I think the most important bit is media [08:30] thostr_, or do we have a test plan for the payments stuff? [08:32] can we buy 7Digital music maybe? [08:32] thostr_, ^ [08:34] tvoss: first draft https://wiki.ubuntu.com/Process/Merges/TestPlan/pay-service [08:34] tvoss: will be more elaborate once we get the missing pieces/implementations in place [08:35] davmor2, ^ [08:35] thanks guys [08:50] cihelp, hey guys, do you know anything about "g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting."? [08:51] looks like the counterpart process crashed [08:51] ;) [08:52] bzoltan: hello! Do you know the status of the 2 MR's for the workarounds of our UITK test problems? [08:53] ogra_, yeah, no related .crash I can find, though, and the phone just went dead (it happens during u8 autopilot, to me on the phone, to jenkins in the VM http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-mako/2477/console) [08:54] Saviq: that is happening during unity8 tests on mako and flo during smoke testing too [08:54] Saviq, i think psivaa saw it too in smoke tests [08:54] psivaa, yup [08:55] feels bad... [08:55] Saviq: unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_expect_sigstop(Native Device) appears to be the offender [08:55] psivaa, hmm interesting, let me try [08:57] psivaa, yeah confirmed [08:57] Saviq: ack. thanks. shall i leave that with you then? [08:58] sil2100: ^ [08:58] psivaa, I won't have the time I'm afraid, going into meetings with design in London onw [08:58] at least not for another 2h or so [09:03] Saviq: ok, i'll report a bug as sil2100 asked for anyone to pick up from [09:19] sil2100, ping [09:19] sil2100: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1346819 is the bug for the unity8 issue above [09:34] tvoss: pong! [09:34] psivaa: thanks! [09:35] cjwatson: ah, just you know - silo 008 is a rather high risk silo, so we would like to have an image build right before landing that silo [09:38] sil2100, I filed bug 1346821, it's probably worth mentioning it on the landing email and adding it to the list of promotion blockers too. [09:46] * sil2100 takes a look [09:46] jibel: oh my! [09:47] sil2100: Sorry I missed the meeting; fsck is still running (!). Anything else other than the image build thing that I should know about? [09:47] davmor2: are you busy? Could you take a look and see if you can reproduce the above bug ^ ? [09:48] sil2100: Just an image build for comparison purposes? Hopefully we don't need a full testing pass on it as well ... [09:48] cjwatson: no worries, in such cases we usually try to get an image built before the landing and right afterwards, only for comparison purposes [09:49] sil2100, did you kick off the image build, yet? [09:49] cjwatson: this way we have more chances to see what broke exactly [09:49] tvoss: no, but I guess it's the rigth time for that - testing almost done? [09:49] Yup [09:50] ogra_, cjwatson, tvoss: ok, I'm kicking a new image now [09:50] sil2100, almost, reconfiguring with a different mp for the scopes api and rebuilding that package [09:51] Let's not land anything right now until this fetches all the packages, and maybe try landing nothing risky besides silo 008 before we kick an image 'after' the landing [09:51] I know it's a bother, but it's the safest way [09:52] I have to say that I think we're overstating the riskiness, but whatever [09:53] cjwatson: could be, but I still remember the chaos caused by a single dbus-cpp rebuild against 4.8 which casued some blocking regressions in the location service [09:54] After which we went back and took all this care :) [09:54] ;) [09:59] === trainguard: IMAGE 144 building (started: 20140722 10:00) === === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #133 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is incoming! Don't release anything that conflicts with it! [10:26] dpm: hello! [10:26] dpm: were you able to get someone working on the AP failures in filemanager and calendar? [10:30] davmor2, unity-scopes-api rebuild done [10:31] tvoss: right updating [10:31] davmor2, thanks [10:35] hi sil2100, I'm in touch with brendand re: file manager, but we haven't found anyone yet. Calendar I was not aware of [10:36] dpm: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1343916 <- it's in the daily e-mail if anything [10:37] dpm, i think i didn't ping you directly about the calendar one yet, but i did ping the channel. no worries anyway [10:51] sil2100, is the pre-silo8 image build done? [10:52] tvoss: it started around an hour ago, so I guess it should have already pulled in all the packages [10:52] sil2100, ack [10:52] fginther, @the mir0.5 CI failures, I looked around and tried to repro locally but couldn't. I don't have even a high level understanding of CI, and not sure what happens before the script gets to the point of failure. Since we see these failures only for 0.5 MPs, there must be a configuration difference between devel and 0.5. But I'm not sure how to check that. Could you help? [10:55] fginther, curiously I see lines like this one : [10:55] http://pastebin.ubuntu.com/7835410/ [10:55] right before the point of failure [11:02] psivaa, did you investigate bug #1346819 at all? [11:02] Saviq: no, sorry I dint. [11:04] psivaa, that's ok, just wanted to know [11:12] sil2100: It'd take a while for things to propagate through -proposed anyway. You can see build progress on https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/utopic/ubuntu-touch [11:12] (Which I could look at except I'm still tethering ...) [11:13] sil2100: Ah, it's done from cdimage's point of view; maybe it's still dealing with system-images [11:14] tvoss: ^- [11:14] cjwatson: right, I'm not sure if tvoss's silo is already finished testing [11:14] tvoss: ? [11:14] cjwatson, thanks for the update [11:14] sil2100, nope, not yet [11:34] === trainguard: IMAGE 144 DONE (finished: 20140722 11:35) === [11:34] === changelog: http://people.canonical.com/~ogra/touch-image-stats/144.changes === [11:47] thostr_, ping [11:58] tvoss: pong [12:02] davmor2, thostr_ just confirmed that you don't need to test pay [12:03] davmor2: it's still disabled by default, so don't worry about it right now [12:03] in that case everything else I needed to test worked as expected [12:03] davmor2: so, land land land.... === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #133 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is incoming! Don't release anything that conflicts with it! [12:09] sil2100, thostr_, tvoss: I'm happy for silo 008 to hit the phone [12:09] davmor2, \o/ [12:14] \o/ [12:15] cjwatson: can you handle it ^ ? [12:20] * tvoss hides away [12:33] Ok, I see cjwatson is busy, let me publish [12:35] I guess we'll need a core dev approving all those [12:35] cjwatson, ogra_: could anyone of you take a look at those many packaging diffs? [12:37] cjwatson, ogra_: http://paste.ubuntu.com/7835889/ [13:11] uh [13:14] Ok, let me approve all the universe ones and then ask Didier for the rest (also the ones with new binary packages) [13:17] sil2100, do you guys need me for silo 8? if not, I would step out to run some errands [13:17] tvoss: I guess we should be fine, the changes look ok packaging-wise but some core-devs and archive admin need to +1 some of them [13:17] sil2100: Sorry, I'd gone out for lunch [13:17] I'm here now [13:18] sil2100: Which ones are left? [13:18] cjwatson: no problem ;) There's just a ton of packaging changes to +1 - most of them seem to be from main, but I'm looking at indicator-location now which is universe [13:18] I'm having some problems with a unit test on jenkins - https://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-utopic-amd64-autolanding/219/console [13:18] OK, I'll just go through the lot, I think I've previously reviewed most of them anyway ... [13:18] I'm getting a failure 0.1.49+14.10.20140715bzr1130pkg0utopic219/modules/Ubuntu/Components/Icon11.qml:35:5: QML Image: Invalid image data: file:///usr/share/icons/suru/actions/scalable/search.svg [13:19] But I took a quick look at most of them and they seem to be safe soname bumps and gcc dep-changes [13:19] when I flash my local phone, that file exists. Could it be that on jenkins it is not there? Is there a way to check? [13:19] cprov: ^ :) [13:20] cjwatson, sil2100, sorrry, busy with developer mode ... i can do left over reviews later today though [13:21] t1mp: let me find someone to help you, one minute [13:21] ogra_: It's OK, I'll deal with them [13:21] cprov: ok, thanks [13:21] thanks [13:21] They're all meant to have an AA check anyway [13:22] Those that have soname bumps at least [13:23] Yeah [13:23] But that's lots === Guest59288 is now known as renatu [13:25] sil2100, kgunn: i'm going to do a settings landing, silo 6 will need a rebuild [13:26] kenvandine: please hold until we have silo 8 done [13:26] silo 8? [13:26] ok [13:26] topic [13:27] why%? [13:27] settings is on the phone, isn't it? [13:27] ok, just preparing a silo [13:27] settings doesn't conflict with 8 [13:27] oh, preparing a silo is fine [13:27] and settings isn't in 8 [13:27] yeah [13:27] seb128: yeah, but we're trying to get an image that just changes that so that people don't misattribute test failures to it [13:27] the topic says "anything that conflicts" [13:28] cjwatson, well, you pointed to the topic, but that's not what the topic says ;-) [13:28] I'm not going to argue about this, it's slowing me down [13:28] ups [13:28] i'll be sure not to publish it until that's cleared [13:28] cjwatson, sorry, closed tab rather than topic details [13:28] seb128, everything conflicts ... simple ;) [13:28] tvoss: Was the removal of -DUNITY_DLL_EXPORTS from unity-scopes-api deliberate? https://code.launchpad.net/~unity-team/unity-scopes-api/require-g++-4.9/+merge/227386 [13:28] that's the only questionable thing I see here [13:29] cjwatson, I *think* so, mhr3^ [13:29] thostr_, ^ [13:29] seb128: shouldn't be long now anyway [13:29] cjwatson, right, as kenvandine said we are just starting to build in a silo [13:29] tvoss, cjwatson, we use symbol map, so it's uncessary [13:29] really mhr3 to answer... [13:29] so time it builds/get tested/etc [13:29] unnecessary* [13:30] mhr3, ack and thx [13:30] cjwatson, seems to be good then [13:30] ok, cool [13:30] core-dev/AA ack, publishing [13:30] \o/ [13:30] cjwatson: thanks! [13:30] cjohnston, thanks :) [13:30] \o/ [13:31] sil2100, running out for an errand now, can you hit merge&clean on silo 8 once things are published? [13:31] tvoss: sure thing :) [13:31] tvoss: I'll deal with it [13:31] cjwatson, thanks === tvoss is now known as tvoss|errands [13:31] it may yet need -proposed handholding [13:32] * tvoss|errands imagines cjwatson herding a bunch of packages through the proposed landscape :) [13:32] feels like that some days [13:32] just send the dog [13:43] t1mp: I am not sure which package provides/installs /usr/share/icons/suru. I suspect it is not available in build time. Did you try to build your package in a PPA as well ? does it work as expected ? [13:45] sil2100: can you please republish silo 16? the MR's are now all approved [13:45] cprov: suru-icon-theme is the package, and it is in depends and build-depends [13:47] bfiller: Let's get an image following the silo 8 landing first [13:47] Hopefully won't be long [13:49] t1mp: okay, are you also using pbuilder locally ? [13:50] t1mp: one alternative is to merge the corresponding trunk and try to build in a LP PPA, so we can compare logs and results. [13:52] cprov: no, I'm building locally using simply qmake && make [13:52] cprov: building of packages always happens automatically for me for the MRs, and I never pushed to a PPA yet (it is all configured to be automatic for the UITK project) [13:53] t1mp: if you have the time to do the experiments above, it will be a proper way to find out what is wrong and where. [13:56] cprov: not really, I am at a sprint this week with a lot of new design stuff to implement so it will have to wait till next week [13:56] renatu: ^actually, was the branch that I made for you built on a PPA? [13:57] psivaa, sil2100, btw, found out the unity8 dbus issue, will have a fix soon [13:57] Saviq: excellent! Thanks :) [13:57] Great news [13:57] t1mp: no worries, if it's not urgent, I can try something later today to help you with debugging. [13:59] cprov: I need it for some changes that we would like to have this week to review with the designers, but it is not the most critical thing right now [14:00] cprov: the branch that I asked renatu about includes the test that fails in my MR, and it is being built on a PPA so I don't know yet if the tests fail there [14:01] Saviq: ack, saw your comment in the bug. thanks :) [14:01] camako, for the mir 0.5 builds, does it need to build against the mir staging PPA? [14:02] fginther, no just from the branch [14:02] camako, ack [14:17] sil2100, ping? [14:17] mhr3: pong? [14:17] sil2100, could i get silo for #15? i know scopes are landing right now, but would really need it, will rebuild once the 4.9 stuff lands [14:18] mhr3: ok, sure, cjwatson is the sheriff right now but I'll assign it to you with override [14:18] sil2100, ah, ok, thx [14:20] sil2100, ogra_: is it wrong to get so excited about the fact that the transfer indicator goes green when you install apps :D [14:21] kgunn: did the manta fix land in a silo in the end? [14:21] i wonder why everything needs to be green nowadays [14:22] ogra_: They listen in to our meeting about everything being green and took it literally? [14:22] well, we should tell the designers they shouldnt take us to serious then :) [14:23] davmor2: yes, rsalveti & i tested and landed that late last night [14:24] kgunn: you guys rock so latest image should have it and I can install it immediately then right? [14:26] davmor2: i'm not sure which image..but yeah, in theory [14:26] :) [14:27] * davmor2 plugs his manta into the pc === alan_g is now known as alan_g|tea [14:39] kgunn: \o/ working manta ! === alan_g|tea is now known as alan_g [15:04] sil2100: I need a silo for line 33 please, it's ok if it conflicts - we will manage it. Mostly for testing during the UI/Design sprint happening now [15:05] bfiller: I'll deal with it (see topic for the main train operator of the day) [15:06] cjwatson: great, thanks [15:06] "CD image ubuntu-touch/ubuntu-rtm/14.09/daily-preinstalled failed to build on 20140722.1" [15:06] tvoss|errands: OK, first problem detected by -proposed: trust-store-tests needs to depend on libtrust-store1 rather than libtrust-store0. Please could you fix that and build in silo 8? [15:06] \o/ [15:06] * ogra_ dances [15:06] ogra_: feel free to ignore for now :) [15:06] the subsequent ones i will ... the first one was exciting to see :) [15:26] * armhf: account-plugin-ubuntuone, indicator-network, libconnectivity-cpp-dev, libconnectivity-cpp0, libtrust-store-dev, libtrust-store0, qtubuntu-media, trust-store-tests, ubuntu-desktop-next, ubuntu-push-autopilot, ubuntu-system-settings, ubuntu-system-settings-online-accounts, ubuntu-system-settings-wizard, ubuntu-touch, unity-scope-click [15:26] that's from [15:26] Trying easy from autohinter: process-cpp/2.0.0+14.10.20140718-0ubuntu1 unity-mir/0.5+14.10.20140718-0ubuntu1 location-service/2.0.0+14.10.20140718.2-0ubuntu1 unity-scopes-api/0.5.2+14.10.20140722-0ubuntu1 dbus-cpp/4.0.0+14.10.20140718-0ubuntu1 net-cpp/1.0.0+14.10.20140718-0ubuntu1 platform-api/2.1.0+14.10.20140721-0ubuntu1 media-hub/1.0.0+14.10.20140722-0ubuntu1 mediascanner2/0.101+14.10.20140721-0ubuntu1 [15:28] indicator-datetime indicator-location indicator-transfer unity-api unity-scope-mediascanner all went in [15:28] hm [15:28] I guess that means that net-cpp pay-service trust-store are blocked at an earlier stage (trust-store explained earlier) [15:29] oh, not net-cpp [15:29] net-cpp finished all the tests so it should be fine [15:29] net-cpp is part of that set, ignore that [15:30] might just need to hint pay-service into the set as well [15:30] I'll do that, but trust-store will need to be fixed [15:30] Yeah, pay-service looks ok in overall, so it shouldn't be blocked - but I see trust-store has some dep problems [15:30] can somebody review it if I whip up a branch? [15:30] and then we can shove it into silo 8 [15:31] Sure, I can try that, not sure if tvoss|errands is around [15:31] I have a call now though, so will be in the background === boiko__ is now known as boiko [15:45] tvoss|errands: so, what's left for silo 008? [15:48] slangasek: cjwatson is resolving the trust-store problem to get it migrated from -proposed [15:53] sil2100: oh, hadn't seen that it was published - yay [15:57] t1mp: hey! [15:57] t1mp: how does the status of the two fixes for our UITK issues going? [15:57] Since I didn't hear back from bzoltan [15:59] kalikiana: hey! I saw that your UITK-AP-fix workaround merge is still not approved - is there any problem? [16:00] sil2100, kalikiana and my fix were merged to staging a bit ago [16:01] cprov: apparently the failures we discussed before passed in the PPA for silo 15 [16:01] balloons: yeah, saw that, thanks :) [16:01] sil2100: the uitk ap test workaround for the timestamps is in our staging now [16:01] sil2100: for the qmlscene crashes I don't know [16:02] kalikiana: ^ what's up with the qmlscene crash fix? [16:02] ah.. it was merged also :) [16:02] sil2100: https://code.launchpad.net/~cjwatson/trust-store/tests-dep/+merge/227776 [16:02] slangasek: ^- [16:02] sil2100: this was just happroved https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/headIconMargins/+merge/227766 so let's see what jenkins does with that :) [16:02] it is not related to the bugs, but we can see if the tests pass now [16:03] cjwatson: approved [16:03] thanks, let me poke a build. trust-store isn't on the phone, so shouldn't require re-testing [16:04] btw, anyone about who can approve something into the store? === gatox is now known as gatox_lunch === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #133 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is incoming! Don't release anything that conflicts with it! [16:13] sil2100: t1mp: kalikiana: sorry, I was busy. What can i do? [16:14] bzoltan: I didn't ping you.. I think. [16:14] not that I remember at least :) [16:16] renatu: are there logs for the unit tests of UITK for silo 15? === tvoss|errands is now known as tvoss [16:17] cjwatson, sil2100 back, how can I help? [16:18] tvoss: too late, am building https://code.launchpad.net/~cjwatson/trust-store/tests-dep/+merge/227776 on top of your stuff already [16:18] t1mp: sil2100 did :) [16:18] cjwatson, thanks for the help :) [16:20] Argh [16:20] sil2100: Shall I just upload this directly? [16:21] cjwatson: yeah... I guess just uploading directly and then merging in manually (+ tagging) is the safest way [16:22] uploaded [16:40] fginther, Hi! [16:42] Can anyone review and deploy a cupstream2distro-config ? https://code.launchpad.net/~om26er/cupstream2distro-config/address_book_service_integration_testing_with_clients/+merge/227787 [16:47] davmor2: just give me a sign if you're able to reproduce the bug [16:47] davmor2: and if you think it's a blocker [16:47] sil2100: album is playing now I'm on track 4 iirc === gatox_lunch is now known as gatox [16:57] sil2100: I have a horrible feel that jibel is play some French music and the phone doesn't like it ;) I'm on track 6 now still playing. That or the phone really loves Adele :) [16:58] Hah ;) [16:58] Then let's not include it as a blocker then, but maybe just mentioning it in the e-mail [16:58] davmor2: could you comment on it? [16:59] sil2100, do you know when will francis come back from holiday ? [16:59] sil2100: I'll keep it playing you can always add it tomorrow jibel doesn't say how far through the album it dies [16:59] davmor2, it died in less than 10minutes [17:02] sil2100: I'll keep looking into it and get back to you tomorrow. I'll see if I can't reproduce it with some different albums [17:03] Ok, thanks! [17:03] jibel: I'm assuming they were albums in mp3 format right? [17:03] jibel: were they fixed bitrate or floating? [17:03] variable even that the word I couldn't think of [17:03] davmor2, same problem with 144, memory usage of media-hub jumped from 0.8% to 29.3% when music-app switched to the next song [17:04] I'll stop here because I'm waiting a call [17:05] jibel: ah right so do you have the phone plugged into the laptop then? if so that could be a difference between us mine was disconnected [17:06] davmor2, yeah, but only to monitor, first time I noticed that it was not plugged === alan_g is now known as alan_g|EOD [17:07] jibel: okay I'll keep having a play, I'm using fixed rate mp3 that were from 7Digital via the UbuntuOne Music store as was. So if yours are variable bit rate that would be the only other difference I can think of [17:10] davmor2, I'm offline for a moment moving a piano, bbl [17:49] slangasek: tvoss: hi, I noticed that this branch is not in silo 8; perhaps it should be? https://code.launchpad.net/~alecu/unity-scope-click/explicit-gcc-version-trunk/+merge/224814 [17:51] well, silo 8 has already published; I don't know how that missed out, but I guess it wants a new silo now if that still needs doing [17:51] alecu: Is it possible to land this separately? [17:51] sure, it can be landed separately if needed [17:51] It would be a lot easier to coordinate [17:52] alecu: You can have a silo for it nowish if you put it on the spreadsheet [17:53] let me just check that it still merges ok [17:53] Hm, what's up with the publisher, it should have ... oh, Mozilla security updates [17:54] * alecu didn't realize that silo 008 had landed... it still shows as "build failed" on my dashboard. [17:54] It's half-landed, I'm working on it [17:54] Having to do the last bit manually [17:54] ah, great. [18:02] jibel: so I see the mediahub and pulse audio both at 20%-ish but that is from song one, I'm keeping my eyes on the cpu percentage on song 2 it hasn't risen, and the memory of both pulse and mediahub have remained roughly the same [18:03] cjwatson: hey are you handling landings? I have about an hour of wifi if you want me to take care of anything [18:05] robru: I'm about to need to finish; still babysitting silo 8 a bit [18:05] cjwatson: ok [18:06] OK, have adjusted the manual proposed-migration hint; it'll require another proposed-migration run though, so that'll be a while longer [18:06] am going to have to go and help with children though [18:07] with any luck that will land, otherwise I'll come back and try again later [18:07] cjwatson: ok cool. think it's safe to land 5 or should I wait on that? [18:07] robru: we didn't want to land much until 8 is properly done and we've built an image [18:07] cjwatson: understood [18:08] robru: 5 isn't on the phone though, so that doesn't interfere [18:08] oh cool [18:08] so yeah, go ahead with that [18:08] k, will do [18:08] * cjwatson -> out for a while [18:10] cjwatson: thanks! [18:10] robru: so, once stuff migrates and silo 008 is merged in, there is one trust-store version that we'll have to merge in manually to the trunk branch [18:11] sil2100: ok. I'm on a ferry right now, wifi will be spotty for me, but I'll try to keep an eye [18:12] A ferry? :O [18:12] sil2100: yep, I live on an island, have to take a boat to get to the airport ;-) [18:13] I hope you have your life-preserver on! Although, according to South park, only vegans wear those... [18:13] ;) [18:13] lol [18:14] bzoltan: heya, I tried to publish silo 5 but I found that one of your MPs is not approved, and another is Superseded (!). Please review those and then we can publish. [18:17] sil2100: hey, what's going on with this failure message in silo 8? i thought it was published? were the packages manually copied? how will i know when the silo has migrated? [18:30] sil2100: so I'm into track 9 2392 phablet 20 0 220412 27636 11352 S 21.9 1.5 15:28.71 media-hub-s+ and pulse is 2258 phablet 9 -11 285564 5728 3560 S 25.8 0.3 16:05.77 pulseaudio and both remain pretty similar [18:42] robru: yeah, so we tried some mojo on that one [18:42] robru: you can try m&c'ing it to see if all is migrated, but since we released a package on top of what's in the silo [18:42] sil2100: hmmmm [18:43] robru: so even if all migrates, I'm not sure if you won't have to force the merge [18:43] sil2100: but do I have to force the merge for every single package? or just trust-store? [18:43] robru: as we released a -0ubuntu2 trust-store to the archive directly, while -0ubuntu1 was in the silo [18:43] sil2100, if we want to get some builds of several branches together for testing that aren't actually ready to land, i can create a silo and just don't check that it's ready right? [18:43] robru: I think what needs to be done: [18:44] robru: force the merge&clean job on the silo once everything migrates, then backport -0ubuntu2 to trust-store trunk [18:44] kenvandine: not checking ready means "don't give me a silo" [18:44] sil2100:ok [18:44] that's what i was wondering :) [18:44] we want an easy way to pull the dual sim work together for testing/debugging, but it's not ready to land [18:45] kenvandine: you need to check it as ready but just not switch to testing: done [18:45] ok [18:45] kenvandine: and best mark in the landing comments that it's for testing only now :) [18:45] pmcgowan, give me the branches [18:46] will do [18:46] thx! [18:46] * sil2100 goes AFK now [18:46] Bye o/ [18:46] good night sil2100 [18:46] kenvandine, https://code.launchpad.net/~jpakkane/ubuntu-system-settings/apneditor/+merge/227534 [18:46] and jgdx branch which is not yet in the list? [18:50] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/1319044-carrier-design-dual-sim [18:50] pmcgowan, ^^ that one? [18:51] kenvandine, yes [18:51] kenvandine, I thought that one was about ready to go [18:51] this morning he said soon [18:53] * kenvandine feels dirty saying it's ready when it's not :) [18:53] i added the comment though [18:54] kenvandine, well, we're not the only ones [18:55] kenvandine, this way I can ask cypher and tony to test as well [18:56] kenvandine: you need the MP URL, and re-assign with ignore set. [18:56] robru, already fixed [18:57] ERROR:root:You asked to reconfigure request id 1406055143385. But we couldn't find it in any existing silo for it. Are you sure you don't want rather to assign a new silo with it? [18:57] robru, ^^ [18:57] i've angered someone ;) [18:57] i guess because it already has a request id? [18:58] kenvandine: oh, yeah. delete the requestid from the spreadsheet row and then run the assignment thing again (you have to close the assignment box and launch it again, because it only generates the id at the beginning. [19:00] robru: kgunn and I are interested in trying again for password locking (line 23) -- is there another silo free? [19:01] mterry: ken just got the last one [19:01] * mterry shakes fist at kenvandine [19:01] hehe [19:02] sorry, we really wanted a way to pull together the dual sim branches for settings [19:02] but since it isn't actually ready to land, we can kill it if needed [19:03] kenvandine, no worries Ken, I'll just scrape together my bits myself [19:03] sigh... [19:03] mterry: bfiller has 5. ask him if he can part with oen [19:03] pmcgowan, conflict [19:03] kenvandine, I mean it, no worries, I don't need the silo this second [19:03] kenvandine, I saw [19:03] mterry, cool [19:03] pmcgowan, it's jdgx's branch [19:03] and i bet he's eod [19:03] indeed [19:04] robru: silo 16 can be republished and freed, the MR's are now approved [19:04] bfiller:thanks [19:04] robru: I'm testing 2 others right now and hope to have them free soon [19:04] silo hog [19:04] can't help it if my team is cranking stuff out :) [19:05] bfiller :-p [19:05] pmcgowan, i think his branch conflicts with the apn branch [19:06] not trunk [19:06] pmcgowan, i'll remove his for now [19:06] kenvandine, that could be for sure [19:08] mterry: wonder, should we pull your stuff into silo6 with qtcomp ? [19:08] i mean just to keep you rolling [19:08] we can kick you out when we try to land [19:08] kgunn, those are so unrelated! :) [19:08] kgunn, I can just build locally [19:08] for testing [19:18] robotfuel: thanks I will sort it out tomorrow morning [19:19] cjwatson, can we merge and clean silo 8? === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [19:36] silo 1 and silo 7 are ready for publishing if anyone can make that happen [19:37] cjwatson: ^^^ [19:37] tvoss: no [19:38] cjwatson, anything I can help with? [19:38] tvoss: still seems to have trouble in -proposed - I'll analyse it shortly but it's my evening [19:38] cjwatson, sure, feel free to ignore me for now :) just thought I'll check in and see if I can help [19:39] bfiller: holding off until silo 8 is *actually* through if possible ... [19:40] tvoss: ah, well, you know how I was making comments about making sure you bumped build-deps on everything relevant? [19:40] tvoss: ... so about that [19:40] cjwatson, where did I forget that? [19:40] tvoss: indicator-network at least (still depends on old dbus-cpp) [19:41] cjwatson, want me to patch that now? [19:41] tvoss: connectivity-api [19:42] tvoss: qtubuntu-media (on media-hub) [19:42] I *think* that's it [19:43] cjwatson, should I add connectivity and qtubuntu-media to the silo? [19:43] oh, they weren't there already, hmm [19:43] cjwatson, nope [19:43] I would say "let's use another silo" but they're all in use right now [19:43] tvoss: so yeah, please add them and build just those two packages [19:43] *three [19:44] cjwatson, ack [19:44] tvoss: away for a bit, if you want to get hold of me then my mobile number's in the directory and feel free to text me [19:45] cjwatson, okay, I guess it can wait until tomorrow. We need another round of testing from davmor anyway [19:45] slangasek, ^ [19:46] can we manage with lighter-weight testing? we have a smaller set of components now [19:46] and I really don't want to keep everything locked for very much longer [19:47] cjwatson, sure, but we at least need indicator-network tested, as well as the media-experience [19:47] sure, but maybe that isn't a full dogfooding pass? [19:47] is anyone else available at this hour? davmor has done a lot for us with this [19:48] anyway, let's please let these built ASAP and then we can see [19:48] really gone [19:50] cjwatson, let me see [19:50] asac, who could help out with testing silo 8? [20:34] slangasek, around? [20:38] Ursinha, hey there, could you reconfigure silo 8 for me, added source packages [20:42] anyone from the ci crowd around? [20:42] tvoss: I believe you need to speak to cjwatson about that.. He seems to be the current train person [20:42] I can recon it, one sec [20:42] I think [20:43] cjwatson, cool, thank you [20:43] cjwatson, got all three missing packages in there now [20:44] well, hopefully it's all three :) [20:45] bah, need to recon harder [20:46] think I've remembered the runes [20:48] cjwatson, triggered rebuild [20:49] tvoss: no stop [20:50] tvoss: I'll tell you whe n [20:51] cjwatson, finished with failure anyway :) [20:52] tvoss: ok, try now [20:54] tvoss: voted approve on the three new MPs though of course they'll need top-approval [20:55] cjwatson, ack and thanks [21:02] cjwatson, there is something weird going on for qtubuntu-media: https://ci-train.ubuntu.com/job/landing-008-1-build/151/console [21:02] cjwatson, I branched trunk [21:03] cjwatson, like minutes ago [21:09] cjwatson, EOD'ing now, build failure in silo 8 persists [21:10] cjwatson, all MPs are top-approved, though [21:12] huh, where's allow-unapproved gone? [21:40] robru: if you have a chance, could you merge https://launchpad.net/ubuntu/+source/qtubuntu-media/0.7.1+14.10.20140604-0ubuntu2 into qtubuntu-media trunk (however's appropriate)? [21:40] that's the source of the current silo 8 failure [21:40] cjwatson, can do [21:40] thanks [21:57] cjwatson, what's the state of silo 8 other than that one trunk sync? is it tested? can i hit publish after the build finishes? [21:57] The three new packages aren't tested [21:57] And tvoss thinks they need it [21:58] (Despite the fact that they passed a full dogfooding with mismatched g++ versions between packages exposing C++11 ABIs, which is supposed to make the world explode, but what do I know) [21:58] cjwatson, what kind of testing is necessary? I've got about half an hour before my flight [21:58] 20:47 cjwatson, sure, but we at least need indicator-network tested, as well as the media-experience [21:58] ah, on device. [21:59] i might be able to test them depending on how long the builds take. [21:59] slangasek: Is it possible to find a QA person who could test out silo 8 for this once this second pass builds? [21:59] well, good question [21:59] cjwatson, slangasek: at this time of day, ToyKeeper is supposed to be our QA contact. [21:59] Or third pass, or nth pass, whatever it is [21:59] ToyKeeper: are you available to help test silo-008 today? [22:00] slangasek: I think so. What's up? [22:01] (usually no direct QA involvement is needed for silos) [22:02] * ToyKeeper starts flashing a fresh image so it'll be ready when the silo is built [22:02] ToyKeeper: see cjwatson's questions above [22:02] ToyKeeper: right, so silo 8 is a big and complex one that apparently people have felt needs specific manual testing - Dave has done a few passes over it. We found that we needed to do (at least) three more builds before it can finish publishing; those builds are in progress at the moment [22:02] indicator-network, connectivity-api, and qtubuntu-media [22:04] I think it would be sufficient for somebody to make sure that networking and media continue to basically work - unfortunately tvoss is finished for the day and because this is such a complex one we'd like to finish landing it as soon as possible so that we can have an image with as close as possible to just that change [22:04] if that makes sense [22:04] Sounds straightforward. [22:04] cjwatson, yeah, there's a growing number of testing:pass silos, I wonder if I should just publish them all, kick an image, and then do silo 8 after that... [22:06] robru: bits of silo 8 have already landed though [22:06] cjwatson, oh right, ok I won't publish then [22:06] because the dependencies weren't checked properly in advance of initial publishing [22:07] so some packages were built, with g++-4.9 apparently, against the old g++-4.8 ABIs, and because the dependencies said this was OK they were allowed into the release pocket [22:07] it's possible that an image built now might be broken [22:07] man, citrain desperately needs some kind of dep check that prevents publishing when a silo contains packages that don't have at least some kind of indirect dependent relationship [22:08] so we really need to fix this [22:08] I think this should actually be fixed in proposed-migration, or at the boundary between the two [22:08] communicate that these packages should be migrated or not as a set [22:08] putting even more weird logic in citrain that people shrug and override is probably not going to help :) === robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #133 promoted | Need CI Train help? Ping: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is half-landed! Don't publish anything else until silo 8 finishes landing and an image is kicked! [22:09] cjwatson, good point, also the more stuff that goes into citrain, the more stuff gets thrown away when ci airline arrives. so proposed-migration probably makes more sense. [22:09] right [22:09] cjwatson, how would it work though? only citrain knows what's together in the same silos. or do you mean like 'stuff copied from the same PPA migrates together' or something? [22:09] (unfortunately it's not exactly trivial to do in p-m, but maybe when I get a while ...) [22:10] robru: well, they get copied as a batch [22:10] ah [22:10] by way of communication to a script that conveniently lives on the same user account as p-m [22:11] In any case, let me know when builds are ready. [22:11] ToyKeeper: thanks. I think they're not too far off [22:11] hope I didn't miss anything in my analysis earlier [22:11] ToyKeeper, I'm signing off soon to board a 9 hour flight, but if you set an IRC highlight for landing-008, then queuebot will ping you when it's ready [22:11] I can be around for a while longer [22:12] if slangasek doesn't mind not seeing me too early tomorrow morning oh wait [22:12] ToyKeeper, or watch this page: https://ci-train.ubuntu.com/job/landing-008-1-build/152/console [22:12] * cjwatson likes having a manager eight hours thataway [22:12] cjwatson: who else will keep me company at 11pm!? oh right pitti === renato is now known as Guest49276 [22:34] noooooooo [22:35] oh, did somebody retry that build? the ppa says still building... [22:36] leave it to me [22:36] it's the usual connectivity-api flakiness [22:36] I did indeed retry [22:37] cjwatson, ok, I just ran a WATCH_ONLY so we can get more bot pings when it finishes [22:37] ok [22:37] I'm boaring in a few minutes here... [22:38] though I was going to do that once it actually built to reduce noise :) [22:38] have a good flight [22:39] looks better now anyway [22:40] cjwatson, thanks, alright we're boarding ;-) [22:53] ToyKeeper: should be available in the silo now [22:53] cjwatson: Awesome. No notice from queuebot though? [22:53] * ToyKeeper speaks too soon [23:16] publishing silo 14 since that's morally part of all this [23:19] I wonder why 16 isn't shown as empty now [23:26] ToyKeeper: not to pressure you but any rough eta? just want to see whether I should make a giant pot of coffee, go for a walk, or what [23:27] When is making a giant pot of coffee ever not a good idea? [23:31] theoretically I probably want to sleep at some point, but I subscribe to the general tenor of your comment [23:31] heh [23:32] theoretical sleep is the best kind [23:39] cjwatson: Sorry, had a bit of an interruption... Testing in progress, though. [23:45] ToyKeeper: ok, thanks [23:46] ToyKeeper: (was that queuebot notification you? I guess not, probably a hangover from last run) [23:47] Nope, that notice wasn't from me. [23:48] o/ [23:49] Chipaca: assigned. you might want to think about notifying upgraders to clean up the stale files, later [23:49] s/files/symlinks/ [23:50] cjwatson: you mean the ones left behind by the old hook? [23:50] yeah [23:50] yes. Maybe? if this had been used by anything yet, yes. [23:51] mkay [23:51] ah, you mean, actually tell people [23:51] yeah, will be doing that ;) [23:58] flipped 8 back to testing: no to avoid confusion