/srv/irclogs.ubuntu.com/2014/10/28/#ubuntu-ci-eng.txt

ribrubfiller: messaging-app conflicts with rtm2600:08
bfillerribru: rtm26 safe to ignore for now as that won't land in 10/30 image00:09
ribrubfiller: ok cool00:09
ribrubfiller: you got rtm 400:09
bfillerribru: thanks00:09
ribrubfiller: you're welcome00:13
ribrubfiller: rtm 9 ;-)00:15
bfillerribru: awesome00:15
infinityribru: Curious.  So, I have literally zero insight into how it's being used in the CI infrastructure.01:11
infinityribru: I can tell you that it's harmless for it to fail to load, but no idea without access to all the moving parts to tell you how it's broken or how to fix it.01:11
ribruinfinity: well I can't speak for all of CI, but within ci train / lp:cupstream2distro, this is the only file that references it: http://bazaar.launchpad.net/+branch/cupstream2distro/view/head:/chroot-tools/.pbuilderrc01:12
ribruinfinity: barry mentioned he was also bit by this eatmydata issue, so it seems like eatmydata is just broken for all of vivid as far as I can tell. that config works fine as-is for trusty and utopic. and I confirmed the package is installed and file present in vivid. so there's something else going on causing it to fail to load01:13
infinityribru: Well, there has been a pretty massive version bump (26 to 82) between utopic and vivid, so it's possible calling conventions changed or something.01:14
ribruhrm01:14
infinityhttp://bazaar.launchpad.net/+branch/cupstream2distro/view/head:/chroot-tools/.pbuilderrc01:15
infinityOr that.01:15
infinityErr.01:15
infinity    + debian/rules: move shared library to /usr/lib/<triplet>/libeatmydata.01:15
infinityThat.01:15
ribruhrm01:16
ribruinfinity: https://wiki.ubuntu.com/PbuilderHowto#eatmydata not sure why I didn't think to google this earlier ;-)01:16
ribrubarry:  ^^ ;-)01:16
infinitySo you probably want something like export LD_PRELOAD="${LD_PRELOAD:+$LD_PRELOAD:}/usr/lib/$(dpkg-architecture -a$ARCH -qDEB_HOST_MULTIARCH)/libeatmydata/libeatmydata.so"01:18
infinityBut only for vivid+01:19
ribruinfinity: -a$ARCH?01:19
infinityAlso, oh god, why do we still have pbuilder in our infrastructure, it burns, make it stop.01:19
infinityribru: It seems that script has $ARCH as the target dpkg arch.01:20
ribruinfinity: lol. too many other fires to put out before that one. but all of ci train / jenkins /etc is going away Real Soon Now, so let's cross our fingers that the new uci-engine isn't using it01:20
ribruah01:20
ribruinfinity: what's the easiest way to conditionalize "if vivid: foo; else: bar" in this case01:21
ribruor query the version of eatmydata installed..01:21
infinityribru: You have $DIST, you can test.  Simlper to test for older dists, though with all this having a short life (in theory), it makes little difference.01:21
ribruinfinity: slippery slope though, don't want to be sloppy just in case it sticks around too much longer ;-)01:22
infinityribru: But I'd use a case.01:22
ribruinfinity: is pbuilderrc just a shell script? it seems to be calling mkdir but other than that I'm not sure if it has full shell support to do whatever01:23
infinityribru: Looks like shell to me.01:23
infinityribru: case $DIST in\n  precise|trusty|utopic) do_old_way;;\n  *) do_new_way;;\nesac01:24
ribruinfinity: there's no easy way to do version number matching with apt-cache or something right?01:25
infinityribru: You're not in the chroot at that point, so no.01:25
ribrucrap01:25
ribruno wait01:25
infinityribru: And, if the chroots are tarballs (which it looks like), you can't even look in them yet.01:25
ribruinfinity: but it just calls lsb_release to populate $DIST, that must mean it's inside the chroot, doesn't it?01:25
ribruotherwise $DIST would just be the $DIST of the host system01:26
infinityribru: No, it's not actually using that.01:26
infinityribru: Those lines populate the variables to the host system's setup if you don't feed it better defaults, which you obviously do.01:26
ribruhmmmm01:26
ribruok01:27
ribruinfinity: can I trouble you for a quick review? https://code.launchpad.net/~robru/cupstream2distro/fix-eatmydata/+merge/23978201:32
ribrubfiller: rtm 12 ;-)01:39
bfillerribru: nice01:39
ribruinfinity: https://ci-train.ubuntu.com/job/upgrade-chroot/114/console well I pushed that branch into production and it seems to be not working. Hrm01:40
ribruno qa?01:43
ribruthat's better01:44
infinityribru: Got it all sorted out?01:48
ribruinfinity: sure didn't!01:48
ribruinfinity: tried it your way and the wiki way (which suggests relative instead of absolute path), both are still spewing like crazy in vivid01:48
infinityribru: So just make the vivid path not use the LD_PRELOAD at all, and we can revisit it later if speed is a huge issue.01:49
ribruinfinity: seems reasonable.01:49
infinityribru: Certainly not something I want to debug blind at 8pm on a day off. ;)01:49
ribruinfinity: just gonna play with a bit in a local chroot since tinkering with jenkins remotely is fiddly.01:49
ribruinfinity: haha, didn't realize it's a day off for you. regular day for me. Ok I'll try a couple things and if it fails I'll just disable it. thanks for the input01:50
imgbot=== trainguards: RTM IMAGE 133 building (started: 20141028 03:05) ===03:04
imgbot=== trainguards: RTM IMAGE 133 DONE (finished: 20141028 04:20) ===04:19
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/133.changes ===04:19
Mirvribru: thanks!05:39
Mirvribru: I'll free up 15 soonish, but I'll make a copy of it for utopic desktop users somewhere as some like using it05:41
Mirvribru: the eatmydata seems familiar and is harmless. we should just get it properly installed so that it could do its job (speed up i/o)05:46
ribruMirv: you're welcome. My latest branch disables eatmydata for vivid until a solution can be found. If you have any insight, branches welcome ;-)05:51
ribruMirv: the pbuilder howto wiki mentions a change to eatmydata in vivid and suggests and alternate configuration but i wasn't able to get it working. Preprod is useless here but feel free to tinker with it in production. lp:cupstream2distro /chroot-tools/.pbuilderrc05:55
ribruMirv: check the commits on my latest merge to see what didn't work....05:56
Mirvribru: thanks, I'll check them. I'm sure eatmydata was not a crucial part of our performance anyway, it's more of a desperate measure in case of slow hard drives etc06:02
ribruMirv: i don't have any hard metrics on the performance with out without it. Maybe we should put some timers on the build job and try building the same packages in utopic and vivid ;-)06:03
ribruMirv: you know, a million times, and average the results, like python's mtimeit ;-)06:04
Mirvit could help a bit in the packages unpacking part which is quite i/o bound06:07
* Mirv converts utopic silos to vivid07:26
* ogra_ tries to decypher ribru's mail ... 08:28
sil2100hmmm08:59
ogra_i guess we want tvoss around before touching anything09:00
Mirvhmmmm09:02
ogra_though looking at https://launchpadlibrarian.net/188458283/buildlog_ubuntu-vivid-amd64.location-service_2.1%2B15.04.20141027.1-0ubuntu1_FAILEDTOBUILD.txt.gz this is a clear test failure, not sure how it wouold related to mis-merging09:03
ogra_*would relate09:03
Mirvsil2100: so, after robru accepted my yesterday's cu2d branch and did some additional fixes, I've changed most utopic silos to be now vivid09:09
Mirvalso, first vivid publish done09:10
ogra_sigh09:16
ogra_apport right after OTA to 133 ... my UI hangs09:16
ogra_and kills the session09:16
* ogra_ sees a fresh unity8 crash file 09:17
sil2100ogra_: yeah, anyway I would indeed wait for tvoss, not sure if he'll be around today though09:21
sil2100Mirv: \o/09:21
dbarthgood morning, is vivid available for mako currently?09:25
dbarth--channel=ubuntu-touch/vivid gives me an error like09:25
dbarthFailed to locate latest image information09:26
ogra_dbarth, that would mean we have promoted something :)09:27
ogra_you would want vivid-proposed ... (but you should simply not use versioned channels, so devel-proposed) ...09:27
sil2100Would be nice to find some cycles to promote a devel channel image anyway, at least sometimes in the nearest future09:27
ogra_there were no successful image builds yet09:28
dbarthogra_: ok, makes sense; i should have known better... ;)09:29
dbarthhmm, but vivid-proposed says the same09:29
sil2100Not sure if we build vivid images yet09:30
sil2100ogra_: right?09:30
dbarthah09:31
ogra_sil2100, i saw one failed attempt09:31
dbarthso i can still stack my brand new vivid silo on top of my utopic image?09:31
ogra_havent checked deeper yet, i was waiting til desktop images build09:31
pstolowskitrainguards, Mirv I've fixed the URL in line #5709:33
Mirvdbarth: essentially yes, but you need to add the silo url manually since apt-add-repository would add it as "utopic" to sources.list09:34
dbarthah ok np09:35
dbarthwe're really on the edge with vivid today ;)09:35
popey\o/ browser locked up09:35
sil2100psivaa_: hey!09:42
pstolowskitrainguards hey, can i get a silo for line #57?09:52
Mirvpstolowski: sure, we just have a meeting ongoing09:56
popeydavmor2: quick, make a webapp from that!10:08
sil2100Wompwompwomp10:08
davmor2popey: not a bad idea I'll look into it after10:09
Mirvwith not one but two Qt silos it looks like I'm breaking up the usability of http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q= a bit :( so much scroll, no fun.10:10
MirvI'll free up the utopic once I've vivid up to speed and have made backup of the utopic to somewhere10:10
sil2100Much scroll? Very big10:10
sil2100Wow wow10:10
sil2100;)10:10
Mirvexactly!10:11
ogra_W: Failure trying to run: chroot /build/chroot mount -t proc proc /proc10:16
ogra_W: See /build/chroot/debootstrap/debootstrap.log for details10:16
ogra_P: Begin unmounting filesystems...10:16
ogra_sil2100, ^^^^ thats the armhf image build failure10:16
ogra_fails very early on ... when greating the first chroot10:17
ogra_*creating10:17
sil2100hm, doesn't make much sense, why is that failing?10:20
sil2100We need someone from the elders to check that out10:21
ogra_thats just fallout, most likely some packages couldnt be unpacked, sadly you cant see that bit10:21
sil2100(a reference to the presentation from Alexander last week)10:21
ogra_debootstrap isnt very verbose10:21
ogra_yeah10:21
ogra_i pinged adam about it10:21
ogra_i'll try a deboostrap myself here10:22
sil2100debootstrap for vivid worked fine on i386 (or amd64?) on the citrain jenkins though10:22
ogra_yeah, it does10:22
ogra_it does also for thex86 images10:22
ogra_(for touch)10:23
ogra_ubuntu-core fails the same way10:24
ogra_https://launchpadlibrarian.net/188476083/buildlog_ubuntu_vivid_armhf_ubuntu-core_FAILEDTOBUILD.txt.gz10:24
ogra_for all arm builds https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-core/10:25
ogra_so i guess infinity is aware already10:25
sil2100btw. I really hate car mechanics, gave them my car before flying off to Washington and they had a week to finish some maintenance10:51
sil2100They were even saying it might be done earlier10:51
* ogra_ did the same with his coffee machie 10:51
ogra_got it back yesterday :)10:51
sil2100But it seems that they will only be done on Thu, so I'm stuck without a car for 2 more days :o10:52
sil2100heh ;)10:52
ogra_well, at least you will be able to get to work ...10:52
brendandsil2100, coffee is way more important than driving though10:52
ogra_++10:52
* brendand will try rolling back the image to see if messaging_app AP tests stop crashing10:53
sil2100ogra_: btw. poked on #ubuntu-unity regarding hud, but best indeed if we wait for Saviq to be back10:54
ogra_right, or mzanetti10:54
brendandogra_, what image had the hud removal?10:55
sil2100cihelp: hey! We would need someone from CI to help us out with smoketesting dashboard results - is anyone available for that today?10:55
ogra_brendand, 12610:55
brendandogra_, oh that long ago. hmm10:56
ogra_yeah10:56
ogra_brendand, well, that was friday10:56
ogra_(or rather even sat. ... it was dropped on fri. image built on sat.)10:57
popeyMirv: could you please upload calendar to store http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.calendar_0.4.531_all.click11:00
Mirvsil2100: I hate car mechanics too, that's why I drive 50+km and travel back with public transport when my car requires service, just because I've finally found one place that actually treats customers well11:01
Mirvor if it's a one day job, I work from a nearby cafe and simply drive back at eod11:01
sil2100Mirv: lucky! I mean, I would be willing to do that as well, but the car mechanics that are just like 100m from my apartment were normally timely11:05
ogra_sil2100, oh ... can we actually turn line 61 into "landed" state somehow ?11:05
sil2100ogra_: looking11:05
ogra_(hud removal ... )11:05
sil2100Sure, doing11:06
sil2100Done11:06
ogra_thx11:07
brendandogra_, i flashed 128. i guess if the messaging tests do well here then we can rule out the hud removal. let's see11:08
ogra_hmm11:09
ogra_i actually wonder if the framework itself specifies the hud somewhere11:09
brendandalthough it looks like it's already crashed11:09
brendand:/11:09
brendandbefore i even got to run them11:09
ogra_or unity-voice-service11:09
ogra_(without haveing a dependency)11:10
brendandogra_, it takes a really long time to restart unity8 too11:12
ogra_sometimes, yeah11:12
* ogra_ has seen that here too11:12
Mirvpopey: calendar uploaded11:23
popeythanks11:23
brendandogra_, we should probably all be collecting stack traces when we have these crashes11:27
ogra_brendand, well, mine seem to all be uploaded to e.u.c11:28
ogra_https://errors.ubuntu.com/?package=unity8&period=day11:29
ogra_hmm11:29
brendandogra_, shit - look at thursday/friday11:29
brendandogra_, although perhaps that's just the effect of the release11:30
ogra_hmm, so this is better https://errors.ubuntu.com/?package=unity8&period=week&pkg_arch=armhf11:31
brendandogra_, 128 seems to be a lot more stable and that was after the hud removal11:32
* ogra_ wonders where ubuntu-rtm errors actually go 11:32
ogra_there is no way to look them up on errors.u.c it seems11:33
brendandogra_, yeah they all seem to be from utopic11:34
ogra_right, which doesnt have the most recent unity811:34
ogra_ev, do we have errors.u.c for ubuntu-rtm somewhere ?11:35
ogra_now that we land in vivid the utopic data doesnt help much anymore (as the vivid data wont since everything moved on)11:35
asacunity is again spinning the spinner and doedsnt come back11:37
ogra_asac, see above ... thats what we are researching11:38
asacok cool any info?11:38
ogra_sadly all our info sources dont really help much ... pointing to utopic or vivid11:38
ogra_utopic is to old, vivid has moved on beyond whats in 14.0911:39
asacand?11:39
asaci dont see how that prevents us from figurinng this11:39
ogra_that measn we cant get proper info from errors.u.c11:39
ogra_beyond that brendand is going back through the images atm11:39
asaci thought that we fixed that11:39
ogra_if we did i wouldnt know how to get that info summary11:40
asace.g. we have the right symbols on retracers for derived distro11:40
ogra_do you ?11:40
asacyes11:40
* asac asks pitti in -touch11:40
popeyMirv: also, please upload sudoku. http://s-jenkins.ubuntu-ci:8080/job/sudoku-app-click/lastSuccessfulBuild/artifact/generic-click-builder-utopic-armhf/output/com.ubuntu.sudoku_1.1.312_all.click11:47
asacogra_: sil2100: https://errors.ubuntu.com/bucket/?id=/usr/bin/unity8%3A6%3A__assert_fail_base%3A__GI___assert_fail%3A__GI___pthread_mutex_lock%3A__gthread_mutex_lock%3Astd%3A%3Amutex%3A%3Alock11:48
asactahts the unity crash ogra is seeing11:48
asacbrendand: ^11:48
asacif thats our crash, thats the starting point11:48
asacstarted on oct 10 on RTM11:48
asacwhat landed on oct 9/10 ?11:48
asac:)11:48
satorisMirv: any idea why line 41 has been given up on and if there is something we need to do to get it back on track?11:49
ogra_asac, depends :) image 94,95 and 96 were built in that timeframe http://people.canonical.com/~ogra/touch-image-stats/rtm/11:50
ogra_94 had an ubuntu-app-launch11:50
brendandasac, but that would have been in the bq image then11:50
brendandasac, there's no way we wouldn't have noticed when qa-ing it11:50
ogra_95 a new UITK11:50
asacpulse11:50
asac:)11:50
asacwe have a playback crash here11:51
ogra_and 96 a new unity811:51
asacogra_: so maybe its indeed OOM because you have soooo many albums?11:51
* ogra_ wonders if thats a red herring 11:51
brendandogra_, i feel like it is11:51
asacgood11:51
asaci got a new unity one11:51
ogra_the "feelable" crashyness only started end of last week11:51
asacthat really tears down everything here11:52
ogra_yeah11:52
ogra_i have that on nearly every reboot11:52
asachttps://errors.ubuntu.com/oops/47162672-5e98-11e4-a34f-fa163e22e46711:52
asacthats mine11:52
asacfrom just now11:52
brendandogra_, only 10 crashes since two weeks doesn't stack up if that's the one crash11:52
ogra_brendand, did you try something pre 126 yet ?11:52
ogra_right11:52
asacig guess thhat might have to get processed first11:52
brendandogra_, no. 128 seemed more stable though. but still not totally stable11:53
ogra_right11:53
ogra_i remember at the airport 128 was rather stable for me while it constantly crashed for davmor211:53
brendandogra_, i'll try pre 126 next11:53
brendandogra_, yeah but davmor2 is special :)11:54
ogra_true11:54
ogra_i know that i manually rolled back the hud stuff though ... when searching for the apt issue11:54
ogra_that might have gotten me this tiny bit better stability11:55
brendandogra_, yeah the hud i think is the top culprit right now11:56
ogra_well, i guess rather unity-voice-service than the hud actually11:56
ogra_missing dep or so11:56
davmor2ogra_: please do a very careful review of sadtrombone.webapp on your phone ;)12:04
ogra_davmor2, you mean i should press the button very gentile ?12:04
ogra_whoops ...12:04
ogra_s/gentile/gentle/12:05
* ogra_ has french day today 12:05
ogra_:P12:05
davmor2ogra_: haha12:05
asacbrendand: can we have a bug for the crashes? see -touch12:10
asacunity812:10
davmor2ogra_: I wonder if it is webapp containers that is making the phone unstable?  we both seemed to get lock ups on or around the g+ app right?12:10
davmor2brendand: ^12:11
davmor2just a guess, I'm trying to find some common ground12:11
Mirvsatoris: it was to utopic, where you don't land anymore. I'll assign a vivid silo for i tnow.12:11
sil2100Anyway, it seems we're a bit low on manpower from the CI team today12:12
brendandasac, yeah will do12:12
brendandcan i point to the ci crashes in a public bug?12:12
sil2100asac: if you could subscribe landing-team-trackers to then - awesome12:12
satorisMirv: ok, thanks.12:12
asacbrendand: sure; those are public anywya, no?12:12
brendandasac, for RTM on krillin?12:13
asacbrendand: hmm. i think posting the link should be fine given that the link is protected?12:14
asacbrendand: is this only on krillin?12:14
asacbrendand: are the links for downloading protected?12:14
brendandasac, yes12:14
asacbrendand: then its fine i guess...12:15
brendandasac, only on krillin? hmm, we have no evidence to the contrary since not many people are using mako12:15
ogra_sil2100, you said at the airport there was a silo for ricmm's fix for the ~70 UITK test failures ... i dont seem to see it anywhere (nor do i see a spreadsheet entry for it)12:36
sil2100ogra_: there's a branch for it prepared, but I didn't know anything about a silo - bzoltan_ just mentioned that they have it and are planning on releasing it with the next UITK (whatever that meant)12:36
sil2100bzoltan_: ^ any news on landing the AP test failure fixes?12:37
Mirvsil2100: not yet landed https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/bug-lp1382414/+merge/23929012:47
MirvETA is most probably this week, since it was discussed last week12:48
sil2100We would really need this in before the cut-off12:51
fginthersil2100, morning13:13
fginthersil2100, did you get a response on your dashboard query from a couple hours ago?13:14
ogra_fginther, i dont think we did13:19
Mirvbregma: ^ unity 14.04 SRU made it in, running merge&clean13:29
* bregma does a happy dance13:30
fgintherogra_, sil2100, I've restarted the portion of the smoketesting that failed due to an unrecoverable device. Looking for other issues...13:32
sil2100fginther: no, didn't get any :)13:33
sil2100fginther: thanks! Do you know if plars will be around today as well?13:33
fginthersil2100, other then the lack of results, any other known issues?13:33
sil2100Oh!13:34
sil2100fginther: what about psivaa_? Do you know if he's also away?13:35
barryribru, infinity i saw the eatmydata errors when i was updating my vivid chroots.  now i don't see them.  go bother someone else you gremlins13:39
sil2100hah13:41
sil2100;)13:41
brendandogra_, 125 is definitely much more stable13:57
brendandogra_, anecdotally at least13:57
brendandogra_, did you or sil2100 get to file that bug?13:58
=== pstolowski is now known as pstolowski|lunch
sil2100brendand: not me, but 125 is the image before the hud removal14:02
sil2100http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/126.commitlog14:02
sil2100So this should be the image that worsened things14:03
brendandbfiller, hey - you've got a lot of silos queued up :)14:03
bfillerbrendand: indeed14:03
bfillerbrendand: let me know if you have any questions about testing14:04
brendandbfiller, hopefully most of them should get looked at today - do you have any preference for the order they are done in?14:04
sil2100davmor2, brendand: so currently there are only 4 silos in the sign-off queue, right?14:05
cwaynejdstrand: we should figure out when to land apparmor-easyprof-ubuntu :)14:06
bfillerbrendand: one sec, on standup14:06
bfillerbrendand: silo 6 would be great to get in first14:08
brendandbfiller, both those bugs are approved?14:11
bfillerbrendand: yes14:11
tvosssil2100, ping14:15
ogra_tvoss, !14:15
sil2100ogra_: hey, did you get any info from -release regarding those chroots?14:15
sil2100tvoss: !14:15
ogra_tvoss, everything ok ?14:15
sil2100ogra_: the armhf ones during debootstrap for armhf14:15
ogra_sil2100, seems infinity isnt up yet14:15
tvossogra_, sil2100 mostly, everyone back home14:15
ogra_cool14:15
sil2100tvoss: \o/ really glad to hear that14:15
ogra_hop its wasnt anything bad14:15
ogra_*hope14:16
ogra_tvoss, so we tried to decypher ribru's mail but kind of failed14:16
tvossogra_, rota virus, kinda dangerous for little ones as they dehydrate fast and easily14:16
ogra_uh, yeah14:16
tvossogra_, the issue is that https://code.launchpad.net/~thomas-voss/location-service/fix-gps/+merge/239411 was meant to land, and I put that MP into the silo (see spreadsheet, although the line says "given up")14:17
ogra_tvoss, especially since the build failure he refers to seems to not be related to merging but seems to be some self test where the build does not find ofono on the dbus14:17
tvossogra_, nope, one of the tests times out, the ofono not there messages are perfectly fine and handled gracefully14:18
ogra_ah ,k14:18
tvossogra_, sil2100 the MP that landed is https://code.launchpad.net/~thomas-voss/location-service/fix-gps-integration-and-allow-for-decorating-provider-names14:18
tvossogra_, sil2100 at least in the binary packages. I think someone published a silo other than rtm 614:18
ogra_tvoss, rtm 00414:19
ogra_that was long pending14:19
ogra_and landed yesterday14:19
ogra_(that was the one that missed the milestone due to QA failing a few times)14:19
tvossogra_, sil2100 so, at any rate, I would like that landing to be reverted and instead https://code.launchpad.net/~thomas-voss/location-service/fix-gps if possible at all14:23
tvossogra_, sil2100 but your call, I can just fix the test hang for AlbertA and we keep on movin14:24
tvossg14:24
ogra_tvoss, but that means reverting a critical fix from milestone 101614:24
tvossogra_, ack, so I will fix the test hang for AlbertA14:24
AlbertAtvoss: cool thanks!14:25
ogra_tvoss, well, it is your trunk :)14:26
tvossogra_, true, still unsure what happened as the respective branch wasn't merged automatically14:27
ogra_tvoss, hmm, it should have been when the silo landed indeed14:27
ogra_but thats a sil2100 question14:27
sil2100Trying to get my head around this as well14:28
tvossogra_, yeah, so something went wrong ... not sure what, though14:28
* ogra_ has only seen cu2d from far far away14:28
ogra_sil2100, the silo had lxc-android--config in it too ... i wonder if the merging choked on that (unlikely though)14:28
sil2100ogra_, tvoss: the thing is... silo 004 had a sync request of location-service14:29
ogra_yes, plus lxc-android-config14:30
sil2100ogra_, tvoss: so there was no merge related to location-service in the landing, so no wonder nothing got merged14:30
ogra_oh14:30
ogra_right14:30
sil2100Not sure how this got into utopic though then14:30
tvosssil2100, ah, interesting, but where did the binary packages come from?14:30
ogra_dput to the PPA ?14:31
sil2100tvoss: trying to figure that out, sadly it's all working on scraps of information14:31
ogra_lool, ^^^ do you knwo ?14:31
sil2100ogra_, tvoss: I would suppose it was a sync from utopic14:31
ogra_i doubt that14:31
ogra_since what landed in utopic was broken ...14:31
ogra_the issues were found on milestone day when the rtm silo was tested14:31
sil2100hm, I see 23 in vivid14:32
ogra_not before iirc14:32
sil2100So a sync from vivid that was maybe?14:32
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: fginther | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru broke 3 ribs
sil2100hmmm14:32
ogra_so it landed in utopic ... then failde QA later in rtm ... and then was stuck for a week14:33
sil2100Actually that's really strange, since CI Train logs say:14:33
sil21002014-10-23 19:19:41,929 INFO Looking at location-service as per sync request14:33
sil21002014-10-23 19:19:44,505 INFO Grab code for location-service (2.1+14.10.20141023-0ubuntu1) from utopic to the 'build' directory14:33
sil2100So I think it got synced from some silo PPA :|14:33
loolsil2100, ogra_: lxc-android-config bzr is way out of sync; that's why everybody uploads changes, either to archive ot to PPA14:33
loolwhich is what I did here14:33
ogra_lool, thats fine14:33
sil2100lool: do you remember where you synced location-service from?14:33
ogra_lool, the location-service side is what broke14:33
loolsil2100: from an ubuntu PPA14:33
ogra_lxc-android-config isnt the issue14:33
loolI mean a regular anding PPA14:33
loolso it didn't land?14:34
ogra_well, i assue something happened to fix it between 10/16 and yesterday14:34
sil2100lool: seems it didn't14:34
ogra_where did that fix come from14:34
sil2100I mean, wait14:34
loolso14:34
sil2100I guess it's landed in both distros now anyway14:34
loola) lxc-android-config package uploaded + location-service branch merged into ubuntu silo => this landed14:35
ogra_right, the question is if that is what we wanted :)14:35
sil2100So I suppose there only was the problem of the branch not being merged properly14:35
loolb) separate rtm lxc-android upload + copy of location-service into ubuntu-rtm PPA => this partially landed?14:35
ogra_lool, right ... on 10/16 the rtm equivalent failed QA14:35
loolit ended up passing QA14:35
ogra_i.e. your b) scenario14:35
ogra_lool, how ?14:35
loolit failed before the sprint14:35
ogra_there must have been a change inbetween14:36
loolwow, electricity went down here14:36
ogra_was that in a device or custom tarball ?14:36
loolbut back up14:36
* lool checks equipments brb14:36
ogra_dont lick your finger and touch power cables ! use a voltmeter instead !!14:37
ogra_:)14:37
loolok, UPS took most of the hit, rest took it fine14:37
ogra_lool, so to make it pass QA something must have been fixed14:37
loolimpressed by the microwave which has no battery but kept the time and the disher that just kept on going14:37
ogra_what/where was that14:37
ogra_device ? custom ? code change ?14:38
loolso the first time this failed, it was mostly me copying the lxc-android-config from ubutnu erroenously14:39
loolthen I'm not sure whether we did a code update or not, I think not14:39
loolvruiz tested the version which landed last week14:39
ogra_you mean yesterday14:39
loolno, that was like thursday last week14:39
loolwhere's the archive of passed qa?14:39
sil2100lool: I think the trello board has that14:39
ogra_lool, http://people.canonical.com/~ogra/touch-image-stats/rtm/131.changes14:40
ogra_thats was yesterday14:40
ogra_not sure if it sat idle over the weekend though14:40
loolwell the rtm build from yesterday shows the package being picked up14:40
loolI guess they only got published in rtm recently14:40
ogra_i remember you fixing lxc-android-config on 10/16 so QA could test14:41
ogra_but then it faild that test14:41
lool2714:41
loologra_: yes, this is what I mention above14:41
ogra_then something must have happened that now makes QA pass14:41
loolbut that's when we were trying to hit the 17th14:41
loolor 16th rather14:41
ogra_right14:41
looland we had a fix on the 17th14:42
loolbut that only started being QA-ed like wed last week14:42
loolon 22th14:42
ogra_and that landed in utopic14:42
loolQA passed 2314:42
loolno, I'm speaking of rtm14:42
ogra_well, utopic and rtm now have the same location-service14:42
ogra_so i assume you landed the fix in utopic on the 17th14:43
loollocation-service landed on 23rd in utopic and yesterday in rtm14:44
loolsorry, I dont even know what problem we're trying to solve here14:44
loolah no, it's *not* in utopic14:44
loolit's in vivid14:44
ogra_lool, just trying to do forensics to know the right thing landed where it should14:44
loolcause utopic was closing at the time14:44
sil2100Yeah14:45
looli see the fixes in rtm and in vivid; do we need them in utopic?14:45
ogra_yeah, might sit in unapproved ... if at all14:45
ogra_lool, no, we just want to be sure the right thing is in rtm14:45
loolI dont think we even tried landing in utopic14:45
loolyeah, I think we're good on that one14:46
loolmissing the startup fix now14:46
ogra_(and why the landing didnt get merged into trunk ... but i think we understood that already)14:46
ogra_(i.e. silo sync fro something that didnt land in utopic)14:46
loolright14:48
ogra_phew, so we're all fine14:48
ogra_lool, tvoss, btw, did you ever test location in a car ?14:49
tvossogra_, not me personally, but it's part of a larger test plan for the Here stuff14:49
ogra_works fine for about 5km :) then i have to restart the app to have it move along with me14:49
ogra_else the dot just gets stuck14:49
ogra_things seem to time out or so14:49
loologra_: I did in the past14:50
loologra_: actually what I've spotted last week is that whenever the screen turns off, updates stop; you have to start some location using app to have them resume14:50
ogra_i did it on a freshly bootstrapper install yesterday14:50
looleven walking14:50
loologra_: seems coherence with your experience14:50
ogra_i disabled screen blanking completely and had the phone on charger14:50
ogra_attached to the windshield14:51
ogra_it gets the fix within 1-2sec ... really nice ... just that it stops then14:51
tvossogra_, could you check that the gps provider was actually running?14:51
tvossogra_, I assume that you had a 3G data connection enabled?14:51
ogra_tvoss, hard to do while driving :)14:51
ogra_yep14:52
ogra_and the maps were properly updating when moving14:52
ogra_juust the dot wasnt anymore after some time14:52
ogra_(i could zoom and move the map with a finger and it downloaded fine, so the network was good)14:53
ogra_it looked like either trust-store timing out the permission or the provider itself timing out14:53
tvossogra_, the map was moving?14:54
tvossogra_, then you certainly had location updates14:54
ogra_i could move it14:54
ogra_it was moving while the dot moved14:54
pmcgowanI am curious, what is the real solution to keeping the screen on when navigating? Should we have a manual toggle?14:54
ogra_and when the dot stopped moving i could swipe it around and got map updates for the missing tiles14:55
tvossogra_, so if you could check prior to the drive that the location service command line actually has --provider gps::Provider, that would help me14:55
ogra_tvoss, http://paste.ubuntu.com/8720282/ ... that should be the respective logfile (as you will notice i switched to googlemaps at some point to see if it behaves any better)14:58
ogra_smells like the dbus backend vanishes somehow14:59
tvossogra_, hmmm, that's interesting. Did you reopen the page?15:00
tvossogra_, at any rate: mind filing a bug against location-service and trust-store?15:00
barryogra_, sil2100 quick sanity check on s-i 2.5.1 for rtm.  upstream tarball is ready to go so i'm prepping a source package for ubuntu-rtm only.  i don't plan on sru'ing 2.5.1 into utopic and vivid will get s-i 3.0 when that's ready.  so i want to version number the rtm package properly.  i'm thinking 2.5.1-0ubuntu1~rtm1.  that will sort higher than the last utopic/rtm of 2.5-0ubuntu1, lower than any vivid 3.0 release, but also lower than15:05
barryany 2.5.1 we might (for unforeseen reasons) want to release into vivid.  does that sound right?  also, i'm leaving it UNRELEASED in the assumption that the citrain will fill that in correctly.15:05
barryogra_, sil2100 once the source package is tested locally, i'll then create an rtm silo only and use a source package upload to the ppa instead of a merge proposal, right?15:05
ogra_tvoss, yes, as i said above, every time the dot stopped moving i needed to restart the app to have it move again ... it works for about 3-5km then sits there15:09
looltrainguards, could we land rtm silo 24 now?15:17
brendandthostr_, do you have any feedback on silos 19 and 7? they appear to have changes that didn't make the list. i asked pete-woods yesterday, he said he needed to check with you15:17
ogra_barry, hmm, why dont you just want to push to vivid and rtm in parallel ?15:18
thostr_brendand: i was out yesterday and he today... will try to clarify... should have it by tomorrow at latest15:20
ogra_pmcgowan, i dont think there is any solution yet ... as per definition an app cant request the screen to be on constantly15:20
ogra_(i had some discussion with tvoss about that before ... seems extending the timeout is possible at some point, but not permanent-on state)15:21
ogra_(in my case for ebook reader stuff though)15:21
barryogra_: i probably could, although i only wanted to land 3.0 in vivid and it'll be a little more work on my end to reconfigure my branches to do that.  if it would make the train run more smoothly, i'd be willing to do that (or at least try to)15:22
asacsil2100: when do you think will we have first vivid image popping out?15:22
ogra_barry, well, it will make switching rtm to vivid easier (which will happen in a far far future ... ) so you would have at least the last working code in vivid even if you couldnt land 3.0 yet15:23
ogra_asac, once debootsrap is able to produce armhf chroots15:23
ogra_asac, i pinged adam this morning but he seems to be out (and colin is on vac ... )15:23
ogra_the build falls over when debootstrapping15:24
sil2100asac: so, still waiting for some answers to why armhf chroots fail with debootstrap15:24
sil2100ogra_: maybe slangasek can help out?15:24
sil2100ogra_: btw. we have a bug number for the issues already?15:24
ogra_sil2100, i think adam is around now15:24
barryogra_: so, just to be clear.  you're saying, land 2.5.1 onto the ubuntu train, which will land in vivid, then sync it over to rtm, and everything will work properly, right?  iow, just use the "normal" pre-vivid process15:24
* ogra_ goes to #ubuntu-release15:24
sil2100barry: so, you want to upload s-i as a source package upload, right? Since it's not released by merges in the train, right?15:25
ogra_barry, i think thats a sil2100 question but thats how i would imagine it ... kind of ...15:25
barrysil2100: that's what i'm trying to figure out ;).  if i were to land it in vivid, then sync to rtm, i'd do a merge proposal like usual15:26
=== pstolowski|lunch is now known as pstolowski
sil2100barry: oh, so normally you release it with merges in the train?15:27
sil2100Since the version number seems different than what the train uses - you have a flag that disables the version rewrite there?15:27
barrysil2100: yep15:27
barryX-Auto-Uploader: no-rewrite-version15:28
barry 15:28
jdstrandcwayne: yes-- it is actually apparmor, click-apparmor and apparmor-easyprof-ubuntu. an additional fix was identified as needed over the weekend for the apparmor change to make any effect15:29
sil2100Ok, excellent15:30
jdstrandcwayne: so that is built in the silo and I just have to test. however, there is another bug about the date on the device being set to 2014-01-01 that you and I need to discuss, but I am heading into a meeting atm15:30
jdstrandcwayne: let's talk in a little bit15:30
barrysil2100, ogra_ okay, i'll try to board the train with the usual ticket and ping you if i have problems15:30
sil2100barry: so, let me think about that, since it's not as easy-peasy as it is in other cases15:30
barrysil2100: okay.  ping me.  in the meantime, i'll continue to test things locally15:31
sil2100barry: anyway I would try to do it like this - try to land it for vivid for now (i.e. 2.5.1) and let's then try syncing that up to ubuntu-rtm15:31
barrysil2100: ok15:32
sil2100We might do a source sync for that, but I'm afraid that CI Train would wrongly interpret the version15:32
barrythx15:32
sil2100But I'll think of something ;)15:32
barry:)15:32
sil2100barry: since when doing a CI Train source sync, it will probably try changing the version to: 2.5.1~rtm-0ubuntu115:32
sil2100barry: not sure if that's acceptable?15:32
barrysil2100: i don't care too much as long as it lands in rtm, but i don't think it's ever done that before and i've definitely done syncs from utopic->rtm15:33
sil2100barry: yeah, but when you were doing utopic->rtm syncs those were usually binary syncs15:33
barrysil2100: that is true15:34
sil2100barry: it *should* work as a binary sync right now too I guess, but more risky15:34
sil2100(since we no longer can be sure of that as in the past)15:34
sil2100Well, anyway, for now vivid, then we care about rtm ;)15:34
barrysil2100: ok.  and i still have a bit of local testing to do first before i'm ready for a silo, so if something hits you let me know.  rtm is of course the one we really care about :)15:35
barryright now15:35
Mirvlool: done. there was some sort of dashboard issue, but all seems fine when I checked manually.15:40
brendandMirv, are you going to be testing silo 22?15:41
Mirvbrendand: it's WIP still, lorn keeps on churning upstream fixes15:41
Mirvbrendand: for testing, I'll probably refer to mr. zanetti and others who have reproduced the problem (although I nowadays think I know how I see that too)15:42
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-20141028-3ca60be.changes15:44
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-testresults-20141028-3ca60be.ods15:44
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-20141028-3ca60be.tar.xz15:44
john-mcaleelysil2100, ogra_ davmor2 brendand ^ new device tarball15:45
* ogra_ checks what you broke again 15:45
john-mcaleelycan I request a qa pass at your earliest convenience15:45
john-mcaleely:-_15:45
john-mcaleely:-) eve15:45
john-mcaleelyn15:45
davmor2john-mcaleely: lalalalala not listening lalalalalala15:45
ogra_wheee dropping log noooooise \o/15:45
john-mcaleelydavmor2, tsk15:45
ogra_get that in !!!15:46
john-mcaleelyso it's fixes for alarms not always working, and cleanup performed during power management investigation15:46
john-mcaleelywhich we should get in so future investigations (!) have an easier life15:46
john-mcaleelyboth bugs are 'on the list', I believe15:46
davmor2john-mcaleely: I'll have a look after I finish this silo I'm testing15:47
john-mcaleelydavmor2, yay. sounds good15:47
john-mcaleelydavmor2, notably absent are the new modem binaries I mentioned last week. They've caused regressions, and are being re-worked15:47
sil2100davmor2, john-mcaleely: if Dave has time for it, then go for it15:49
* ogra_ just wants the logging noise gone 15:50
ogra_screw the modems, land it already :)15:50
john-mcaleelyha. never have so many been pleased by printf changes15:50
ogra_heh15:50
sil2100fginther: can you check what's up with #133 krilling test results that it's not moving forward?15:58
ogra_i thought he did above15:59
fginthersil2100, sure, it failed again (for a different reason) and I restarted it again. but I do suspect some other results to be there16:00
ogra_well, reminders is known to be wonky due to using OAuth 1.016:01
ogra_you likely want to skip that16:01
ogra_click_image_tests are also known to fail (but cwayne and mvo_ should be working on that )16:01
ogra_though the latter should make anything stuck16:02
mvo_ogra_: *cough* right - what was the url again?16:02
sil2100fginther: what was the reason for the failure this time?16:02
fgintherwasn't reminders fixed to not hang the tests?16:02
ogra_mvo_, so i looked a bit deeper ... krillin doesnt use the click_list anymore for the test16:02
fginthersil2100, unity8-autopilot could not be installed: 'Err http://derived.archive.canonical.com/ubuntu-rtm/ 14.09/main python3-junitxml all 0.6-1.1build116:03
fginther  Could not resolve 'derived.archive.canonical.com'"16:03
ogra_mvo_, seems the test calls "click list" on the device and compares it to http://people.canonical.com/~ubuntu-archive/click_packages/click_list ... which used to be our master list ... but due to the fact that we now have a custom tarball on krillin that removes clicks there and adds its own they wont match anymore16:03
fgintherit couldn't hit "derived.archive.canonical.com" at all16:03
ogra_mvo_, so i think cwayne needs to provide you a different "krillin_click_list" to match against and the test needs to use that16:04
mvo_ogra_: oh, I see. what is the url again for hte test failure?16:04
ogra_mvo_, http://dashboard.ubuntu-ci:8080/smokeng/utopic/touch_stable/krillin/132:20141027.1:20141015-32e0f27/634/click_image_tests/220717/ is the url of the last test16:04
mvo_ogra_: thanks16:04
cwaynemvo_: ogra_: i'm happy to get you a list16:05
tvossfginther, around?16:14
bdmurraysil2100: what needs to happen next with bug https://bugs.launchpad.net/ubuntu-rtm/+source/whoopsie/+bug/1339916? I see it was approved in the spreadsheet.16:15
ubot5Ubuntu bug 1339916 in whoopsie (Ubuntu RTM) "SystemIdentifier can change between reboots" [High,Triaged]16:15
loolMirv: thanks16:16
fginthertvoss, yes16:16
ogra_bdmurray, add a line to the spreadsheet for it to request an rtm silo16:17
ogra_oh, sorry16:17
* ogra_ should read sentences to the end :P 16:17
ogra_oh, other spreadsheet16:17
ogra_bdmurray, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&pli=1#gid=016:17
ogra_you want an rtm landing entry there16:17
ogra_bdmurray, once you got a silo assigned, you dput the change to the silo PPA and test it ... the rest is handled by QA and the landing team then16:18
ogra_bdmurray, note that the version needs to be on top of the last rtm package though ...16:19
* ogra_ looks that up 16:19
ogra_bdmurray, https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-October/000775.html ... you want rtm5 most likely16:19
sil2100bdmurray: yeah, so if it's approved, we need to get it to RTM through the train - is this change landed in vivid/utopic already?16:20
sil2100bdmurray: I mean, where is it landed, to vivid or to utopic?16:20
ogra_sil2100, utopic16:20
bdmurraysil2100: utopic and vivid (presumably)16:20
sil2100bdmurray: ok, then we can do a binary sync then16:21
ogra_sil2100, and then there was an lxc change on top of it which blocked us from syncing it over16:21
sil2100bdmurray: just fill in an landing entry for it an I'll fill in all the details to do a sync16:21
bdmurraysil2100: it also requires a change to lxc-android-config16:21
sil2100Ah16:21
ogra_sil2100, new lxc version and according changes ... we cant use utopic at all as base for rtm for this package anymore16:21
ogra_neither vivid i guess16:21
ogra_since that has the same packag16:22
ogra_e16:22
ogra_(and a dep on a newer lxc version)16:22
sil2100ogra_: then a sync of whoopsie and then upload a custom lxc-android-config16:22
ogra_right16:23
ogra_based on https://launchpad.net/ubuntu-rtm/14.09/+source/lxc-android-config/0.208rtm416:23
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru broke 3 ribs
brendandsil2100, did the spreadsheet get messed up?16:26
sil2100brendand: what's wrong?16:26
brendandsil2100, ubuntu-rtm/landing-004 says line 65 in its description16:27
brendandsil2100, but line 65 is definitely not that16:27
davmor2Saviq: I've just had the phone reboot/unity8/mir/lightdm/crash it's one of them anyway on the ubuntu spinning logo I'll check the crash files after, but it was on receiving the osd for google syncing contacts16:28
ogra_looks like 66 though16:28
ogra_off by one16:28
ogra_davmor2, reboot ?16:28
ogra_thats definitely a kernel or driver issue then16:28
* ogra_ has never seen that 16:29
bdmurraysil2100: I seem to only have view access so can't add a new landing entry16:29
davmor2ogra_: ubuntu spinning logo, I'm assuming reboot is the wrong term and I know how Saviq likes specifics so I covered them all :)16:29
ogra_phew ...16:30
sil2100bdmurray: oh no!16:30
sil2100Let me fix that :)16:30
ogra_davmor2, so the known issue then16:30
davmor2ogra_: yes but a fresh log/crash file for Saviq to poke hopefully :)16:31
kenvandineanyone know why 4 of the 7 powerppc builders have a status of "Manual"?16:31
ogra_i think asac collected one and me too16:31
ogra_kenvandine, probably a question for #ubuntu-release16:31
kenvandinecausing long wait times for the vivid silo builds :/16:31
ogra_but likely simply because they arent ready yet16:31
* ogra_ thinks we were a bit fast with opening this time round ... to have all bits in place in time16:32
kenvandineperhaps16:32
kenvandinebut it would be nice if all 7 were building :)16:33
ogra_(especiallly since soome arches will need some time to process all initial package builds)16:33
sil2100bdmurray: done16:34
asacsil2100: when do you think can we do v landings?16:34
asacslangasek: ^^16:34
sil2100asac: we're doing v landings already16:34
asacsil2100: when do we do first image you think?16:34
bdmurraysil2100: okay, I've added a landing entry16:35
sil2100asac: it's just that we don't have an image yet, not sure when that will be resolved though...16:35
ogra_asac, we already do them ?16:37
sil2100ogra_: I think I missed in the backlog, but do we have a bug for the chroot issue?16:37
ogra_sil2100, i dont think so, but infinity is digging, i assume it will be fixed soon16:39
ogra_obviously it isnt reproducable locally so i guess he needs to dig into the builders themselves16:40
=== bschaefer_ is now known as bschaefer
ribrubarry: are you saying you got eatmydata working without any configuration changes in vivid? wtf?17:05
barryribru: no, only that it hasn't shown up again yet.  but the day is young17:06
ribrubarry: oh ok. because I found some wiki documentation for pbuilder that suggested some changes to make eatmydata work in vivid, but they didn't seem to work for me, I tried several variations.... after a while I just gave up and disabled it in vivid.17:07
brendandogra_, did we try just rolling back the hud removal yet?17:11
ogra_brendand, did you confirm it is actually the hud ?17:11
brendandogra_, no i still have no idea17:11
ogra_(i will have to rip it out again, even if i roll back, so i want to be 100% sure)17:11
brendandogra_, well i mean did we try just installing the old version of the package - we don't actually have to revert it yet17:13
ogra_how do you mean "old version" ?17:13
ogra_it was ripped out completely17:13
ogra_just apt-get install hud17:13
ogra_that will revert the change easily ;)17:13
davmor2john-mcaleely: can you make the tarball so I can access it please it makes it so much easier to flash then ;)17:20
john-mcaleelydavmor2, oh17:20
davmor2john-mcaleely: You don't have permission to access /~jhm/barajas/device_krillin-20141028-3ca60be.tar.xz on this server.17:20
john-mcaleelydavmor2, please retry17:21
john-mcaleelydavmor2, sorry!17:21
davmor2john-mcaleely: yay ta17:21
sil2100fginther: o/17:31
sil2100davmor2: you SLACKER!17:34
davmor2sil2100: sorry I thought it was off in the afternoon, you could of pinged :P17:35
* ogra_ didnt get a calendar notification either 17:35
davmor2sil2100: I was too busy testing silos :P17:35
ogra_and ibn fact my phone calendar doesnt have the evening meeting at all anymore17:35
* ogra_ forces a calendar sync17:36
davmor2sil2100: install sadtrombone app and you can play it :P17:37
sil2100I got an e-mail reminder17:37
sil2100;p17:37
davmor2sil2100: I didn't17:38
ogra_yeah, it is obviously in my gcal17:38
sil2100davmor2: you testing the device tarball now?17:38
ogra_but not on my phone17:38
davmor2sil2100: yeap just moved onto it now I finished the silo I was on17:38
ogra_davmor2, what happened to failsauce ? i thought *that* was the recommended app for the task17:38
* john-mcaleely excitedly awaiting results17:38
john-mcaleelywell, awaiting, anyway17:39
john-mcaleely:-)17:39
davmor2ogra_: it probably is but popey said to make it so I did :)17:39
popeyit works17:39
davmor2popey: and passed all the tests17:40
ogra_heh17:40
sil2100fginther: one quick question though - do you know if the http://ci.ubuntu.com/smokeng/utopic/touch/ dashboard is configured to fetch images from devel-proposed or utopic-proposed?17:43
ogra_sil2100, check the console log of one of the tests17:45
ogra_the u-d-f command should be in there17:45
ogra_(with channel name and all)17:45
ogra_+ adb reboot bootloader17:46
ogra_+ ubuntu-device-flash --password ubuntuci --bootstrap --developer-mode --channel ubuntu-touch/devel-proposed17:46
ogra_sil2100, ^^^^17:46
sil2100Found it as well, thanks!17:47
ogra_yay, and a calendar sync got me the meeting back17:48
ogra_so i wont miss the harps tomorrow17:48
sil2100Harps for the win!17:58
ogra_++17:59
* ogra_ finally finds a minute to subscribe to vivid-changes17:59
ogra_wow ... and i already missed a ton of packages17:59
fginthersil2100, it uses devel-proposed18:01
=== alan_g is now known as alan_g|EOD
asachmm. i kinda still feel i dont get a notification for system updates18:11
asacdidnt see 133 krillin rtm by notification, but just through trying in system settingts18:12
asacChipaca: ^18:12
ogra_asac, are you sure your networking was up and working ?18:18
* ogra_ always missed them when he also had wlan issues 18:19
ogra_i did a --bootstrap today though ... we'll see how that goes18:19
asacogra_: yeah pretty, but well :)18:34
asacnext time i will monitor for new images and keep looking at state18:35
asacmonitor here18:35
ogra_you can be sure to get an image every morning when getting up usually18:35
asacogra_: so i cant rule out that temporarily the network was down, but i would anticipate that it picks it up first time it can talk tot he server again18:35
asacok lets see what the next morning brings :)18:35
ogra_if davmor2 manages to test the device tarball successfully you might even see one tonight18:35
asacok good news i guess :)18:36
ogra_finally dropping all the log spamming from the kernel18:37
ogra_silly hardcoded printfs in android kernels ...18:37
* asac hopes this will give another boost in usability :P18:37
ogra_heh18:38
* asac will do a out-of-wifi-walk-through-town scenario tomorrow morning - scheduled :P18:39
asacreally hope the image is up to that so i can find more interesting bugs than "damn, this needs restarting" :)18:40
plarssil2100: hi, sorry I was unresponsive to your email earlier, at a conference this week but I think fginther talked to you already about reminders still appearing to cause problems?18:45
ogra_asac, use location ;)18:45
plarssil2100: what's the status of the new autopilot with internal test timeout landing? iirc there needs to be a phablet-test-run change for that as well18:45
ogra_plars, system-settings is also worrying ... startsd to fail out of the blue in 12818:45
john-mcaleelythere are multiple anecdotal reports of upgrade notifications 'not working'18:46
ogra_(and constantly since)18:46
asacogra_: why?18:46
plarsogra_: has anyone tried to reproduce yet?18:46
ogra_plars, nope18:46
ogra_asac, if i knew that i would have fixed it :P18:46
sil2100plars: I think that's still not there yet18:46
sil2100plars: but from what I saw, it's not only reminders causing trouble18:47
plarsogra_: nothing has changed for us since 10/21, and that was just where the default wifi config is pointing at18:47
plarsnothing test related18:47
ogra_asac, the only thing in 128 was the apt rollback which cnat really affect system-settings18:47
sil2100plars: sometimes I saw the dashboard being stuck on some other test suite, like weather or system-settings18:47
asacogra_: shall i try downgrading something?18:47
plarssil2100: yeah, ogra_ mentioned system-settings18:47
asacunfortunately i cant even reproruce, so i could only state a gut feeling that its "maybe more stable"18:47
asacogra_: my backtrace from earlier today had media-hub in it18:48
asacthat thing landed in 126 i was told18:48
ogra_asac, i'm not even sure it is a failing tests ... looking at the console log i see system-settings running something18:48
ogra_but the dashboard disagrees18:48
asaci am talkinga bout my crash locally18:48
asacthat thing had media-hub in it18:48
asachttps://errors.ubuntu.com/oops/47162672-5e98-11e4-a34f-fa163e22e46718:48
asacbut was a bit bogus18:48
ogra_asac, kgunn is looking into that bug18:48
asacso if we also see something related to media-bug/audio etc. in the automation18:49
ogra_asac, bug 138680318:49
asaci am sure its the same18:49
ubot5bug 1386803 in unity8 (Ubuntu) "unity8 crashing a lot since image #126" [Undecided,Confirmed] https://launchpad.net/bugs/138680318:49
asacyeah18:49
asacrighgt18:49
ogra_we were focused on hud initially18:49
ogra_but seems thats not it18:49
ogra_so now the other bits get inspected18:49
asacok18:50
asaclet me know what ended up causing the issue18:50
asacjust wanted to point out that if automation has something related to audio/media-hub in trace18:50
asacits probably the same i saw locally here18:50
asacsame with different paint18:50
asacheh18:50
ogra_well, for me its always scoperunner that crashes alongside18:51
ogra_judging by the timestamps in /var/crash18:51
davmor2john-mcaleely: so the tarball looks good, I've been tailing log files as I test it and they have been fairly quite appart from some of the apps but I'm assuming that is the app rather than random data as it shuts up again after I close it :)19:10
davmor2ogra_: ^ that should make you happy19:10
ogra_\o/19:10
ogra_:)))))))19:11
ogra_:D19:11
ogra_davmor2, syslog is the only interesting one for these changes anyway19:11
ogra_kernel all goes there19:11
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: fginther | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru broke 3 ribs
davmor2ogra_: yeah I tail syslog still am infact :)  and other that apps that trigger hardware like the camera and tagger and here maps app/location it was mostly quite odd lines thrown in but nothing major19:13
ogra_awesome19:13
ogra_thats what i like19:13
* ogra_ remembers having to do all these printf fixes for the nexus7 kernel back when we did desktop images for them ... it was pure horror19:14
davmor2ogra_: hahaha19:15
john-mcaleelydavmor2, sounds good :-)19:37
john-mcaleelyogra_, so, when's a good time to publish it?19:38
john-mcaleelysil2100, ^19:38
ogra_any time is fine19:38
john-mcaleelyI'll do it now then19:38
ogra_3am UTC wouldnnt be so fine19:38
ogra_in case you planned to wait til tzhen :P19:38
bfillerribru: could you publish silo 11 on rtm please?19:38
john-mcaleelyha. is that when the daily starts, or when the custom tarball lands?19:39
davmor2ogra_: john-mcaleely is not you he goes to sleep ;)19:39
ogra_daily19:39
ogra_well, that might be true for this week actually :)19:39
john-mcaleelyaha :-)19:39
ribrubfiller: dnoe19:40
ribrudone19:40
john-mcaleelyogra_, davmor2 sil2100 new tarball published19:40
john-mcaleelythank you!19:40
bfillerribru: thanks19:40
ogra_yay, thanks19:40
ribrubfiller: you're welcome19:40
davmor2john-mcaleely: awesome19:40
pmcgowanhi guys was there an issue with the 130 image not starting properly?19:42
ribrubfiller: rtm 6 and 1419:58
bfillerthanks ribru19:59
ribrubfiller: you're welcome19:59
ogra_asac, i just got the notification here fyi20:14
* ogra_ OTAs to silent logs 20:14
ogra_et voila ...20:16
ogra_session crashed directly after SIM PIN -> PIN20:16
jdstrandfyi, rtm silo 003 but 'QA signoff needed' is marked as 'yes'. it was formerly 'no', but someone changed it I think. I was going to land it tonight (the changes are really small-- adds an apparmor rule, adds an extra option to apparmor_parser invocations in the boot script and click-apparmor, and adjusts the parser to not unconditionally regenerate the cache when providing that option)20:33
ogra_jdstrand, convince olli_ ...20:33
jdstranddavmor2: you said you'd test the custom tarball tomorrow, but you can't do that until the above ^20:33
ogra_technically every landing in rtm needs QA signoff atm20:34
jdstrandI don't really care if someone does it, there was just coordination happening20:34
jdstrandI've got to step away for a while; I'll be back later20:36
ribruugh, dashboard is missing lots of spreadsheet data but the spreadsheet seems fine, not sure why it's not picking that up. great20:38
jdstrandok, updated the comments in the spreadsheets to reference all the changes20:43
jdstrandspreadsheet*20:43
asacogra_: ack notification retrieved and processed20:59
ogra_asac, 50% of the vivid image failures are fixed ... thanks to adam ... i'll do the other half tomorrow20:59
asacogra_: debootstrap probs?21:00
asacis there a tracking bug?21:00
* asac thinks not21:00
ogra_yeah, these are fixed21:00
ogra_nope21:00
ogra_they were builder related21:01
asacogra_: what other failures do we have now?21:01
asacah, image building?21:01
ogra_yes21:01
asacor ppas etc.?21:01
asacogra_: just touch or all images?21:01
asacuknow?21:01
ogra_next bit is to find a way to make livecd-rootfs find that it is on rtm and switch some configs back and forth21:01
ogra_just touch armhf21:01
ogra_well, all armhf actually21:01
* asac impatient while unity spinner is spinning on first boot after upgrade21:01
ogra_well, it crashed immediately for me21:02
ogra_after sim pin and pin entering21:02
asachmm. did i enter the pin?21:02
ogra_asac, since we use a hardcodded /etc/passwd in touch newly added users break the build ... i need to find a way to conditionally add all the new systemd users when building o vivid21:03
asaci think the fact that i cant remember that i entered the pin means that i didnt get that far21:03
asacbut *shrug&21:03
asac-rw-r-----  1 phablet  whoopsie    11295 Oct 28 22:00 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash21:03
ogra_asac, thats "normal"21:03
ogra_non issue21:03
ogra_(recoverable error about a duplicated icon entry)21:03
asacwe won't try to fix that?21:04
asacok phone is running21:05
asaci dont see a unity crash in /var/crash though21:05
asacit just took ages and came up21:05
ogra_lucky you21:05
asacguess because of the crash file getting dumped above?21:05
ogra_yeah21:05
asacogra_: you say it will happen if i reboot?21:05
ogra_apport running21:05
ogra_asac, for me it happens always on first boto after OTA21:05
ogra_*boot21:05
asacmaybe it crashes without a .crash?21:06
ogra_nah21:06
asaci swear it took very very long to boot21:06
ogra_i have plenty of crash files21:06
asacok21:06
* asac reboots phone and sees what happens in /var/crash21:06
asacwho is working on the app scope still being empty?21:09
* ogra_ forgot who, but someone is 21:09
ogra_thostr_ perhaps ... iirc he was in the dicussion this morning21:09
pmcgowanasac, it was marcus I believe21:11
ogra_oh, right21:11
asacok pinged the bug21:12
asachttps://bugs.launchpad.net/ubuntu/+source/unity8/+bug/138203921:12
ubot5Ubuntu bug 1382039 in qtmir (Ubuntu) "[TOPBLOCKER] Apps scope empty on boot" [Critical,Triaged]21:12
asacseems the bug suggests its all on tedg :)21:13
ogra_luckily the workaround is just a down-swipe away :)21:13
asaclets see what folks say21:13
ogra_you want votes ?21:13
* tedg perks up21:13
asacdoesnt give me much sleep that there is a workaround :)21:13
asacogra_: votes for what?21:13
asacthat this needs fixing? :P21:13
ogra_<asac> lets see what folks say21:13
asacyeah, what they say who needs to do what to get this fixed21:13
ogra_i thought if tedg needs to fix it :)21:14
asachehe21:14
tedgOh, it's fixed in silo, we just need Saviq to land it :-)21:14
asacthanks. keep the bug posted on such great progress :P21:14
ogra_damn ... i was hoping i could get some bribes out of that :)21:14
asacheh21:14
* ogra_ likes that voting idea21:14
asacguess depends on how many votes you have21:15
asacthink we could give folks for flawless landings some virtual cash21:15
ogra_i vote for not moving to systemd ... just causes my first headdache in vivid21:15
asacthey could use that to vote for bugs and folks :)21:15
sil2100ogra_: \o/ good to hear about the debootstrap21:17
ogra_sil2100, well, livecd-rootfs hacks ahead21:18
ogra_its not done21:18
ogra_damn21:20
ogra_this gets really tricky ... stgrabers hardcoding of passwd|greoup|shadow in the images assumes that you have an md5sum of the original file ... which you only have after one successful build21:22
slangasekE: config/hooks/99zz-check-uid-gid.chroot failed (exit non-zero).21:24
slangasekSUCCESS!21:24
ogra_lol21:24
ogra_yeah, it likes to be ironic :)21:24
slangasekwell I'm very glad the hook did its job ;)21:24
ogra_well, i guess i could just take an utopic passwd, add the lines, generate an md5  and hope for the best ...21:25
ogra_which will then fail on /etc/group21:25
ogra_smells time consuming21:25
ogra_hmm, and we would also want it conditional ... only on vivid21:26
slangasekbut a local build will give you the full environment that triggered the failure, you can then extract both /etc/passwd and /etc/group from it21:26
* ogra_ doesnt really feel like maintaining livecd-rootfs-rtm instead 21:27
slangasekonly on vivid> don't we always use the version of livecd-rootfs corresponding to the target release?21:27
ogra_yes21:27
ogra_but we have only one trunk21:27
slangasekok, so21:27
ogra_of which we roll the packages21:27
slangasekyou're going to have to get used to that21:27
ogra_and i dont want to maintain an rtm livecd-rootfs21:27
slangasekbecause releases from trunk to 14.09 are not going to happen21:27
ogra_hmm, k21:28
slangasekhowever, as olli_ and I were just discussing, we do expect to be able to use a single source trunk for both vivid development and a "14.10-devel" branch21:28
ogra_we tried to keep it in sync in utopic vs rtm21:28
slangasekso in that case, yeah, it needs to be clever21:28
ogra_that mens it needs multiple md5's21:29
ogra_that will become fun over time :)21:29
slangasekunfortunately, yes21:30
slangasekin practice though I think you only ever need two sets at a time21:30
* ogra_ adds sqlite to the brannch to be future proof :P 21:30
slangasekone for current devel, one for previous stable21:30
ogra_yeah, thats true21:30
ogra_luckily we roll ... that means no point releases for old images21:31
slangasekexactly21:31
ogra_so i dont need to look to far back at least21:31
ogra_sil2100, you should perhaps enable the ML on https://launchpad.net/~landing-team-trackers21:46
ogra_saves you from long CC lists for such mails ;)21:46
fgintherhas anyone tried 134 yet on a krillin? the smoke test jobs all failed "phablet-network"21:46
sil2100ogra_: another ML you say? ;)21:47
ogra_fginther, runs happily here after a first boto crash of the session21:47
ogra_sil2100, well, only for announcements ... not for conversation21:47
popeyfginther: I'm on 134 here21:47
fgintherogra_, popey, thanks21:47
popeynetwork works fine21:47
ogra_fginther, if the crash happens apport kicks in ...21:47
fgintherI'll kick them again one at a time21:48
ogra_fginther, that might cause everything to behave really slow for a bit ...21:48
fgintherogra_, that makes sense21:48
sil2100ogra_: so, I wanted to G+ my landing e-mail, but it didn't appear in the archive yet22:13
sil2100Been waiting for like ages22:13
sil2100Will G+ it later22:14
sil2100o/22:14
ogra_hmm22:15
* ogra_ noticed odd behavior of the ML archive before ... 22:15
kgunntrainguards: does anyone understand the comment on line 22 wrt u-s-c in ubuntu-rtm/landing-001 ?22:57
kgunne.g. i believe it's still needed22:58
ribrukgunn: sorry otp. my guess would be that there's a new sync that will take care of that sync as well. although 'line 67' seems like a stale reference, as line numbers can jump around.22:59
ribrukgunn: altough I don't see any other landings that reference u-s-c, so unfortunatley no, i don't know what that comment is supposed to mean, or who wrote it23:16
kgunnhmm23:17
ribrukgunn: if you're confident it's still needed and there's an approved bug for it, I guess just delete that comment, sounds like a mistake.23:24

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!