[02:04] === trainguard: IMAGE 148 building (started: 20140724 02:05) === [02:11] robru: around? [02:11] bfiller, indeedily-doodily [02:11] robru: :) I need a silo for line 32 please [02:12] bfiller, ahhhh you had asked about that one earlier but I was confused because it said 'boiko' in the lander. sorry [02:12] robru: May I ask for a silo assigned to the line31? [02:12] robru: no worries, need one for the other one as well [02:13] bfiller, ok you got 4 [02:13] robru: is there a specific reason for not processing the lines in sequenc? Just curiosity [02:13] robru: cheers [02:13] bzoltan1: you up early or still haven't gone to bed? [02:13] bzoltan1, yeah, it has to do with timezones. when I'm in US hours and I see a bunch of requests from EU people I don't like to assign them out of fear that they'll just sit there empty for 12 hours while other requests wait. if you're really around and really want one, feel free to ping me [02:14] bfiller: a bit both... I got 4 h sleep :) [02:14] bzoltan1: kids? [02:14] bfiller: yeps :) they are the sunshine of my life... for real [02:14] bzoltan1, hm, conflict with silo 15. any chance to merge those into one, or should I override? [02:15] bfiller: they should be the moonlight occasionally [02:15] anyone have any idea why, when cross compiling with sbuild, the tests binary target would get built, and then 'make check' would fail not being able to find the program? [02:15] robru: silo 15 just for testing really so think it's ok to override [02:15] bfiller, ok thx [02:16] bzoltan1, ok you got 8 [02:16] robru: wow... that is a weird one 1) why renato is landing UITK change without me 2) why the MR is targeting the trunk and not the staging [02:17] bzoltan1, oh that is weird, renato proposed somebody else's branch, and now it's in bfiller's silo... [02:18] robru: let's not land a 4108 lines MR that way... [02:18] bzoltan1, robru : renato and timp are at sprint, they wanted a silo to test chagnes together [02:18] that's what silo 15 is [02:18] bfiller, ahhh ok [02:19] bzoltan1, 4k lines sounds like merge targeted to wrong branch ;-) either that or they are sprinting *hard*! [02:20] bzoltan1: you might want to touch base with timp.. I think they are just experimenting to show the designers. not intending to land that silo [02:20] robru: noone should sprint that hard... timp knows that I am working on a landing [02:20] bfiller: Ohh, that would explain [02:21] robru: bfiller: we should have a flag for "not intended to land, just for building and testing" for silos like that [02:22] I'm out, see you guys :) [02:22] bzoltan1, yeah, or maybe even a whole other set of silos for things that won't land. seems ci train is more popular for testing than originally anticipated ;-) [02:22] bfiller, goodnight! [02:24] robru: people do not know that they can make and set up PPAs just as before the CI Train... I have like 4 PPAs in the SDK ... this UITK landing I was testing alredy yesterday [02:24] bzoltan1, yeah, maybe we need to just educate people on PPAs. citrain is just a small harness around PPAs that automates copying PPA packages to distro. no real need for ci train unless you're planning to actually release something. [02:25] robru: +1 that [02:30] robru: PPAs are complicated if you need the full range of builders [02:30] with real hw [02:30] sergiusens, so maybe we should make a couple non-citrain devirtualized PPAs that use the real hw but don't tie up citrain for weeks on end? [02:31] robru: it's probably the same thing if you get to manage them [02:42] robru: what's next with that package? [02:42] sergiusens, it'll need an archive admin to ack it through the NEW queue [02:43] ack [02:43] sergiusens, they'll see it eventually, or you can ping them if you're in a hurry [02:44] robru: just want to continue merging, but it's manageable [02:45] sergiusens, yeah you can't free the silo while it's in the NEW queue, because the NEW queue doesn't actually "contain" the package (eg the NEW queue is just a pointer to the silo). so if you merge&clean now, you'll lose the package. [02:45] robru: no worries, it's an empty commit :) [02:45] no hurries even [02:45] yeah [03:39] === trainguard: IMAGE 148 DONE (finished: 20140724 03:40) === [03:39] === changelog: http://people.canonical.com/~ogra/touch-image-stats/148.changes === === mvo_ changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: mvo_, trainguards | CI Train Status: #133 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [07:36] sil2100, ping [07:39] tvoss: poong [07:40] sil2100, so silo 8 is in, any issues? [07:41] tvoss: so far from what I can see it seems to be alright :) [07:43] sil2100, wow [07:44] tvoss, from a dashboard pov it looks pretty fine [07:44] brendand, thanks [07:45] too early to celebrate,but I could use a beer now [07:45] another day, another mir fix... [08:22] bzoltan1: how's testing the UITK going? [08:24] sil2100: it looks good ... in few hours I will be ready and I can tell if we can go with the staging or I fall back to the cherry picking. The UITK tests are all green, unity8 too, all the key apps are fine so far. I had problems with the crashing OSK and the music app has weird emulator what has a fix proposed. [08:24] anyone else stuck with no bluetooth? [08:25] bzoltan1: sounds promising so far [08:27] sil2100: do you know what the silo5 is blocked by? [08:28] qtcreator-plugin-ubuntu/arm64 unsatisfiable Depends: webapp-container [08:28] qtcreator-plugin-ubuntu/powerpc unsatisfiable Depends: webapp-container [08:28] qtcreator-plugin-ubuntu/ppc64el unsatisfiable Depends: webapp-container [08:28] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtcreator-plugin-ubuntu [08:30] Ah! [08:30] So that'll be from https://code.launchpad.net/~zeller-benjamin/qtcreator-plugin-ubuntu/runhtml/+merge/226821 [08:30] Can that dependency be made [i386 amd64 armhf] just like the one immediately below it? [08:31] Yeah, sorry about that, could have double checked... I guess we need to make the dep arch-dependent [08:31] bzoltan1: ^ do you know if that change in that merge will not cause any issues if webapp-container is not installed? [08:32] If it's possible to adjust that dependency, it'd be simplest for zbenjamin to tweak his branch and then rebuild [08:34] sil2100, ping? [08:34] cjwatson: sil2100: zbenjamin is out of business today [08:34] mhr3: pong? [08:34] sil2100, could you give pete-woods lander permission for ci sheet? [08:35] ... or to recon with an extra branch on top [08:35] sil2100, he'll be taking it over from me [08:35] cjwatson: sil2100: I can not fix it without conflict. Would it be acceptable to land it and push a fix straight after? [08:35] mhr3: sure, after the meeting I'll do it [08:35] no [08:35] extra uninstallable packages can make proposed-migration take globally worse decisions [08:35] sil2100, thx [08:36] I do force things sometimes for compelling reasons, but not just because of scheduling [08:36] bzoltan1: you can absolutely fix it using an extra branch starting from Benjamin's that declares his as a prerequisite branch [08:36] add that to the list of merges, reconfigure, build [08:37] what I can't see from the context of the diff is what the code will do if webapp-container is absent [08:37] cjwatson: Wow, I did not know about that path... cool, thanks. I will do it [08:37] which I guess is relevant information when considering making a dependency arch-dependent [08:38] bzoltan1: I'm pretty sure that path works anyway - happy to assist [08:42] cjwatson: like this? https://code.launchpad.net/~bzoltan/qtcreator-plugin-ubuntu/arch-dependent_dependency/+merge/228058 [08:43] bzoltan1: I believe so; LGTM [08:44] You should be able to add that to the spreadsheet and self-reconfigure, as the lander [08:56] sil2100: I need this MR to land before the UITK lands -> https://code.launchpad.net/~canonical-platform-qa/music-app/fix1348055-do_not_depend_on_position/+merge/228051 [08:57] oh [08:57] hm, music-app is a click right? dpm ^ [08:57] hi sil2100, yes, all core apps are [09:02] sil2100, I'm not familiar enough with the change, and balloons and popey do the click uploads. So until Leo and balloons are up, there is not much we can do. Why is the app a blocker for the SDK? [09:06] dpm: it probably causes a test failure when the new UITK is used [09:07] brendand: could you take a look at this change and do a review? [09:07] brendand: ^ [09:07] We would then be ready for release when balloons appears [09:11] sil2100, looks fine to me [09:18] brendand: if you approve it, do you know if it would be auto-merged? [09:29] sil2100, brendand, I can top-approve if QA thinks is good to go, and then it will be auto-merged [09:29] dpm, yeah [09:34] brendand, sil2100, top-approved as per the discussion. This should now auto-land in music-app - could someone take care of generating a click package when that happens? The way it works generally is that popey requests the click creation from Jenkins (I'm not sure if he triggers it himself or someone else needs to do it) [09:36] dpm, i don't know who can do that - apart from people who are on holiday (popey, Mirv) [09:36] Doesn't it get spat out automatically as an artifact?? [09:36] er with just one ? [09:36] let me check the zip files [09:37] from previous MPs [09:37] dpm, i guess we want the click package built from trunk though, not from the MP [09:38] brendand, that's what I meant. This needs to land first before requesting the click [09:38] in any case, I think at least fginther should know how to generate the click from Jenkins [09:40] dpm, run this : http://s-jenkins.ubuntu-ci:8080/job/music-app-click/ [09:40] brendand, I don't have access to that (and I'm not sure I'd want it ;) [09:40] dpm, i do [09:41] dpm, so i guess anyone with ci-lab access can do it [09:41] excellent [09:41] can I get a silo for ci sheet line 19? [09:41] sil2100: I'm off to lunch, if you could guard the train for a bit that would be great. but just one silo currently, so not too much we can do [09:41] sil2100, we should have a list/channel/lp team for everyone with ci-lab access [09:41] mvo_: silo 12 can be published... [09:42] sil2100, that way we should never be stuck for someone to prod things along [09:42] sil2100, and also store uploaders [09:42] brendand: yeah... it was alwas a bit vague for me who has powers to do what [09:43] mvo_: ok! Sure thing, I'm playing around with CI Train now anyway [09:43] sil2100: cool [09:44] thostr_: thanks, doing that now [09:45] mvo_: can I get a silo for line 19? should be a quick one [09:45] thostr_: sure [09:45] thostr_: just assigned it to you [09:45] mvo_: thanks [09:45] * mvo_ is really off now === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): psivaa | CI Train support: mvo_, trainguards | CI Train Status: #133 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [10:57] renatu: oSoMoN: Both of your MRs are added now to the Silo8. I reconfigure and rebuild. [10:58] sil2100: I need to land two additional MRs for the browser and the messaging apps alongside with the UITK in order to keep the autopilot tests happy. [10:59] sil2100: would you please reconfigure the silo8? [10:59] bzoltan1: oh, ok, messaging-app had one failure in AP tests already - is there a new failure? [10:59] bzoltan1: sure [11:00] sil2100: renatu ^^ [11:06] sil2100, this should fix the messagin-app failure: https://code.launchpad.net/~renatofilho/messaging-app/fix-autopilot/+merge/228071 [11:07] brendand: is that also the fix for our earlier issue ^ ? [11:08] renatu, boiko already pushed a branch that i think does it in a better way [11:08] renatu, actually it was tiago - https://code.launchpad.net/~tiagosh/messaging-app/fix-broken-test [11:09] renatu, it's currently trying to get past CI, but there is some failures which aren't predictable [11:10] brendand, sil2100 , yes the tiago branch is better [11:11] sil2100: what's wrong here: https://ci-train.ubuntu.com/job/landing-016-0-reconfigure/20/console [11:12] thostr_: there seems to be a problem with the MR here: https://code.launchpad.net/~alfonsosanchezbeato/mediascanner2/krillin-apparmor/+merge/227302 [11:12] (invalid link) [11:12] sil2100: right... [11:13] Once this is fixed, it should reconfigure fine [11:50] sil2100: the UITK tests look good. All issues were trivial to resolve. The autopilot tests of the messaging and browser apps will get little facelift. I am now testing elopio's fix for the music app. That is the last one. All other tests passed. [11:52] o/ [11:52] bzoltan1: so far things sound nice, just give us a sign once all of those are ready [11:52] Saviq: hi! How's the testing for unity8 going? :) [11:54] sil2100: btw I think the silo5 is good to go now [11:56] sil2100, ping [11:56] do we see any regressions due to the gcc transition? [12:00] sil2100, one test failed, need to fix [12:00] sil2100, lunch now and will do straight after === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: mvo_, trainguards | CI Train Status: #133 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. === alan_g is now known as alan_g|lunch [12:29] tvoss: test wise we are very good, I asked davmor2 to take a dogfooding look at the latest images and so far he has not reported anything :D [12:44] davmor2: any big blockers noticible in the latest image? [12:44] sil2100: still looking had some iso testing to do too [12:45] sil2100: there is the annoying power menu you get when hitting the power button to wake the device [12:46] sil2100: I think there is already a bug for that though [12:49] davmor2: yeah, I got that once today at least [13:01] sil2100: hiya, i need an admin reconfig for silo13 please [13:01] dbarth: hey! mvo_ is the sheriff, mvo_ could you do it? ^ :) [13:01] oh sure [13:01] sure [13:01] on it [13:01] thx [13:02] Thanks! [13:03] sil2100: hm, it tells me "ERROR:root:signon-ui was not in the initial list of components for that silo. You can't reconfigure the silo yourself. Please ask the landing team to reconfigure it for you." - do I not have all privs I should have? [13:04] mvo_: how did you reconfigure it? Did you use the reconfigure job? Since for this case you need to use the main spreadsheet [13:04] mvo_: i.e. find the landing, click on the row and do 'assign silo' again to get the 'Reconfigure' dialog appearing [13:05] mvo_, I would like to rebuild 18, to pick up branch changes how to do? [13:05] sil2100: aha, thank [13:06] sil2100: for a simple rebuild clicking on "build" is enough (?) [13:06] mvo_, unless it was already rebuilt earlier today [13:06] sil2100: (context is the question of pmcgowan) [13:07] pmcgowan, mvo_: in this case I think clicking 'build' and writing the projects that need to be rebuilt is required [13:07] so I can do that myself maybe [13:07] Yes :) [13:07] dbarth: silo is reconfigured [13:07] pmcgowan: I can give you a hand as well, thats my job (currently :) [13:08] trying it one sec [13:08] seems I failed [13:09] pmcgowan: let me check === alan_g|lunch is now known as alan_g [13:09] mvo_, just got the cant build message [13:09] mvo_, must need to force [13:10] pmcgowan: yep, let me see if I can convince it :) [13:10] * mvo_ triest the small hammer first and then the big one [13:10] better [13:10] thanks mvo_ [13:11] yw! [13:11] trainguards: hi, can I ask for silo for row 35? [13:11] kenvandine, morning, I'd like to get jonas dual sim branch approved and silod [13:12] pmcgowan, indeed, did he say it's ready? [13:12] alecu: sure, sorry that I didn't assigned it earlier we were a bit low on silos this morning [13:12] he did in email [13:12] mvo_: no problem, and thanks! [13:13] pmcgowan, cool, reviewing [13:14] kenvandine, we just restarted silo 18 with jussis fixes [13:14] pmcgowan, cool, i want to get call_forwarding in a landing silo today too [13:14] kenvandine, indeed, maybe with jonas branch [13:17] mvo_: can I get a silo for line 37 in the spreadsheet? [13:18] sure [13:19] thanks [13:26] sil2100: Here is the situation... The UITK is compliant with the regular full testsuite with a single exception. The music app has still very wrong autopilot tests. It was duplicating an old version of the UITK emulator and it is prone to failure at any given point. elopio managed to solve 2 of the 5 failing music app tests, but we still have 3 failures. It has nothing to do with the UITK, as it is clearly a problem caused by poorly [13:26] thostr_: sil2100: are we landing silo 16? [13:26] I want to land it but I see from the spreadsheet that you're both looking at that line :-) [13:27] rsalveti: I just put testing to green... so from my pov we can land... just waiting for somebody from ci [13:27] ok, let me land it [13:27] bzoltan1: I think your message has been cut at the end === pete-woods is now known as pete-woods|lunch [13:28] bzoltan1: anyway, hm, we didn't see any music-app test failures recently, why are those suddenly happening with the new UITK then? [13:29] sil2100: http://pastebin.ubuntu.com/7847642/ [13:30] mvo_, Can we get a silo for lines 22 and 27 now the gcc 4.9 stuff is landed? [13:30] (preference in that order) [13:30] bzoltan1: thanks, ok - still the question arises, why didn't this poor test suite fail with the old UITK? Since as I mentioned, we had 0 failures for months now in music-app [13:32] bzoltan1: hi, I can't land the qtcreator change right now, its changing a existing debian/changelog, could you please have a look? https://ci-train.ubuntu.com/job/landing-005-2-publish/71/artifact/packaging_changes_qtcreator-plugin-ubuntu_3.1.1+14.10.20140724-0ubuntu1.diff - i.e. the change is in a changelog entry for a already released package [13:32] mvo_: I will do.. a bit later. I am busy with the UITK [13:32] ok [13:33] mvo_: hmm... I think it might be even ok in this case [13:33] sil2100: for UITK, we have these custom proxy objects (formerly known as emulators) in the AP tests that app autopilot tests can use [13:33] tedg: which one is more important, I have only a single silo left right now [13:33] mvo_, 22 please [13:33] mvo_: since qtcreator-plugin-ubuntu is, IIRC, currently blocker in -proposed because of this reason - so you can actually publish this and 'overwrite' the version in -proposed [13:33] sil2100: because some times in an internal component we add just a property, and then the type of the component changes for autopilot. In our CPOs, we can update the tests to use the new type [13:33] sil2100: the music-app didn't use the emulators [13:34] sil2100, tvoss: I don't see anything that isn't already reported so far [13:34] sil2100: music-app had this code in it: [13:34] def get_back_button(self): [13:34] 117 return self.select_single("AbstractButton", objectName="backButton") [13:34] in the test [13:34] t1mp, sil2100 the music app has had a pending rewrite of tests on the agenda for a little bit now [13:34] we added a property to the back button and now it is not of type AbstractButton anymore. [13:35] I have a fix for music-app AP here: [13:35] Oh, ok [13:35] http://bazaar.launchpad.net/~tpeeters/music-app/fix-go-back/revision/538 [13:35] there's definitely some custom code that can be removed [13:35] I'll remove the commented-out stuff before merging it (after we test the fix) [13:35] sil2100: ok [13:35] tedg: then you can have 27 as well :) [13:35] I'm at a sprint now and my device is in use for testing something else right now [13:35] \o/ /me is rolling in the silos! [13:37] t1mp, balloons, bzoltan1, elopio: ok, so could you guys just make sure all the required fixes/rewrites for music-app are at least merged into trunk before proceeding with the release of UITK? [13:37] But I guess I wouldn't count it as a reason to drop staging and doing cherry-picking, especially that it's being actively worked on right now [13:42] sil2100: I am testing the changes from t1mp right now. I expect it to give OK results. [13:47] balloons: are you working on music-app? Or is there someone else to review our changes when we propose the MR? [13:48] t1mp, I can help review. I've not been working on it, I guess that's been all elopio, but he didn't mention it to me ;-) [13:48] did we talk to andrew or victor the core app devs? [13:49] balloons: no, I didn't talk to them about this, they appear to be offline [13:49] sil2100, are free silos thick on the ground today by any chance? [13:51] mterry: what do you mean? ;) [13:52] sil2100, are any free to be assigned for line 20 (locking support) [13:53] mterry: let me poke mvo_ about it, but the strange thing is... I vaguely remember assigning a silo for this line TWICE yesterday, and today I saw it was still without any silo [13:53] I'm either hallucinating, or something strange is going on [13:53] you used the wrong spreadsheet :P [13:53] sil2100, the merges that will not be CONTAINED! [13:54] ;p [13:59] davmor2, \o/ [14:00] mterry: no silos right now sorry [14:00] * mterry cries into his cups [14:01] mvo_, OK! no worries [14:01] mvo_, just tell tvoss to stop using silos for test builds :P [14:01] ogra_, no silos for me :) [14:02] anyone have some deep knowledge of cross compiling with sbuild? xnox ? i'm having a reallly weird issue with compiling something, and could use some more experienced eyes looking at it to see if i'm doing something especially stupid [14:02] hello hello [14:03] dobey: what issue do you see, could you pastebin the error ? [14:04] mvo_: http://pastebin.ubuntu.com/7843862/ [14:04] mvo_: basically the test binary is being built during build, but then not being found during the make check [14:04] mvo_: lp:~dobey/ubuntuone-credentials/cross-compilable is the branch where i'm getting this, if you want to try it [14:05] dobey: compiled unit tests can't be executed... you can build them, but not run. [14:05] xnox: ugh :( [14:06] dobey: well, because Intel cpu's don't execute ARM code =) hence crosscompilation =) [14:06] dobey: it's not like you are building i386 on an amd64 machine =)))) [14:06] You should generally configure a cross-build environment not to run tests. [14:06] DEB_BUILD_OPTIONS=nocheck [14:07] xnox: but that's weird, it works fine with other packages [14:07] The reason you get "not found" or similar is that execve returns ENOENT when the program's ELF interpreter doesn't exist. [14:07] dobey: from bulk cross-building experience I can definitely say that running tests doesn't work fine with most other packages :) [14:08] dobey: but perhaps this package fails to honour DEB_BUILD_OPTIONS=nocheck? [14:08] cjwatson: oh, i guess because of overriding dh_auto_test? [14:09] dobey: ah yes, buggy debian/rules [14:09] dobey: one can override dh_auto_test, in a way that still honors DEB_BUILD_OPTIONS and crosscompilation et.al. [14:09] dobey: you should wrap the override in ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) / endif [14:09] dobey: why did you override dh_auto_test at all? [14:10] i might just be able to kill the override now anyway [14:10] dobey: check is one of the default test targets as is.... [14:10] Also, personally I'd do that arch check using ifneq (,$(filter armel armhf,$(DEB_HOST_ARCH))) rather than in shell [14:10] If it needs to be done at all [14:10] xnox: because we were building in a PPA that used qemu for arm at one point, and one of the test suites was crashing in qemu [14:11] but we're not building in that PPA any more i think [14:12] and since all the CI train stuff is on real arm hardware iirc, we shouldn't need to do that [14:13] thanks === pete-woods|lunch is now known as pete-woods === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): Ursinha | CI Train support: mvo_, trainguards | CI Train Status: #133 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [14:15] sil2100: I have flipped the tested switch on the Silo8. This MR need to land on the music_app -> https://code.launchpad.net/~tpeeters/music-app/fix-go-back/+merge/228120 [14:21] bzoltan1: thanks! Does this merge fix all the music-app issues? [14:21] sil2100: yes [14:21] Awesome! [14:22] sil2100: say it only when the first CI smoketest shows better results then now :) [14:22] ;) === alan_g is now known as alan_g|tea [14:22] mvo_: ok, so please land UITK once you have a moment! [14:23] sure [14:24] sil2100: aha, I tried to land that some minutes ago alredy, it errors with https://ci-train.ubuntu.com/job/landing-008-2-publish/55/console [14:26] bzoltan1: hmmm... [14:26] bzoltan1: it seems the branch https://code.launchpad.net/~renatofilho/messaging-app/fix-autopilot does not exist anymore? [14:26] bzoltan1: while the silo is configured to use it [14:26] bzoltan1: what happened? [14:26] We might need to rebuild messaging-app there then [14:27] sil2100: what the hack? [14:27] Strangeness! [14:27] renatu: ? [14:27] sil2100, hi [14:28] sil2100, I removed it, you should use tiago's branch [14:28] Ah... [14:28] sil2100, https://code.launchpad.net/~tiagosh/messaging-app/fix-broken-test [14:28] bzoltan1: ok, so we need to rebuild the silo with the new branch ;/ [14:28] bzoltan1: and re-test messaging-app [14:28] sil2100: OMG [14:28] Damn, this is confusing [14:29] sil2100: renatu should not have touched the MR in the middle of action [14:29] sil2100: I have tested renato's MR not tiaosh's [14:30] bzoltan1: yeah... thankfully it's just one component that will require a retest, but still... rebuilding the package + testing still takes some time :| [14:30] bzoltan1, sil2100, sorry brendand point us the branch early here in the channel [14:30] sil2100: would you please reconfigure the silo8? [14:31] renatu: still... please do not do it too often. It wasted like 2-3 hours now. [14:31] bzoltan1: sure, although a normal reconfigure should be sufficient, but best being safe than sorry [14:32] bzoltan1: ok, I'll modify the MP list to the new MP as well [14:32] sil2100: that part I have done [14:32] sil2100: so you take care of it? [14:33] bzoltan1: oh, hmm... my spreadsheet seems to still show renatu's branch [14:35] bzoltan1: I still see renatu's branch, so I'll change it to tiago's one === alan_g|tea is now known as alan_g [14:36] * sil2100 just hopes the spreadsheet doesn't go crazy [14:37] bzoltan1: reconfigured! [14:37] bzoltan1: you can rebuild :) [14:38] (messaging-app that is) [14:38] thanks sil2100 [14:44] plars: How did the dry-run-RTM system-image test go? [14:45] cjwatson: I can run tests with it locally, and I have some proposed changes to the ci scripts to integrate it that I'm trying to run through staging. There are some dashboard changes that will be needed that josepht is looking at right now [14:45] cjwatson: as I understand it, the real one will come next week or so, and we'll be calling it it stable-proposed right? [14:46] cjwatson: the current plan is to move utopic testing on our side with the variant name "touch" to a variant called "touch_devel" and then create one called "touch_stable" that aligns with the results from testing stable-proposed [14:47] plars: Probably about two weeks from now. Name still slightly TBD but presumably it's not hard to change on your side [14:47] (waiting for Stéphane to come back so we can finish that debate) [14:47] cjwatson: no, we can change the name to whatever on our side. In the meantime, we'd like results on staging-stable-proposed correct? [14:47] plars: stable-staging-proposed, but yes [14:48] plars: Just to make sure that the process works rather than because of any special interest in the results, of course [14:48] right [14:48] plars: Although it was branched from the last promoted image so hopefully should be pretty solid [14:49] cjwatson: from the looks of running it locally, it does pull from an rtm derived archive rather than the usual places though [14:49] so it's good to test [14:49] plars: Right, great [14:50] Yeah, its sources.list and such should be all derived-archive.whateveritis [14:56] bzoltan1, brendand__: can anyone top-approve tiagosh's MR? [14:57] mvo_, I removed an MR from my silo, which effectively removes the package. Do I need a reconfigure in that case? Or can I just continue and assume it won't get merged. [14:57] sil2100, renatu ? [14:57] tedg: not sure, sil2100 may know but if in doubt, go with the reconfigure [14:58] tedg, mvo_: it will require a reconfigure [14:58] sil2100, Ah, okay. Thanks. [14:58] mvo_, Can you please reconfigure silo 17? [14:59] sure [15:00] tedg: done [15:00] mvo_, Thanks! [15:28] bzoltan1: argh, why did UITK got rebuilt in the silo as well? I thought only messaging-app was supposed to be rebuilt [15:28] bzoltan1: it's now waiting for it to finish building for no reason [15:29] sil2100: sorry, I did not know if it was possible to rebuild only one source pakage there [15:29] sil2100, did you remember to give priviledges to pete? [15:30] bzoltan1: ah, yes ;) When for instance only a merge for one project changed, you can press 'Build' and list that one project name in the list of packages to rebuild, and it will fetch the changes and build from scratch [15:30] sil2100: arghhh... I am an ignorant ass [15:30] bzoltan1: force rebuilds are only necessary when nothing changed in any merge and you still want to rebuild :) [15:31] * bzoltan1 is learning every day something new [15:31] No worries! It's just sad that we have to wait unneccessarily, while being very hyped on getting it released! [15:31] mhr3: yeah, now I did! (I'm such a lier, thanks for reminding me) [15:32] sil2100, cool, now give me a silo for #39 and pete will try to land it ;) [15:32] fwiw it's super simple change, should go super smooth [15:33] mvo_: could you assign it? ^ We have one silo free, but I see one silo freeing up now, so it should be fine [15:33] sure [15:33] Thanks! [15:33] done [15:33] I was about to ask if I should take over again (for ~30min or so) :) [15:34] pete-woods, please land my thing ;) [15:34] sil2100: did you publish 001 already? [15:37] No, I didn't publish any silos right now :) [15:37] mhr3: by land, you mean build, and everything right? [15:39] well, I click build... [15:39] (and it is doing stuff) [15:42] davmor2, do you remember if we have a bug open for "cant control volume when notification/snap decision is shown" ? [15:42] pete-woods: that's the first step! [15:43] erm no not that I'm aware of [15:43] k [15:43] sil2100: :) === gatox is now known as gatox_lunch [15:49] Saviq: problems with the unity8 landing? === boiko_ is now known as boiko [15:57] sil2100: renatu: https://ci-train.ubuntu.com/job/landing-008-1-build/165/console [15:57] sil2100: renatu: that is exatly why I do not like when anybody is messing around with an otherwise successful landing [15:58] Grrrrrrrrrrrrrr [15:58] mvo_, sil2100, there's something weird, could you hit rebuild on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-005/+build/6208775 ? [15:58] mhr3: pushed rebuild [15:58] bzoltan: geh... yeah, exactly [15:58] jup [15:58]