[00:00] robru: OK, we've thought of one detail that needs to be put in place to make sure that translation message sharing works properly before starting imports, but I know what to do now and the translations can sit in the import queue until I've done it. [00:01] cjwatson: OK, need anything from the train side? [00:04] robru: Nope, thanks [00:05] Best collect the hacks for this in one place [00:05] cjwatson: great, thanks for taking care of that. [00:05] I feel kind of dirty but at least it wasn't too hard :-) [00:07] There's also a hidden dependency here on the fact that the silos are devirtualised, which is the only reason that translations are getting stripped [00:07] But we can just keep that flag even after devirtualisation otherwise no longer matters [00:08] Well, except ephemeral PPAs, hmm, will have to think about that [00:11] cjwatson: ephemeral train silos are a long way off, no hurry [00:13] robru: Indeed, but in part because LP won't let you create them. [00:13] We like to not be in people's way for important projects. [00:13] cjwatson: haha, indeed [00:13] cjwatson: is it just that we can't create devirt ppas, or does lp api actually not allow ppa creation at all? [00:16] robru: Oh, you can create them, but you can't configure them the way silos should be configured (especially but not limited to devirt) without giving ci-train-bot a scary amount of privilege. And anyway other bits of the workflows for PPAs we expect to be deleted and forgotten about at the end probably aren't quite right. [00:16] cjwatson: I see. [00:17] It's moot until we get scalingstack for all arches, anyway, but shouldn't be too hard at that point. [00:18] A thing that lets you configure relatively unprivileged aspects of PPAs would be not that scary, it's just devirt that's kind of verging on admin privileges. [00:18] cjwatson: yeah definitely don't want bots with admin. [00:18] What's the work on your end? [00:18] Just the logic to create and clean up? [00:18] cjwatson: yeah basically [00:18] Or is there non-trivial assignment logic as well? [00:19] cjwatson: currently it determines what silos exist by querying lp api, would need to change some of that logic to care less about what PPAs exist and just create them as necessary. [00:19] I guess it would mostly be deleting code. [00:19] cjwatson: depends how many lp api calls it would take to create the PPA with the right settings. [00:20] cjwatson: lots of ppa-discovery code would go away, but then lots of ppa-creation and deletion code would take it's place [00:21] We could probably just give person.createPPA more arguments. [00:21] No point in making you create and configure it separately just because we hate you and want you to write more code or something. [00:21] hehe [00:22] cjwatson: it's probably not a huge change measuring by lines of code, but there's certain architectural assumptions that would have to change and that could have some growing pains. [00:23] k [00:23] Well, scalingstack for everything is still probably months away not weeks, so no rush [00:23] cjwatson: anyway, we're focused on the spreadsheet replacement for now so the ephemeral PPAs thing isn't blocking us badly. [00:23] OK [01:23] robru: still around perchance? :-) [01:24] veebers: yeah what's up [01:25] robru: hey :-) First, is it possible to make the new citrain site https only? (I get a warning dialog when using it) [01:26] veebers: production will be https. I didn't bother to make a cert for the staging area. [01:27] robru: ah, ack :-) Second, prob dumb Q, landing for the devices (i.e. overlay ppa) which distro is that? ubuntu or ubuntu-rtm? [01:27] veebers: it's all ubuntu for now [01:27] robru: ah ack, thanks for the clarification :-) [01:27] veebers: you're welcome [01:56] robru: if you're still around :-) seems packages failed to build due to signing. http://ci-train.staging.ubuntu.com/job/ubuntu-landing-001-1-build/1/console [01:59] veebers: just eating, will look later, thanks for trying. [02:00] robru: nw. Should I be using the old spreadsheet if I need this landed or will this do the jobfor me? [02:11] veebers: you need the spreadsheet for a real landing. The staging area is not eligible for real publishing to distro [02:12] robru: oh, hah, sorry I had the wrong end of that :-) I'll fire up a spreadsheet landing now [02:12] I'm hoping this'll go live in a week or two [02:15] veebers: i think you looked at the wrong part of that log. Build failed in ppa: https://launchpadlibrarian.net/211049255/buildlog_ubuntu-wily-amd64.autopilot_1.5.1%2B15.10.20150708-0ubuntu1_BUILDING.txt.gz [02:16] veebers: you can now assign your own from the spreadsheet, enjoy ;-) [02:16] robru: I hope it goes live too, its a much nicer interface [02:18] veebers: thanks [03:31] trainguards, I've been told I can assign a silo from the spreadsheet, unsure how though [03:37] veebers: "landing tools > assign/reconfigure" menu [03:37] fyi, pmcgowan said this (line 82) needs to land tomorrow (part of fix for bug #1462489) [03:37] bug 1462489 in apparmor-easyprof-ubuntu (Ubuntu) "Allow apps to keep the screen on" [High,In progress] https://launchpad.net/bugs/1462489 [03:38] jdstrand: you can now assign your own silos. Go crazy [03:38] oh, I missed that [03:38] jdstrand: let me know if you need any help [03:39] robru: where are the instructions? on ubuntu-phone? [03:39] jdstrand: no instructions really, this is a small change phased in ahead of the larger spreadsheet replacement change coming soon [03:40] jdstrand: just go to the landing tools menu and follow the prompt to assign [03:40] jdstrand: veebers make sure the right row is highlighted first [03:40] robru: ah coolio, thanks [03:40] ack [03:40] robru: oh, cool :) [03:40] veebers: you're welcome [03:41] I'm eod 3 hours ago but happy to help if anything goes wrong [03:44] robru: nice, thanks :-) [03:45] robru: worked well, thanks :) [03:45] veebers: jdstrand you're welcome! === chihchun_afk is now known as chihchun [04:56] and I'm awake now [06:33] Good morning trainguards! Can I have a silo for line 83, please? [06:33] oSoMoN: done, silo 035 [06:33] Mirv, thanks! [07:25] jibel: hi. With the problems you highlighted in the thumbnailer (silo 10), what exactly did you see on arale? Black thumbnails, a placeholder image, or something else? [07:40] woah [07:41] what made the session startup so slow ? [07:41] it takes a felt 20sec more with todays image [07:45] woah ... over 80seconds ... [07:45] that used to be way below 1min ... (krillin) [07:46] jibel, davmor2 ^^^ did that not happen during QA testing ? [07:53] * ogra_ files bug 1472507 [07:53] bug 1472507 in Canonical System Image "extremely slow session startup after upgrade" [Undecided,New] https://launchpad.net/bugs/1472507 [07:55] ogra_, I didn't see that but victorp mentioned it yesterday too. I'll have a look. [07:56] victorp, ^^^ you might want to "ne too" that (or duplicate it against your bug if you opened one) [07:56] *me too [07:57] (so it gets confirmed status) [07:57] ogra_: how long does arale take to boot for you on 51? from vibrate to lock screen? [07:58] right now, yeah, it was way less before [07:58] between 30 and 40 [07:58] i think sturmflut said hiw boots in 22sec :) not sure how he measured that :) [07:59] i have 50 on my arale and it takes 50 s [07:59] so not sure it's image 51 [08:05] i didnt notice it yesterday morning ... could indeed also have been 49 to 50 where it broke ... [08:05] i definitely know it wasnt that slow on monday [08:09] new unity8 on monday :) [08:10] ogra_, ack [08:13] ogra_, it is slow right after the upgrade or on every boot? [08:16] could somebody get https://bugs.launchpad.net/canonical-devices-system-image/+bug/1472161 on the milestone list? [08:16] Launchpad bug 1472161 in webbrowser-app (Ubuntu) "[regression] full URL is not displayed when focusing the address bar" [High,In progress] [08:16] ogra_, ok, 1:40 from the moment the screen turns on with the bq logo to the first sim prompt on krillin. [08:16] that's sile 35 and a regression in ota5 [08:18] ogra_, and 18s on arale [08:19] same image [08:23] jibel: hi. Could you provide a bit more detail about the problems on arale that you encountered testing the thumbnailer in silo-010? What did the missing thumbnails look like? [08:35] jamesh, Hey, missing thumbnails look like a placeholder image [08:35] jibel, yeah, 1:40 isnt good, we were below a minute ... and yes, i can reproduce it every boot [08:35] odd, fine here. [08:36] ogra_, I know it isn't good, especially compared to arale [08:36] jibel: but all other thumbnails showed up correctly? (just want to make sure the thumbnailer-service package got installed correctly: it gets skipped by "citrain device-upgrade" if you don't have libleveldb1 installed) [08:37] jamesh, the package was installed, I don't use citrain device-upgrade and do it manually [08:37] jamesh, the solution to that is to copy libleveldb1 into your silo (citrain install disables the main archive to not taint the testing) [08:38] jibel: okay. I wouldn't mind seeing an excerpt from ~/.cache/upstart/dbus.log when this occurs. [08:38] jibel, ogra_: can we somehow identify when this regressed? [08:38] sil2100, well, i can only say it regressed today for me [08:38] jamesh, okay, I'm looking into this long boot issue which is more pressing and will reinstall the silo afterward [08:38] and it doesnt seem to be consistent ... some people do not see it it seems [08:38] Then somewhere here http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/60.commitlog [08:39] while jibel victorp and i can repro it, popey and sturmflut can not [08:39] sil2100, i linked to my changelo in the bug ... [08:39] ogra_, when you test your device is plugged or unplugged to usb? [08:39] * ogra_ checks your link [08:39] ogra_, mind you , I only managed to repo on arale, krillin updated fine [08:40] sil2100, yeah, looks similar [08:40] for me it's the other way arale is fine but not krillin [08:40] jibel, unplugged [08:40] Good morning! [08:41] i wouldnt call it critical, everything seems to work fine beyond that [08:41] (not a OTA blocker) [08:41] but it is definitely noticeable and annoying [08:41] hey sturmflut2 [08:42] ogra_, it is not consistent, this time the device booted in 55s [08:42] funny [08:42] * ogra_ reboots his krillin again [08:43] I'll upgrade my krillin and see if I see the same thing [08:43] sil2100: want these new clicks uploaded to the store? [08:43] while i like most of the new icons, the cellular one is really awful in its steepness [08:43] popey: yes please :) [08:43] ok [08:46] Ok, anyway, let's close the landing gates - I see we might have some blocker fixes approved to land anyway, but for now we lock down [08:46] jibel, exactly 100sec this time ... 20sec for the bootsplash ... which is usual and 80 with the usc spinner [08:46] sil2100, there is a request for a device tarball for arale on the spreadsheet, do you know if it landed already? [08:47] ogra_, that's what I saw during previous boot [08:48] jibel: ah, the second one? Not sure, I hope alextu checks the spreadsheet... let me ask [08:48] hmm [08:48] and my arale just did it in around 20sec [08:48] (the full boot) [08:48] jibel: I see there's yet another device tarball that was ready [08:49] yeah, and again ... seems my arale only was slow for the first few boots, now it seems fast [08:50] My arale is fast as lightning [08:51] ogra_: hm, my krillin rebooted pretty fast [08:52] 95sec here again [08:53] well, someone should bootchart that ... sadly i'm busy with preparing a snappy release today :/ [08:57] 33s on krillin, the more I reboot, the faster is goes :) [08:58] jibel: we have the last device tarball, we'll need now someone to sign off the new one - it has the notification led fix in it [08:58] s/is/it [08:58] sil2100, ok [08:58] Still writing the announcement e-mail, too much distractions [09:06] ogra_, could the device try to suspend during boot like it did during shutdown? [09:06] it did ? [09:06] * ogra_ never heard of that [09:06] ogra_, maybe I misremember the exact cause but there was a long shutdown issue [09:07] ogra_, anyway, when the devices is plugged boot time is always between 30 to 35s [09:07] well, thats usually due to wrong stop on lines in upstart jobs [09:07] let me plug in mine [09:08] 16sec bootsplash [09:09] 20sec session [09:09] wow ! [09:10] sil2100: calculator, calendar, clock, music, notes (reminders), shorts and weather all updated with new icons in the store. [09:10] popey: thank you! [09:10] Excellent [09:11] unplugged: 20sec bootsplash, 80sec session again [09:19] jibel, do you think bug #1472161/silo 35 can/should be included in the ota5 landings? (it's to fix a regression in the current candidate) [09:19] bug 1472161 in webbrowser-app (Ubuntu) "[regression] full URL is not displayed when focusing the address bar" [High,In progress] https://launchpad.net/bugs/1472161 [09:20] seb128: we'll have to wait for Pat to pop-up for a final decision anyway... but in overall we don't like regressions [09:21] seb128, yeah, set it to ready for QA and we'll try to land it [09:21] jibel, thanks [09:39] AlbertA: how did qtubuntu-* end up getting in? [09:43] sil2100, so the plan is to try to land what is currently in the ready for testing queue + silo 35 seb128 mentioned earlier if it is ready on time. Then you can build a first candidate. [09:43] sil2100, Is there anything else to land? [09:44] sil2100, I think we needed a policy group fix for qtsystem that landed yesterday [09:45] jibel, oSoMoN: I just tested silo 35 and marked it as testing pass on the ci table [09:48] seb128, thanks, I also validated it on my side, I was waiting for someone on my team to review it, but if we’re in a hurry I think it’s perfectly safe to land now [09:56] oSoMoN, no idea when it needs to land, but today I guess [09:56] qa can verify it meanwhile [09:57] seb128, yeah, landing today would be good [10:02] trainguards, hello, silo 42 has been in proposed pocket for quite a while (for around 20hrs i think), any idea why is that? [10:04] pstolowski, https://launchpad.net/ubuntu/+source/unity-scopes-api/0.6.19+15.10.20150706.1-0ubuntu1 [10:05] pstolowski, it failed to build on arm64 it seems [10:07] seb128, ah [10:08] pstolowski, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html is the url to check for proposed migrations [10:08] pstolowski: https://launchpadlibrarian.net/210999339/buildlog_ubuntu-wily-arm64.unity-scopes-api_0.6.19%2B15.10.20150706.1-0ubuntu1_BUILDING.txt.gz - does that look something that might fail occasionally? it can be rerun. [10:08] pstolowski: I just wonder how it was possible to publish that since it should have warned in CI Train if it failed to build in a silo for one arch [10:09] Mirv, exactly... shall I then just kick the build of unity-scopes-api? [10:10] pstolowski: why all train users are so trigger happy with new builds to fix one arch! it should be made more painful :D so no, it's already published, and single archs need to be restarted by trainguards manually (either in silo or in archives) [10:11] ogra_, ah I got a slow boot. I adbshelled to the device and apport was running. unity8 crashed [10:11] jibel, hah ! [10:11] pstolowski: rerunning now at https://launchpad.net/ubuntu/+source/unity-scopes-api/0.6.19+15.10.20150706.1-0ubuntu1/+build/7628619 - but if it fails, it might be something needs to be changed, rebuilt, and republished [10:11] ogra_, can you check if you have any crash file corresponding to a slow boot [10:11] in a previous boot it was maliit-server [10:12] pstolowski, [10:12] 18: Value of: (db->settings()["locationSetting"].get_string()) [10:12] 18: Actual: "London" [10:12] 18: Expected: ("New York") [10:12] seb128, yeah, i know, this test is a bit racy [10:12] pstolowski, k, so should the build be retried? [10:12] pstolowski, do you have a bug about the test not being stable? [10:16] seb128, yes, should be retried; no bug yet === pstolowski is now known as pstolowski|lunch [10:18] pstolowski|lunch, can you open one? [10:19] seb128, willd do [10:20] thanks [10:22] sil2100: today scope still has old calendar icon, do you know if that's being updated? [10:31] popey: hm, not sure [10:31] rvr, I take silo 21 can you do 35 after 26? [10:31] jibel: Yes [10:31] jibel: just so you know... silo 36 might need to be landed as an exception as well [10:31] sil2100: I'll ask the icon designer [10:31] jibel: it seems management wanted that [10:33] sil2100, well if we want to release something it has to stop at some point. The silo is not even built [10:33] jibel: yeah... mzanetti is rebuilding it since some other silo landed in the meantime [10:33] sil2100, jibel: nope. silo7 hasn't landed yet [10:33] will have to rebuild after that [10:33] It's for the arale look and feel [10:34] mzanetti: is 007 more important? [10:34] currently just building/testing to be prepared for when the other is out of the way [10:34] sil2100, it's not... but it's approved and tested by gerry already [10:34] Yeah, but QA is not testing it yet, so I would say we should prioritize [10:35] jibel, yes, lots .. unity8, -dash, maliit and whoopsie-upload-all [10:38] ogra_, that would explain why it is inconsistent, if the same process crash again it won't be reported === greyback__ is now known as greyback [10:42] pstolowski|lunch, retry failed on the same test, I do another retry [10:48] jibel, yeah [11:15] ogra_, and again, unity8 unity8-dash and maliit crashes, it took nearly 2 minutes to boot [11:15] wow, that starts to sound more critical [11:40] jibel, hmm, my arale just locked up hard ... doesnt take inout [11:40] *input [11:44] can the ci train spreadsheet replacement work for click packages/tarballs? [11:44] sil2100: ^ === pstolowski|lunch is now known as pstolowski [12:01] seb128, hmm if this keeps failing I may need to rollback on of the changes from that silo which perhaps made things worse than before [12:10] ogra_: around? https://ci-train.ubuntu.com/job/ubuntu-landing-003-2-publish/lastSuccessfulBuild/artifact/ubuntu-ui-toolkit_packaging_changes.diff - one universe binary package (ubuntu-ui-toolkit-autopilot) new dependency on an universe package, is that ok? [12:10] even though src plus some of the other binary packages are in main [12:10] Mirv, as long as it is properly mentioned in the changelog :) [12:11] * ogra_ will take a look soon (sorry, busy atm) [12:11] ok [12:12] cwayne: yes :) [12:12] cwayne: it doesn't build them, but it can be used to track non-train landings [12:13] rhuddie: hey! your UITK commit message does not include the information about addind a new dependency in debian/control, which is a requirement for any debian/ changes [12:13] sil2100: neat! [12:15] rhuddie, i usually dont sign off packages that dont explicitly mention the dependency change ... please make sure to do this properly next time ... (for now i'll approve it) [12:15] Mirv, with the above .... ACK [12:17] My arale battery is really good since the few last updates [12:18] Mirv, ogra_, ack. I'll remember for future so its not missed [12:18] ogra_: :( I mean, nice for ack, not nice for your quest for educating people being hard. FYI the bug of autochecking that by CI Train was deemed a bit hard to implement. [12:18] I still think that's the only right way, CI check for it. [12:18] yeah, i can imagine that the logic for that is hard === _salem is now known as salem_ [12:27] ogra_, the dash crash I get on boot is bug 1363946 [12:27] bug 1303637 in unity-scopes-api (Ubuntu) "duplicate for #1363946 scoperunner in RegistryI test fails if locale is not set" [Low,Confirmed] https://launchpad.net/bugs/1303637 [12:27] mzanetti, ^ [12:28] pstolowski, yeah, 3rd retry failed as well, doing another one but you might consider looking at fixing the issue or disabling the test if it's a buggy one [12:28] or better fixing it ;-) [12:28] ogra_, maliit-server is https://errors.ubuntu.com/oops/6874ad2a-2562-11e5-8f47-fa163e525ba7 but not fully retraced and quite popular on 15.04 [12:28] seb128, is there an arm64 machine i could access and debug this test? [12:29] and unity8 failed to retrace completely [12:29] seb128, i'm just running this test in a loop on the desktop and it passess... [12:29] pstolowski, try asking on #ubuntu-devel about porting boxes, or try arm64-porter.canonical.com [12:30] jibel, well, i'm not as concerned about it crashing on every boot as i am about the hard lock [12:32] seb128, ok, thanks === mvo_ is now known as mvo [13:22] pmcgowan: hey, apparmor-easyprof-ubuntu is in silo 17 for stable-phone-overlay and I'm finishing up testing now [13:22] pmcgowan: I wasn't sure what to put in 'QA signoff needed' though [13:22] jdstrand, awesome, jibel ^^ [13:24] pmcgowan: /win 29 [13:24] meh [13:28] boiko: Silo 26 approved [13:28] rvr: great! thanks a lot! [13:28] salem_: ^ [13:29] boiko, rvr awesome, thanks. [13:31] rvr, can you pick silo 17 when it's ready? [13:31] jibel: Ack [13:32] jdstrand, can we start the verification of silo 17 or you think it's better to wait until you finished testing? [13:32] Packages built [13:52] sil2100. popey: has anyone uploaded the new camera app to the store yet? [13:53] bfiller: I don't think so... [13:53] bfiller: we only landed it to the archive [13:53] popey: ? [13:53] sil2100: I was out last two days, needs to happen. I can do it now, hopefully the final image hasn't been spun yet [13:53] Nope [13:53] I only did gallery [13:54] bfiller: no worries, silos still being signed off and translations in progress of being exported [13:54] sil2100: cool, will do now [13:54] bfiller: so please release :) [13:54] Thanks [13:57] jibel: go ahead [13:58] sil2100, pmcgowan: ok. 36 good to go [13:58] o/ [13:58] My target date to kick the new image is around 19 of my time, so in ~3 hours [13:59] Mirv, seb128 about that test failure on arm64 and silo 42: it's not clear why it fails only on this arch, i've requested access to arm64 box to debug this, but it may take time. does this block entire landing? if so, then I'll prepare MP that disabled that test for this landing [14:00] and will continue debugging [14:03] jibel: note, you can skip the autopkgtest-- I forgot to update it for the new policygroup so there is a failure on the unexpected 'keep-display-on' policy group. that doesn't affect the functionality in the package in any way (and I am staging the fix for that now for next time) [14:11] sil2100, hey, I think I need to sort out the issue with silo 42 mentioned above, it has critical fix affecting battery ^ [14:18] Laney: qtubuntu-android qtubuntu-desktop depends on qtubuntu-sensors and they have the ubuntu-application-api3-touch(desktop) dependency [14:27] pmcgowan, is there anything else on the "need sign-off" queue that must land this week? It's a bit late to land 36 [14:28] jibel, 36 and the device tarball that goes with it, sorry for the last min as usual [14:28] davmor2, ^ can you do it? [14:28] jibel, the apparmor change [14:28] you know about [14:29] pmcgowan, rvr is on the apparmor change [14:29] device tarball won't arrive till first thign tomorrow from asia [14:29] pstolowski, yeah, that build issue is a migration blocker [14:30] jibel, and silo 53 is that landing? [14:30] pmcgowan: not another tarball I only signed one off this morning ;) [14:30] job security [14:30] popey: camera uploaed [14:30] popey: mind approving it in store? [14:30] jibel: I can do it once I finish this browser one maybe 30-60 minutes [14:31] seb128, in that case I'm disabling the test for now and will rebuild the silo. this will not require any re-testing from qa [14:31] jibel, ^ [14:31] pstolowski, k [14:31] jgdx, pete-woods how is silo 53? [14:31] sil2100: Oh, I told Robert about this last night, but you'd left by then. Translations are being correctly uploaded to ubuntu-rtm/15.04 for copies to stable-phone-overlay now. However, we thought of a detail we need to sort out (ensuring Packaging records so that message sharing works) before we can turn on import queue processing and permit translations. I'm working on that. [14:31] pmcgowan: ^- FYI [14:32] pmcgowan, we cannot start regression tests tomorrow otherwise we won't make it on time. And silo 36 touches core components [14:32] pmcgowan: I've tested it, and it seems to work [14:32] cjwatson, ack [14:33] jibel, will we also wait for the crashes to be fixed? that ogra_ mentioned above [14:33] pmcgowan, it is hard to tell what impact (beyond boot time) they have [14:35] pmcgowan, davmor2 is currently the only one (the chosen one) able to test this properly AFAIK [14:35] pmcgowan, re: silo 53 [14:35] jgdx: oh not more peap stuff [14:35] oh yes indeed [14:36] so 36 and 53 seem the last to land [14:37] jibel: I can probably test both, but I assume the preference now will be 53 I assume right? [14:37] and 35 fixes a regression I see [14:38] 35 will land soon [14:38] pmcgowan: testing 35 now [14:39] jibel, 39 is the only other one to consider [14:41] sure bfiller [14:43] bfiller: done [14:43] popey: thanks [14:44] jdstrand: I need a test app for silo 17 [14:46] mzanetti, do you have an app for rvr? [14:47] pmcgowan, rvr, one sec. I'll update the one from yesterday to not be unconfined, but use the apparmor permission we need to test this [14:47] mzanetti: Thanks [14:53] rvr, http://notyetthere.org/data/untitled5.mzanetti_0.2_all.click [14:53] rvr, this uses the "keep-display-on" policy as said in the bug. I didn't test it on the silo to [14:54] rvr: I put one in the bug [14:55] mzanetti, could you split 36 and build a silo with only GU related changes? [14:55] pmcgowan, ^ [14:55] I see mzanetti also has one [14:55] jibel, reason? [14:55] jibel, yes I can do.. but obviously requires a rebuild etc [14:56] jdstrand: Ahh... test-keep-display-on.jdstrand_0.1_all.click [14:56] mzanetti, what else is in there [14:56] jdstrand: I'll check it too [14:56] pmcgowan, some test improvements that I had in there earlier already [14:56] but sure, I can drop them, no prob [14:56] rvr: ok-- but it is just mzaneeti's qml file :) [14:56] mzanetti's* [14:57] mzanetti, jibel just trying to avoid risk [14:57] I understand. ok. rebuilding then, ok? [14:57] jibel, ^ [14:58] mzanetti, yes [14:59] that line seems a bug btw ^ (I've set it from yes to no) === chihchun is now known as chihchun_afk [15:20] trainguards: can silo 35 be published, please? [15:29] pmcgowan, do we promote OTA candidate images to flash-able channel? [15:30] if not, I guess rc-proposed would be sufficient... [15:39] awe, not sure I follow, yes its rc-proposed [15:39] awe, there is an rc channel actually but nt really used for that [15:39] yea, after some thought, it was a dumb question [15:39] ;)- [15:42] pmcgowan: is there a known issue with installing apps from the store? seems to not be working for me on latest image [15:43] get error "Download or install failed. Please try again." [15:45] bfiller, not that I am aware of [15:46] bfiller, oh my [15:46] failed here as well [15:46] busted [15:46] maybe something with the 2-factor auth? [15:46] store or image is the question [15:46] jibel, ^^ [15:48] bfiller, checking with martin as I bet you are right [15:49] jdstrand: jibel: Silo 17 looks good [15:50] pmcgowan, bfiller fails here too [15:51] bfiller, I've this in the logs of scope-registry: Error received from UDM during startDownload: Network Error === espy is now known as awe [15:54] bfiller, jibel I am told prodstack went down so downloads busted [15:55] pmcgowan: ok, thanks [15:55] pmcgowan, thanks [15:59] jibel: fyi, re silo 17, I haven't been able to complete the image/unprivileged/apparmor-easyprof-ubuntu because it is a long running test and something is stopping adb and killing the test. I'm bringing up an alternate device to test on. If rvr was able to complete the test run, I don't think you need to wait on me [15:59] jibel: let me rephrase, I am using 'adb shell ...' and something unrelated to the test is breaking the connection [16:00] which of course makes the test not complete. but, like I said, I am now trying on a different device [16:01] jdstrand: I was able to verify that the new feature works fine [16:02] yes, I was able to do that [16:02] I was referring to the test plan [16:06] jdstrand: The manual tests are ok. [16:06] cool [16:07] I'm highly confident in this upload between what you've done and the test plan I was able to complete (and like I said, trying to complete that test on a different device that doesn't break the adb connection) [16:08] prodstack> One PS4 compute node went down [16:15] meh, the adb connection keeps breaking [16:15] * jdstrand tries on emulator [16:21] bfiller, jibel store is back up [16:22] oSoMoN: was AFK, publishing now [16:29] hey trainguards o/ can i have a silo for line 86 ? === dbarth__ is now known as dbarth [16:30] sil2100, thanks! [16:31] On it [16:33] trainguards: is it possible to publish a dual silo to wily only? [16:34] oSoMoN: it is, basically I just have to delete the vivid packages [16:34] robru, ok, I’ll want to publish silo 8 to wily only tomorrow (still need to validate it a bit more) [16:35]