[02:03] === trainguards: IMAGE 26 building (started: 20141119 02:05) === === chihchun_afk is now known as chihchun [03:28] === trainguards: IMAGE 26 DONE (finished: 20141119 03:30) === [03:28] === changelog: http://people.canonical.com/~ogra/touch-image-stats/26.changes === === chihchun is now known as chihchun_afk [05:24] morning here too [05:49] why, certainly === chihchun_afk is now known as chihchun [06:59] cihelp: need clarification on this https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/6140/console [06:59] cihelp: seems there are package conflicts there? [07:28] cihelp: ^ to zsombi's request, the error looks like if a vivid rootfs (qt 5.3.2) would try to install utopic UITK packages (compiled against qt 5.3.0) [07:46] cjwatson: infinity: around? what's the correct value to pass to 'pbuilder create --mirror _____' if I want to create an rtm chroot? [08:25] is the dashboard down? [08:26] I mean the jenkins one [08:38] Seems to work here [08:40] robru,infinity: the URL is http://derived.archive.canonical.com/ubuntu-rtm/, but that won't quite help because debootstrap doesn't understand 14.09. It's probably simplest to create a chroot with something uniformly older (say, trusty), flip sources.list over, and upgrade; or grab the chroots from Launchpad ("manage-chroot -d ubuntu-rtm -s 14.09 -a amd64 get", from lp:ubuntu-archive-tools) and use those as a starting point. [08:41] Might even be possible to do the latter directly with sbuild using Stéphane's sbuild-launchpad-chroot gadget. [08:43] Oh, FYI folks, "devel" now works in PPAs; no need to edit sources.list any more after using add-apt-repository. [09:03] jibel: hey! Do you know if the new custom tarball has been picked up for testing yesterday night? [09:03] Oh, wait, I see it did [09:03] jibel: nvm! [09:05] sil2100, it's in 165, isn't it? [09:05] Right [09:05] sil2100, we didn't test 165 yet [09:05] we'll do it this morning [09:10] cjwatson: great! for the 'devel' working. [09:19] Looking good so far, we seem to be missing only 2 topblocker fixes right now, both having fixes ready [09:20] jibel: do you have someone that could take a look at rtm silo 11? [09:28] sil2100, FYI, my testing of oxide 1.3 (in silo 3) is complete and good, dbarth is still testing webapps a bit more extensively, but it looks like we should be ready to land it soon [09:35] nice [09:39] oSoMoN: \o/ [09:50] Mirv: when you get a moment could you please upload calendar to the store (note, it's not in the rtm image so it's not covered by freezes) http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/generic-click-builder-utopic-armhf/output/com.ubuntu.calendar_0.4.549_all.click [09:51] Mirv: also sudoku pls. http://s-jenkins.ubuntu-ci:8080/job/sudoku-app-click/lastSuccessfulBuild/artifact/generic-click-builder-utopic-armhf/output/com.ubuntu.sudoku_1.1.319_all.click [09:51] john-mcaleely: ping [09:53] olli, pmcgowan: so, we're closing the landing gates now - all fixes for the listed topblockers either already landed or are in silos [09:53] olli, pmcgowan: actually, only 2 topblockers are left and both have fixes in silos === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: RTM Archive frozen (no new silos landing) ! RTM cron builds disabled [09:57] popey: calendar and sudoku uploaded [09:57] thanks Mirv [10:15] john-mcaleely: re-ping [10:15] john-mcaleely: we would need a device tarball generated from silo 11 for QA to start testing [10:17] sil2100, OH ! [10:17] sil2100, did you notice silo 13 ? [10:17] (that is the "UI freezes randomly" topblocker) [10:17] (not marked as such ... bad tedg ) [10:18] sil2100, good job! [10:18] ogra_: oh my, well - it's targetted for the next milestone anyway ;) [10:18] I wouldn't try forcefully pushing it in here [10:19] sil2100, well,if we have spare QA capacity i dont think a week more testing would be bad [10:19] sil2100, rvr will review silo 3 and rhuddie silo 11 when it's ready [10:19] it is *very* intrusive [10:19] ogra_: sil2100: I noticed [10:19] The changelog is huge [10:20] True, actually, if john-mcaleely won't pop up pretty soon we might ask for testing this silo now [10:20] yes [10:20] Since without him it might be troublesome to test 11 anyways... [10:20] Ooops, I'm talking about silo 3 [10:20] heh [10:20] rvr: ok, that's a different story ;) silo 3 is a new oxide, and that's always huuuge [10:21] sil2100: ogra_: Silo 3 contains an update to oxide, is that known? ... Ok [10:21] yes [10:21] known and wanted [10:21] Ack [10:21] (and dont dare to find any problems, rebuilding ocide will take a month at least :P ) [10:21] *oxide [10:47] sil2100, so whats left [10:56] pmcgowan, tons of new bugs with the OOBE here for me [10:56] i just hung the dash hard [10:57] and i can repro [10:57] sigh [10:57] ogra_, you mean the wizard or the new scopes stuff [10:58] new scopes [10:58] f*** [10:59] going to the bottom of "today" ... then tapping "tell me more" at the button ... in the following page scrilling completely down and tapping "finished ... " gets me a hard hang of the dash [10:59] oh, wait ... this time it doesnt ... it instead crashed the dash [11:00] WTH [11:01] the OOBE as a whole kind of trashes the whole experience IMHO ... it makes it feel very unfinished (but thats personal opinion, not a bug) [11:05] ogra_, sorry but that is just not true... [11:06] just because that is the first time you see that bug, doesnt mean is the OOBE [11:06] victorp, heh, well, thats my user impression [11:06] the way we scatter buttons everywhere [11:06] ogra_, I meant = tons of new bugs with the OOBE here for me [11:06] the way you can not easily find a way to disable it [11:06] plus the new bugs [11:06] a scope can *not* hang the dash [11:07] (fitbit doesnt work anymore, reproducable crash ... and we havent looked deeper yet, i'm sure there will be more stuff bubbling up) [11:07] victorp, well, i can reliably hang or crash it using the very bottom button on the hints page [11:08] the blue one [11:08] ogra_ ok.. let take it out, so then you can not reliably reproduce the bug! [11:08] victorp, no, lets get it fixed ... [11:09] ogra_, but you know what I mean.. the scope is just using the fw.. if it hangs is a bug in the framework that was there before [11:09] and other scopes will hit [11:09] btw, what button. I will try to reproduce [11:09] i have not seen the dash crash in a month now [11:09] and i use plenty of scopes regulary [11:10] now we have one action that makes it hang hard [11:10] ogra_, you must not be using scopes much ;P I have seen it crash a fair amount [11:10] and it is one that is very exposed in our default scope [11:10] ogra_, sure, so lets fix it [11:11] but, can you tell me how to reproduce please :) [11:11] going to the bottom of "today" ... then tapping "tell me more" at the button ... in the following page scrolling completely down and tapping "finished ... " gets me a hard hang of the dash [11:11] yeap hanging for me too [11:12] every second or third time i get a complete dash restart (showing the "scopes" splash) [11:12] interesting... [11:12] victorp, there seems to also be an issue with accounts integration ... (like ther eis none) [11:13] ogra_, ? [11:13] ogra_: I can confirm I get this hang [11:13] wait for seb128 to return ... seems fitbit ids completely gone for him [11:13] also :( [11:13] oh, wierd.. it doesnt hang on nexus4 but it hangs in krillin [11:13] i cant repro that since i dont have a fitbit account (or device) [11:14] ogra_, ok but that is not related to this bug or the changes we landed [11:14] ogra_: while you're here, had a low level question. according to /proc/cpuinfo the krillin has 1 CPU core, however it has 4 afaik. is /proc just lying to us / are we using only 1 CPU? [11:14] pete-woods, compile a kernel and look again while the compiler runs ;) [11:15] they are dynamically offlined if not in use [11:15] ogra_, what worries me is that krillin is behaving differently to n4 at scope level.. [11:15] ah, cool. that's good to know :) [11:15] victorp, yeah [11:21] ogra_, pmcgowan: does anyone of you know if john-mcaleely will be around today? [11:21] We'll have to give some other instructions to QA if not [11:21] i dont ... [11:22] let me check [11:22] sil2100, I appear to be here [11:22] yes he is [11:22] but pmcgowan should be able to shout through the office :) [11:22] Oh! [11:22] :) [11:22] sil2100, just a little late [11:22] victorp, ogra_: FYI https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1394155 [11:22] Launchpad bug 1394155 in unity-scopes-shell (Ubuntu) "Deadlock / crash of the dash possible through Today scope" [Undecided,New] [11:22] sil2100, it appears you need a device tarball for the rtm release? [11:22] pete-woods, confrimed [11:23] john-mcaleely, with a new initrd ... [11:23] john-mcaleely: ping pong then! We have silo 11 which we would need a device tarball from for krillin, with a new initrd [11:23] john-mcaleely, wehere does the krillin build pull that from ? [11:23] ogra_, and new pngs, and some changes to system-image-update, by the looks [11:23] john-mcaleely: comment says this: "Needs a device tarball for krillin, john-mcaleely will generate a new one (please ping him if not yet available when you start testing this)" [11:23] victorp: also, we have seen different behaviour on the two platforms before. I think the QML caching / preloading thing differs between them at very least [11:23] ogra_, from a private gerrit. rsalveti appears to have pushed all the merge proposals we need [11:23] perfect [11:24] pete-woods, not sure is related [11:24] thats what ii wanted to make sure :) [11:24] Got scope URI "scope://com.canonical.scopes.dashboard_dashboard?q=start" [11:24] QObject: Cannot create children for a parent that is in a different thread. [11:24] (Parent is QNetworkAccessManager(0x20ae87c), parent's thread is QThread(0x1f53500), current thread is QThread(0x20aa888) [11:24] pete-woods, ^^ [11:24] sil2100, ack. if it's ok, I'd like to be thorough here, so that might take a couple of hours [11:24] sil2100, if you want it quicker, it can be done quicker [11:24] ogra_, I'm building the first set now [11:24] victorp: I have seen that before, and have a fix. have just tried this with that fix applied and it still happens [11:24] victorp, lol ... that might be the just demoted QNetworkAccessManager bug ... we should probably push it back to topblocker [11:25] ogra_: no, it's a bug in the GeoIP code in the shell [11:25] oh, ok [11:27] john-mcaleely: how many couple of hours that would take approximately? [11:27] sil2100, (conservative eta, considering I want to do a master build first, and a test pass) 2pm UK. 2.5 hrs from now [11:28] sil2100, quickest you can have an untested (ie, rely on rsalveti's testing) device tarball: 30 mins [11:28] I would prefer we do it safe, even if it takes longer [11:28] john-mcaleely: so proceed with the standard approach, we'll simply have the promotion candidate a bit later [11:29] ogra_: and this basically means we might have time for the silo 13 [11:30] sil2100, ack [11:30] sil2100, will keep you updated === chihchun is now known as chihchun_afk [11:32] jibel: hey! I think we'll also try including the fix from silo 13 - it's a fix for a topblocker from the next milestone [11:34] sil2100, it's ready to test? [11:36] jibel: at least tedg maked it as ready for testing [11:38] sil2100, okay, we can pick 13 one until we have a new device tarball for 11 [11:39] rhuddie, since we won't be able to test 11 before 2 to 3 hours can you take 13 instead? [11:39] I suppose silo 13 needs some additional testing as the change is bigger and it's a very high-risk component [11:39] jibel: thanks! [11:40] rhuddie, then omer will join and pick 11 if you are not done with 13 [11:40] jibel, sil2100, ok, I'll look at 13 now [11:41] rhuddie: thanks :) [11:41] sil2100, john-mcaleely, we can start testing without the device tarball and later to atomic testing for only this landing i think [11:42] jibel, ^^ (about silo 11) [11:42] s/to/do/ [11:43] ogra_, anyway we cannot test 11 and 13 simultaneously. We'll start by 13 which is ready and test 11 when the tarball is available. [11:43] yeah [11:55] ogra_: later I might take a half-day sick-day, don't feel too well so I might just go lay down for a while [11:55] sil2100, thats fine, get some rest [12:08] ogra_, sil2100 so the device build passed some initial smoke tests, so I've kicked off an official build. on track so far [12:08] john-mcaleely: great news :) [12:09] john-mcaleely, awesome [12:43] bah [12:44] I had a few boots today where the apps view in the dash takes like > 10s to load the top icons [12:44] like the phone/messages/browser etc ones [12:44] slow network ? [12:44] could be I guess, but for sure those are not coming from the internet? [12:44] they get checked for new content afaik [12:45] bug 1357321 might be related [12:45] bug 1357321 in qtbase-opensource-src (Ubuntu) "QNetworkAccessManager doesn't support roaming on Ubuntu" [Critical,In progress] https://launchpad.net/bugs/1357321 [12:46] (only remotely ... though since it shows the same breakage if you switch networks ) [12:48] I saw something similar today as well, but I don't switch networks [12:48] Only one AP and only WiFi enabled [12:51] right, the bug just shows that the icons depend on networking .. thats what i wanted to point out [12:57] can someone put more coal in ci.ubuntu.com/smokeng/utopic/ ? [12:58] it's like swimming in treacle [12:59] it just wants you to stop looking at old utopic results :P [13:04] jibel: I just CCed you to the new custom tarball changelog [13:04] jibel: can you have someone from your team looking at it? It's removing some of the troublesome changes from the tarball [13:05] So it basically has only reverts [13:05] well [13:05] but not everything is reverted [13:05] which means th remainders need some special attention [13:05] (to make sure they still work even with the other bits removed) [13:06] right, so really just some exploratory testing on the aggregators specifically [13:10] Right [13:11] That's why we need QA sign-off [13:11] yep [13:12] well, we always need QA sign-off for custom :) [13:12] * cwayne1 is glad he starts working early in the morning so he could get this to QA in time [13:15] jibel: ^ :) [13:15] sil2100, yup, on it [13:16] * cwayne1 just verified the fix in 14.09-proposed-customized and 14.09.es-proposed-customized [13:17] Thank you! [13:18] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20141119-db417fa.tar.xz [13:18] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20141119-db417fa.changes [13:18] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20141119-db417fa.ods [13:19] sil2100, ogra_ jibel ^ new device tarball for rtm and also silo 11 [13:19] yay, its all rolling in :) [13:19] vivid tarball to follow in a while [13:19] rsalveti, (fyi) ^ [13:19] yeah, landed already in vivid anyway [13:19] om26er, ^^ can you take silo 11? [13:19] ogra_, not as a krillin tarball :-) [13:19] (just not krillin vivid) [13:20] :-) [13:20] :) [13:20] \o/ [13:20] Rockin'! [13:21] We're lacking QA people now actually! [13:21] ;) [13:21] heh [13:21] yup, as expected [13:21] jibel, sure. [13:22] that looks like a dangerous bug to test. [13:22] heh [13:22] om26er, it is, you're lucky. [13:22] there is some test script (or description) in the bug though [13:23] om26er: feel free to poke people if you have any problems with that one, since the bug itself is a bit 'tricky' [13:24] sil2100, don't add more topblockers to wave1 and it'll be okay :) [13:24] hah ;) [13:24] No more, we promise! But this way, we basically have no topblockers for wave2 now [13:24] So this means we can concentrate on image quality [13:25] jibel, you mean we should stop the meeting where we invent them right now ? [13:26] sil2100, heh, no topblockers for wave2? I'm pretty sure the bucket will be full again [13:26] yeah, we are good at inventing them ;) [13:28] ;) [13:29] sil2100, ogra_ How do I install the android part ? [13:29] om26er, ubuntu-device-flash has an option for that ... john-mcaleely is more familiar with this than i am [13:30] om26er, [13:30] you just need the tar,xz locally and point an option to it though [13:30] ubuntu-device-flash touch --channel ubuntu-touch/ubuntu-rtm/14.09-proposed --bootstrap --device-tarball path/to/downloaded/device_krillin-xx.tar.xz [13:30] om26er, ^ [13:31] (you can vary --channel if you need to, of course. add --revision N at the start if you need [13:31] ) [13:32] john-mcaleely, in case of silo 11 here: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-011/+packages [13:32] is android_20141117-0039.orig.tar.xz the right file ? [13:32] om26er, no [13:33] om26er, this is the file you need [13:33] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20141119-db417fa.tar.xz [13:33] for *krillin* [13:33] om26er, ^ [13:35] john-mcaleely, alright, thanks. downloading. [13:36] om26er, :-) [13:37] om26er, and ignore the PPA it only has the raw input files for this [13:37] ogra_, ok, so I don't need initramfs-tools-ubuntu-touch - 0.80 from there ? [13:38] no, thats already inside your tarball [13:38] cool. [13:40] sil2100, I flashed customized en, and there is no keyboard in the wizard to type my wifi key [13:40] bah [13:41] wasnt that fixed like three promotions ago ? [13:41] cwayne1, ^^^^ [13:41] hm, there is some weird here. cancel and select the network again and the keyboard appears [13:42] hm? that's got nothing to do with custom... [13:42] is the base image in that channel actually recent ? [13:42] it's the latest rootfs [13:42] are silos 3 and 13 intended to land today? [13:43] yeah, looks like [13:43] great [13:43] pmcgowan, yes [13:43] pmcgowan, they are. ETA for QA sign off 1 hour or so [13:43] thanks [13:43] pmcgowan, 11 too [13:44] and the custom traball rollback [13:44] ah right [13:45] ogra_, I'm reflashing, I'm wondering if it's the problem with dbus going crazy when you boot the device and it's connected. [13:45] yeah, that could be [13:45] try without cable :) [13:47] works fine on second try and without cable [13:47] pmcgowan: they're in the queue right now [13:47] silo16 would amke it go away :) [13:47] *make [13:47] pmcgowan: anyway, we now wait for silo 3, 11 and 13 to land, then we can kick the promotion candidate [13:47] but thats not due to land currently [13:47] sil2100, awesome [13:48] ogra_, btw seeing some bad dbus stuff here all week [13:48] about to file a new bug [13:48] pmcgowan, different from "eats your CPU when cable attached" ? [13:49] (that is what rtm 16 would fix) [13:49] yes, eats cpu without cable attached [13:50] ogra_, just grab some stuff, its network manager AP changes [13:51] pmcgowan: is it eating up CPU badly? [13:51] yes, this is mako [13:51] will file a bug [13:51] * ogra_ recommends mayonnaise or mustard :) [13:52] It might be the dbus-CPU issue that we know of, that tvoss is still trying to find (as it's really hard to reproduce) [13:52] right [13:52] but we also have the upower induced one ... though that onyl shows if the device is on cable [13:53] bug 1337200 is fallout of that afaik [13:53] bug 1337200 in ubuntu-system-settings (Ubuntu) "High CPU due to excessive device changed signals from upower" [High,In progress] https://launchpad.net/bugs/1337200 [13:54] rsalveti, Hi! how do I verify the fix for bug 1387214 ? I don't seem to find anything clear in the bug report. [13:54] bug 1387214 in initramfs-tools-ubuntu-touch (Ubuntu RTM) "[TOPBLOCKER] file corruption on touch images in rw portions of the filesystem" [Critical,In progress] https://launchpad.net/bugs/1387214 [13:55] om26er: added that to the spreadsheet, 1 sec [13:55] om26er: http://paste.ubuntu.com/9096495/ [13:56] rsalveti, and How do I finally check if corruption happened or not ? [13:57] om26er: after validating the image, you can reproduce by using the test script described by the bug [13:58] om26er: http://paste.ubuntu.com/9096553/ [13:58] that will start the script in a loop, let it running for a few iterations [13:59] rsalveti, do I need to run that script after each validation step or after running all the steps ? [13:59] om26er: after running all the steps [14:00] * sil2100 goes lay down for some moments [14:00] ack [14:00] ogra_: in case I oversleep, I leave you in charge of teh meeting :) Thanks! [14:00] np [14:03] rsalveti, last question: should I *not* wipe the device after the first step i.e. --bootstrap with new device tarball. ? [14:06] om26er: doesn't matter [14:29] john-mcaleely: thanks for creating the tarball [14:31] rsalveti, yw [14:50] jibel, I am finishing silo 13, no issues found === plars changed the topic of #ubuntu-ci-eng to: Need a silo? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: RTM Archive frozen (no new silos landing) ! RTM cron builds disabled [15:03] rvr, are you done with silo 3 [15:03] ? [15:04] jibel: Only one test left, 5 minutes and done [15:18] jibel: Finished [15:18] passed ? === chihchun_afk is now known as chihchun [15:29] popey: New Music app introduced untranslated strings [15:29] ogra_: Yes, passed [15:33] yay [15:33] trainguards: RTM silo 3 just got approval from QA, can we publish? [15:33] indeed [15:34] oSoMoN: sure [15:35] oSoMoN: so it was deemed that binary copy of utopic build is fine for rtm? [15:36] well sil2100 did that, so I assume yes [15:36] yup, i think that was the plan [15:36] trello looks good [15:37] Mirv, 13 is good to go as well [15:37] ok then [15:37] ogra_: 13 is approved but from earlier today has " [15:37] Blocked for this week because it's topblocker but approved for Wave 2. [15:38] Mirv, we dont mind extra enduser testing :) [15:38] not sure who put that in place [15:39] definitely not what we discussed [15:39] ogra_: rvr wrote that. [15:39] well, if it passed, let it in [15:39] then 44 mins ago rhuddie wrote that it's tested [15:40] ogra_: my understanding kind of was that wave 2 is not supposed to go in before next week or such, maybe deemed as risky and promotion wanted without first? [15:40] Mirv: Yes, I wrote that in trello this morning. But jibel told us later that it was approved for this wave. [15:40] Mirv, no [15:40] I might be wrong, but I'd like to be pointed to be wrong :) [15:40] rvr: ok then [15:40] rvr: ogra_: that part was simply not written in there. [15:40] the waves are recommendations to give the "hard" bugs more time [15:40] not mandatory ... if it is ready., let it in [15:41] point people to me iff they complain ;) [15:41] * Mirv the gatekeeper [15:41] 013 published too [15:41] cool [15:42] so we arre waiting for 11 and the custom tarball [15:44] jibel: any eta on the custom tars? ive been testing english + spanish here and looks good [15:51] rvr: oh? ahayzen ^^ [15:54] rsalveti, does the script keep on running forever ? It has rebooted for like 6 times already. [15:55] om26er: yeah [15:55] then it means it worked for 6 times [15:55] rsalveti, so how do we conclude the results ? [15:55] cwayne1, english is ok. waiting for rvr for spanish [15:56] cwayne1: jibel: Flashing the phone [15:57] om26er: let it running for at least 10 times [15:57] rvr: jibel: cool, ill wait til theyre both +1'd to push it [15:57] om26er: then just abort, which means it worked fine [15:57] om26er: without the changes I did it was breaking on the first run [15:58] popey, hmmm? strange [15:58] rsalveti, aha, then the fix is working, good. [15:58] cwayne1: #8, right? [15:59] rvr: yessir [15:59] Ack [15:59] rsalveti: that fix is for the corruption bug? [15:59] cwayne1: yes [15:59] more of a workaround for now [15:59] \o/ [16:00] rvr: can you provide more detail to ahayzen ? [16:00] or a bug [16:00] popey: I filled a bug [16:00] ...they look translatable ... http://bazaar.launchpad.net/~music-app-dev/music-app/remix/view/head:/common/SongsPage.qml#L283 http://bazaar.launchpad.net/~music-app-dev/music-app/remix/view/head:/common/SongsPage.qml#L309 [16:00] so either the pot is out of date or your language has just not been translated yet [16:01] right, so we need to get them translated and crank a new click [16:01] popey, bug 1394265 [16:01] bug 1394265 in Ubuntu Music App "Untranslated strings" [High,New] https://launchpad.net/bugs/1394265 [16:01] ahayzen: We are supposed to be in UI freeze, so no new strings :P [16:03] https://translations.launchpad.net/music-app/utopic/+pots/music-app/es/+translate?batch=10&show=all&search=shuffle [16:03] No "Shuffle" there [16:05] I see it in the .pot http://bazaar.launchpad.net/~music-app-dev/music-app/remix/view/head:/po/com.ubuntu.music.pot#L142 http://bazaar.launchpad.net/~music-app-dev/music-app/remix/view/head:/po/com.ubuntu.music.pot#L146 [16:07] ah hang on that web UI maybe incorrect as it maybe showing lp:music-app/utopic :/ [16:08] * ahayzen wonders how you switch it to the other branch [16:11] rvr, look at https://translations.launchpad.net/music-app/remix [16:12] rvr, https://translations.launchpad.net/music-app/remix/+pots/music-app/es/+translate?start=0&batch=10&show=untranslated&field.alternative_language=&field.alternative_language-empty-marker=1&old_show=all [16:18] trainguards, I can has silo for line 79 please? [16:18] ahayzen: I'll do that later [16:19] rvr, thanks i'm checking with dpm but i think i know how to make that view default now [16:27] rsalveti, you said the change affects write performance, does it also affect read performance ? [16:28] no [16:28] only write apparently [16:28]