[02:10] === IMAGE 63 building (started: 20150112-02:10) === [03:10] === IMAGE RTM 191 building (started: 20150112-03:10) === [03:25] === IMAGE 63 DONE (finished: 20150112-03:25) === [03:25] === changelog: http://people.canonical.com/~ogra/touch-image-stats/63.changes === [04:15] === IMAGE RTM 191 DONE (finished: 20150112-04:15) === [04:15] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/191.changes === [05:57] robru: if you still here :) Mirv will not be around for three weeks [06:21] bzoltan: ah but sil should be back today ;-) what's up? [06:24] robru: his family income per capital just got reduced by about 27% [06:25] bzoltan: I hope that's a euphemism for "having a child" because otherwise that sounds like a really shitty pay cut... [06:26] robru: as his manager I can ensure that his pay did not change :D [06:27] bzoltan: who are we talking about? I thought steve was sil's manager? [06:30] robru: Ohh ... Mirv is reporting to me [06:30] ah [06:30] bzoltan: so what can I do for you? I don't see anything to do in the dashboard [06:52] robru: nothing right now :) I just informed you. I will have two landings today .. both vivid and RTM... hopefully. The silo1 in both. But RTM needs QA signoff and the vivid needs some testing [06:53] bzoltan: OK, I'm eoding now, but sil should be around shortly to publish stuff [07:33] Morning === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: - [07:58] good morning [07:58] trainguards, could someone reconfigure the silo for line 30 in the spreadsheet? [08:18] tvoss: sure! [08:18] Reconfiguring [08:18] sil2100, welcome back and a happy new year :) [08:18] sil2100, thanks [08:18] tvoss: thanks :) Is that silo 20 that you want reconfigured? [08:19] sil2100, silo 10 it is [08:19] sil2100, should become an rtm silo [08:20] Ah, so it's line 21 then [08:21] tvoss: hm, ok, so in this case we need to free this silo and re-assign it, as only this way we can change the target series [08:21] tvoss: is that ok? [08:21] sil2100, sure [08:30] tvoss: ok, reassigned - just be aware that you already have a location-service rtm silo in 005 [08:30] sil2100, thank you [08:50] trainguards ↑ indeed, please do :) [08:50] o/ [08:50] Love RTM fixes :) [08:52] Saviq: assigned [08:53] sil2100, o/ welcome back! [08:56] sil2100, the spreadsheet doesn't look good (yet?) [08:57] hmm, the spreadsheet never looks good! And it's really slow [08:57] ok let's see if it gets up to speed soon [08:58] I would decrease the update timers a bit, but now that we have more silos than before it might again just die and race a lot [09:08] * ogra_ yawns [09:09] ogra_, welcome back :) [09:09] hey hey ... happy new year :) [09:11] sil2100, looks like the last system-settings upload broke 120 tests on RTM [09:13] Happy new year indeed [09:14] ogra_: when was the system-image upload? [09:14] Damn, my commitlogs are broken again, crap [09:19] bah [09:19] sil2100, ogra_ - hey long time :) [09:19] yeah, 4 weeks :) [09:20] feels like it was last year though [09:21] ogra_, it was :) [09:21] :) === chihchun is now known as chihchun_afk [09:27] Ah... I see why commitlogs broke, of course [09:27] Out of disk space again... === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [09:59] trainguards, can I haz silo for line 52, please? [09:59] tvoss: sure! We have a meeting now, so will assign once it's over [09:59] sil2100, thx [10:10] tvoss: wow, another location-service silo? ;) [10:10] sil2100, yup [10:11] sil2100, got some fixes staged, landing one by one [10:11] hm, btw. I still don't see this bug as approved by the product team [10:11] I'll assign it but make sure you push them to review it [10:15] trainguards, hello, may i ask for reconfiguring of silo rtm 11 (added MP from another project, my attempt to reconfig failed) [10:15] ? [10:23] pstolowski: sure thing :) [10:24] pstolowski: reconfigured [10:25] sil2100, thanks! [10:31] davmor2: have updated http://pad.ubuntu.com/MusicAppManualTesting for latest tests for search [10:32] popey: yeah it'll be me testing latter on I'll give you a ping after lunch when I start on it [10:35] davmor2: awesome, thanks. If you see I missed any test cases let me know and I'll add them. want to make it as comprehensive as possible. [10:36] popey: will do [10:36] ta [11:31] zbenjamin, bzoltan: I'm trying to assign a silo for you right now but seem to be encountering some problems, in the middle of debugging those now [11:32] Ah [11:33] Ok, see the problem [11:34] zbenjamin, bzoltan: could anyone of you re-submit and re-approve the https://code.launchpad.net/~binli/qtcreator-plugin-ubuntu/lp1409596/+merge/246089 merge? Currently it's targetting lp:ubuntu/qtcreator-plugin-ubuntu which is not your trunk, it's the distro branch [11:34] sil2100, can you get me the last version of system-settings? [11:34] sil2100, i'll try reverting it now [11:34] sil2100: ok [11:35] brendand: you mean, you want the last working (non broken) version of u-s-s? [11:36] sil2100, well just the previous version [11:36] brendand: well, it seems there have been multiple releases since image #186 when autopilot broke [11:37] 0.3+15.04.20141211~rtm-0ubuntu1 is the version pre-#186, I can fetch you the packages for that [11:37] sil2100, ok [11:38] brendand: http://paste.ubuntu.com/9717897/ [11:39] sil2100: i changed line 53 to target the correct version [11:41] sil2100: uh something is wrong [11:41] sil2100: we remove that mp [11:41] sil2100: i completely removed it now === MacSlow is now known as MacSlow|lunch [11:50] zbenjamin: sil2100: let's just reject that MR .. [11:51] bzoltan: i just set it to "needs fixing" [11:51] bzoltan: and removed it from the lnading [11:52] zbenjamin, bzoltan: so you don't need it in this landing? [11:53] Ok, let me assign then now [11:53] sil2100: no it can wait till its fixed [11:54] sil2100: thx :) [11:55] yw :) [12:24] popey: just signed into instagram and facebook on 191 I photos for both :) [12:24] ☹ [12:24] #191? [12:47] * sil2100 goes to lunch [12:47] popey: latest rtm image [12:49] hm [12:51] davmor2: Dispatching search: "com.canonical.scopes.instagram_instagram" "" "" [12:51] file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool [12:51] i get that in my unity8-dash.log [12:52] popey: one for cwayne when he gets up then [12:52] yeah [12:52] thanks for checking [12:52] popey: no worries moving onto Music app after Lunch [12:52] ta [12:52] ogra_: happy new year :-) [12:52] Chinese new year already? ☻ [13:00] rsalveti, same to you ! === alan_g is now known as alan_g|lunch [13:01] davmor2: changelog sent :) sorry if its late, was a bit sick friday :/ === greyback_ is now known as greyback [13:02] cwayne: *pounce* [13:03] cwayne: poor excuse ;) I can look at it latter :) [13:03] cwayne: http://people.canonical.com/~alan/screenshots/device-2015-01-12-130210.png [13:03] cwayne: Dispatching search: "com.canonical.scopes.instagram_instagram" "" "" [13:03] cwayne: file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool [13:03] i do have an account setup, but it doesnt seem to work [13:06] popey: that's an old version, if you go into system settings -> accounts -> instagram, is the scope checked off to grant access? [13:06] cwayne: scope not listed [13:06] cwayne: I'm on the very latest image [13:07] cwayne: http://people.canonical.com/~alan/screenshots/device-2015-01-12-130616.png [13:08] latest promoted or latest -proposed [13:08] also, what does account-console list show [13:08] i think this is another instance of stuff getting borked when i had to move the account-plugin into the same click to make sure that it could get into the store [13:09] i am on proposed [13:09] ubuntu-touch/ubuntu-rtm/14.09-proposed [13:14] popey: try running this then rebooting: adb shell "sqlite3 /home/phablet/.config/libaccounts-glib/accounts.db \"UPDATE Services SET provider='com.canonical.scopes.instagram_instagramaccount' WHERE provider='com.account.plugin.instagram_instagram';\"" [13:16] hmmm [13:28] nice [13:28] cwayne: that fixed it, thank you [13:39] popey: np === alan_g|lunch is now known as alan_g === MacSlow|lunch is now known as MacSlow === karni is now known as karni-afk [14:43] cwayne: hey and happy new year :) fyi rtm silo 010. we'll need a custom tarball regeneration [14:53] o/ === chrisccoulson_ is now known as chrisccoulson === plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: - [15:05] a [15:09] jdstrand: happy new year to you as well :) when do you expect silo 10 to land? we were about to land a custom tar, but if yours is imminent we can hold off til later today/tomorrow to coordinate [15:16] brendand: how's the system-settings AP investigation going? [15:17] sil2100, interestingly... [15:17] brendand: is it still reproducible in the previous u-s-s version? [15:17] sil2100, yes. the working theory now is the regression is in some package that is installed by the test. maybe autopilot itself [15:18] sil2100, so we need to look at dates/times [15:18] http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/186.commitlog <- this is what landed in #186, so I suspect it's one of those packages that caused it [15:18] sil2100, what changed between the time it last worked and the time it started failing [15:19] There's an UITK change in this image, but the description seems unrelated, hm [15:20] cwayne: I've been waiting for QA signoff since last... thursday? [15:20] cwayne: I was told that qa should do it sometime today [15:20] *by* sometime today [15:23] hm, ok [15:23] davmor2: sil2100^ i think we should probably then hold off on custom until that lands [15:23] jibel, brendand, davmor2: ^ ? [15:23] otherwise you'll have to do custom twice :) [15:24] QA page says silo 10 passed [15:24] jdstrand, ^^ [15:24] oh, I just checked the spreadsheet a few minutes ago... [15:25] (the landing spreadsheet) [15:25] sil2100, jdstrand rvr tested it [15:25] the landing spreadsheet still says 'QA needs to sign off' [15:25] but, that's fine [15:25] cwayne: looks like it passed. I guess you can regenerate? [15:26] jdstrand: well, is it in the image/archives yet? [15:27] cwayne: no. that's right, I forgot, you need it there first [15:27] so, if someone tells me to push it, I will [15:29] jibel: I wonder if rvr is having the issue I have sometimes you change the spreadsheet to passed it looks to change for you but the sync to actually change the sheet is dead so it never gets updated except locally, I of course blame ogra_ for that ;) \o/ so glad ogra_ is back :) [15:29] jdstrand: is that rtm silo 10? [15:29] sil2100: it is [15:30] jdstrand: hm, it's not set to tested done by QA yet on the spreadsheet, right? [15:30] Or are my eyes just wrong? [15:30] rvr: you tested silo10 right? [15:30] sil2100: you are right and so are mine. others said it was tested by qa on some other list [15:30] ygh [15:30] davmor2, don't get me started on spreadsheets please [15:31] davmor2, jibel: yeah, sometimes the spreadsheet times out and doesn't save the change... [15:31] jdstrand, sil2100 I think rvr just forgot to mark it https://trello.com/b/AE3swczu/silo-testing [15:31] sil2100, i need to get the old autopilot package for system-settings, where would that be? [15:31] (rvr, btw, thank you for testing) [15:31] brendand: hm, hmmm [15:32] brendand: wait a moment [15:32] sil2100: yeah I'm guessing that is what has happened here as the silo is in the passed section of the trello board [15:32] brendand: that's actually a valid question [15:32] brendand: ah, crap! [15:33] brendand: ok, let me give it to you [15:33] brendand, you can find all the version here https://launchpad.net/ubuntu-rtm/+source/ubuntu-system-settings/+publishinghistory [15:33] brendand: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-002/+build/6635435/+files/ubuntu-system-settings-autopilot_0.3%2B15.04.20141211%7Ertm-0ubuntu1_all.deb [15:33] brendand, select i386 for the autopilot tests [15:39] sil2100: could you rebuild rtm silo 2 with different version numbers. The maliit-framework that is getting synced is a lower version number than what's in rtm already https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-002 [15:42] bfiller: let me take a look at that and try dealing with it [15:42] Sadly sometimes that happens... [15:42] sil2100: thank you [15:43] bfiller: yeah, I'll fix that, since it's a common issue with the current train [15:44] jdstrand: which version of a-e-u would i need for generating the new cache? [15:59] trainguards ubuntu-rtm silo 15 is a FP, I got confused flagging the line above as ok [15:59] ^^ [15:59] alex_abreu: ACK [16:00] sil2100, thx === chihchun is now known as chihchun_afk [16:08] oSoMoN: hey! The sync request of webbrowser-app - does that carry fixes for the current milestone? [16:10] sil2100, it’s not been formally approved yet, it’s more of a request to allow testing to verify what would happen if we were to backport trunk to rtm [16:12] pmcgowan: jdstrand: Right, sorry, I forgot to mark it [16:12] oSoMoN: ok, so I'll assign a silo but leave a comment about that [16:12] Oh, ok, nevermind [16:12] sil2100, I just added a comment to make it explicit, thanks [16:12] Comment there ;) [16:12] Thanks! [16:15] cwayne: 1.2.40 [16:15] cwayne, sil2100: let me know when to push it and I will [16:15] jdstrand: i'm ready whenever you guys are [16:16] rvr: did you mark it as ready? Can we land it? Just double confirming === karni-afk is now known as karni [16:16] sil2100: 10:12 < rvr> pmcgowan: jdstrand: Right, sorry, I forgot to mark it [16:17] cwayne: do you have someone from qa who is tasked with testing your new custom tarball already? [16:17] basically, I don't want to push it and then the custom testing/push lags [16:18] jdstrand: then it's all fine for me for releasing it, cwayne would that slow you down or can we release? [16:20] sil2100: I found a problem with silo 6 + silo 0 + silo 10, although I think it's only a matter of silo 6 (ciborium). [16:21] sil2100: if we have people to test custom + spanish custom in ~30 minutes so that we dont have a long first boot im good [16:21] davmor2: are you busy now? [16:22] sil2100: what????? [16:22] davmor2: we needz ze custom tested in ~30 minz! [16:23] Will you have time then? [16:23] * jdstrand notes he has not pushed anything [16:23] I can push at a time that is convenient for cwayne and qa [16:23] sil2100: No I'll be in a meeting in 30 minutes I can test after the meetings and tea though [16:24] What a coincidence, I'll be in a meeting in 30 minutes as well [16:31] alex_abreu: hey! Can you make sure all merges in silo 008 are approved? [16:31] sil2100, sure [16:35] alex_abreu: tell me when I can re-publish the silo [16:36] sil2100, ok you can [16:42] brendand: any luck on the investigation? Do you think this should block our promotion plans for today? [16:42] sil2100, yeah, reverting the autopilot package fixes it [16:43] sil2100, but there's nothing we can do about that now. blocking the promotion won't achieve anything [16:43] * sil2100 checks the diff [16:43] brendand: yeah [16:45] sil2100: jdstrand: so what's the deal? would davmor2 and rvr be able to test the customs [16:45] cwayne: yeah, after our landing meeting in 15 minutes davmor2 should still have some time I suppose [16:49] sil2100: we'd need someone to test spanish too, at least a brief check -- we need to keep them in sync [16:49] * davmor2 blames ogra_ for all file corruptions now, you just keep lining up jobs to blame you for :P [16:50] sil2100: so, should I push it now then? [16:51] rvr: you around for some time still, right? [16:53] sil2100: One hour or so [16:53] jdstrand: ok, so please push it if you can :) [16:54] ok, I'll do it in just a moment [16:55] davmor2, rvr: once jdstrand releases his silo, could you take a look at the custom+spanish_custom tarballs? [16:56] sil2100: I can take a look, but can't promise I'll finish today [16:56] sil2100: NO :P :D [16:57] jdstrand: Seems the issue I found is known and not related to the silos [16:59] cwayne: ok, pushed ^ [17:00] jdstrand: thanks [17:00] not sure when the spreadsheet or the dashboard will be updated... [17:01] sil2100: I would like to execute an experiment. I would like to see how the latest UITK Vivid landing (silo1) behaves with the RTM image. May I ask for a silo with the same MR just for build and test? So not to land, but to run the tests and see all the builds. [17:02] bzoltan: hm, ok, we can do that, we just need to make sure it's commented everywhere that it's not meant to be landed then [17:04] ogra_: hey! Will you make it for the meeting? [17:04] sil2100: I will make a branch and will not top approve it ... so it will not land and I will change the control file, so it can not accidentally land ... plus add DO NOT LAND in every possible comment field. [17:04] sil2100, yeah, justfinishing up the snappy one ... [17:04] ogra_: ACK [17:04] (gimme a few) [17:05] jdstrand: sil2100: ah, wed need a rootfs with the new a-e-u right [17:05] cwayne: yes [17:06] that should be coming (1.2.40 is in -proposed atm: https://launchpad.net/ubuntu-rtm/+source/apparmor-easyprof-ubuntu/1.2.40) [17:07] davmor2: meetong [17:08] ogra_: sil2100: ^ can we get an rtm rootfs kicked off once 1.2.40 is in 14.09 [17:08] i guess we can === plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: - [17:13] kenvandine, sil2100 - here's a bug for tracking the issue: https://bugs.launchpad.net/ubuntu-rtm/+source/ubuntu-system-settings/+bug/1409809 [17:13] Launchpad bug 1409809 in ubuntu-system-settings (Ubuntu RTM) "Autopilot tests fail due to system settings not being able to start" [Undecided,New] [17:14] brendand, thanks [17:15] ogra_, sil2100 (and cwayne): https://launchpad.net/ubuntu-rtm/+source/apparmor-easyprof-ubuntu shows 1.2.40 is in release [17:15] (fyi) [17:16] jdstrand: thanks, kicking custom now [17:17] check if rmadison agrees ;) [17:17] (obviously does) [17:32] qa, hey, what is the deadline for current wave of rtm fixes (for having them tested in silos)? [17:35] sil2100, jibel: emulator is good but some apps have been removed so I have had to invalidate the one test for now, and modified the downloaded app for ebay so that one could pass. So it is as good as it ever is [17:35] sil2100: davmor2: rvr: so assuming an RTM rootfs has been kicked, I think the custom image to test will be 270 [17:35] cwayne: thanks [17:36] cwayne: Is there a new image for custom-proposed-es? [17:36] I was flashing 43 [17:37] rvr: there will be with the new rootfs, it would be 45 [17:37] cwayne: Ok [17:37] rvr: the scopes will be the same in 43 and 45, so if you want to test the OOBE on 43 then all that would need to be checked on 45 is that the cache was updated [17:39] i've got to go run some errands, so all please shoot me an email if there's any questions [17:42] davmor2: \o/ [17:42] davmor2: thanks! [17:42] jibel: so, any final words before we promote? [17:42] sil2100, +1 to promote [17:43] jibel: it's 188, right? [17:43] sil2100, krillin/rtm/188 is what we tested [17:43] ogra_: could you promote rtm 188 for krillin and its counterparts for mako and emulator? :) [17:43] sil2100, mako 157 and the rest is 151 [17:43] The spanish might be also needed to be promoted, right? [17:43] sil2100, sure, gimme a bit [17:44] But not sure if it got tested well enough [17:44] yes [17:52] sil2100: ^ this is my experimental silo request [17:52] bzoltan: I love the big caps-lock warning! [17:52] sil2100: :D [17:53] ;) [18:06] === IMAGE RTM 13 promoted === [18:06] that is: krillin 188, mako 157, emulators 151 [18:06] jibel, which es image should i promote ? [18:07] ogra_, 137 [18:07] thx [18:09] === IMAGE RTM.es #7 promoted === [18:09] (krillin 137 as above) [18:09] ogra_: thanks! :) === alan_g is now known as alan_g|EOD [18:11] sil2100: would you please reconf the rtm silo10 [18:20] bzoltan: sure [18:20] ogra_: is emulator image promoted as #13 as well? Or as #12? [18:21] sil2100, oh, right, yeah, emulator is one behind [18:24] ogra_: Is es-proposed-customized still building? [18:25] rvr, i dont think anything is building atm [18:25] bzoltan: done ;) [18:25] Ok, I'm off outside now, bbl [18:25] cwayne: No image 45 then? :-/ [18:26] rvr, es-proposed-customized is nothing we build, thats solely cwayne's thing i think [18:26] ogra_: Ah, ok [18:27] I'm hitting [F5] on that channel compulsively :) [18:27] 44 is from 1h ago apparently [18:27] do you expect anything newer ? [18:27] Yup, cwayne specifically mentioned 45 [18:28] ah, k [18:28] trainguards, can I get vivid silos for lines 59, 60 and 61 please? [18:30] tedg: on it [18:30] robru, Great, thanks! [18:31] tedg: well row 59 will need to be not blank before I can assign it [18:31] Hmm, not blank for me… [18:32] tedg: rows 60 and 61 got 8 and 13 [18:32] tedg: weird, just refreshed the spreadsheet and line 59 showed up. weird sync glitch I guess [18:33] robru, Okay, whew, I couldn't figure out anything else to do to it :-) [18:33] tedg: line 59 got silo 16 ;-) [18:34] robru, Cool, thanks! [18:34] tedg: worst case, reload the spreadsheet, if the row was missing, re-enter the data. it happens sometimes. [18:34] tedg: you're welcome! [18:36] * tedg wonders if 2015 will be the year the spreadsheet dies [18:38] cwayne: 2015/01/12 18:38:02 Flashing version 269 is still trying to be downloaded :( [18:38] tedg: I would guesstimate we are a month away from killing the spreadsheet. it's happening, just slowly. [18:39] or rather, "it's happening, just constantly fraught with setbacks and distractions." [18:39] tedg: also robru lies ;) [18:40] davmor2, So there's no setbacks and distractions? ;-) [18:40] * tedg will not miss the spreadsheet [18:41] Okay, packages building, device reflashing, lunch! [18:44] tedg: you and everybody else! (not missing the spreadsheet, that is, not lunch) [18:45] bfiller: silo 17 [18:55] wait so was there a new rootfs [18:56] ogra_: ^ [19:00] slangasek: sil2100: Ursinha: I vote we cancel our meeting now as there's not much to discuss (I'll send an email update shortly with some staging instance details) [19:01] unless anyone disagrees... [19:02] davmor2: ^ [19:03] robru, sil2100, Ursinha: well maybe sil2100 wants to say happy new year to everybody? :) [19:03] but I'm ok to cancel if you all agree there's nothing to discuss [19:04] slangasek: aha, already did say happy new year at that other meeting 2 hours ago ;-) [19:04] heh [19:07] Happy New Year! [19:07] ;) [19:07] No, I'm fine with skipping, I just got back like 10 minutes ago anyway [19:08] sil2100: k, great. [19:08] sil2100: I'm still working on the staging bringup. I fixed SSO but now there's some firewall issue stopping it from working. once I get a successful build out of it I'll email those instructions on how to use it. [19:13] sil2100: was there a new rootfs kicked? if not we can just do the custom test tomorrow morning [19:14] sil2100: Šťastný nový rok [19:15] sil2100: ogra_ talk to us please [19:15] davmor2: hey! [19:15] cwayne: no new rootfs was kicked [19:16] sil2100: cwayne so tomorrow am then right? [19:16] We didn't have a new image yet, there will be an auto-build later at night [19:16] sil2100: that'll be too late for anyone to test though at a guess [19:16] We wanted to have the custom landed so that the new image doesn't have any issues [19:17] We could theoretically disable the cronjob and just kick the image manually tomorrow once the custom is tested... [19:17] robru: ugh, ok, thanks! [19:17] sil2100: custom needs the new rootfs to be tested though [19:19] davmor2: can you test it with changes from a silo? [19:19] sil2100: how many silos have landed? [19:19] For RTM it might have been only one silo landing today [19:20] davmor2: since if we have a new rootfs (a new image) built during the night, this would mean some users will get long boot times, right? [19:21] sil2100: well there is the 3 that meant that silo 10 could land and then I think there were one or 2 so that is 4-5 and then that has to be installed after the custom tarball image has been installed [19:21] not sure how well that would work [19:22] davmor2: hm, why so many silos? Today there was only this silo landing, and we have a rootfs with all the others already [19:24] sil2100: silo 10 depended on 006 and 001 and then there is any that have passed today [19:25] davmor2: yeah, but none of those landed yet, only silo 10 [19:26] So do we need to land 006 and 001 along with the tarball? [19:27] sil2100: so I'm around for 30 minutes, and by the sound of it if the app armor fix isn't in place it will take 10 minutes to boot the image after I have bootstrapped on the image to test that has the tarball in place [19:31] sil2100: the problem we have is that cwayne has been waiting for the new rootfs to build so he could trigger the tarball and we test image 270, we can test 269 and install all the ppa's but that kinda defeats the object, so it looks like this will get tested in the morning now by the sound of it :( [19:32] Ok, then there was some miscommunication here then [19:32] hm, so I would actually prefer everything happening at once [19:33] So maybe let's disable the cronjob for today, what do you say? [19:34] sil2100: what does cancelling the cronjob do though? [19:34] sil2100: you can build the new rootfs and then we just test the new 270 image in the morning [19:36] sil2100: we need the app-armor fix in place so that the custom image doesn't take a week to boot unless I'm misunderstanding cwayne [19:36] righto [19:39] sil2100: so as I see it we can cancel the cronjob, do a manual build first thing tomorrow your time, which should finish when I get online I can then test the new 270 image and a few hours latter you can release that done. The other thing we could do is remove the ota tag from the build that we make so that cwayne can build on it but users don't upgrade to it [19:41] so i've got the custom tar all set davmor2 since it's in the archive [19:41] so if you cancel the cron and do it early UK time, you guys can start testing as soon as a rootfs is done [19:42] sil2100: ^ [19:44] hm, ok [19:44] So then I misunderstood it, I thought it's actually the other way around [19:45] Then we don't need to disable the cronjob as, if I understood davmor2 and cwayne now, releasing the custom tarball would cause the long boot times [19:45] If that's the case, then let's leave everything as it is and take care of the custom tomorrow morning [19:45] sil2100: wilko [19:46] no no no [19:46] the rootfs will cause the long boot times [19:46] the custom will fix it [19:46] Ok, so it's as I thought [19:46] davmor2: ^ [19:46] but the custom is already built, so it can be tested as soon as the rootfs is done [19:46] i.e. doesn't need to wait for my morning [19:47] head is spinning now [19:47] Yeah, but it's best if those two are done with as short delay as possible, so let's disable the cron and do the rootfs build and custom testing on davmor2's morning [19:47]