[01:35] <kgunn> anyone around to provide some silo love ?...so we can start building for mir.
[01:36] <kgunn> maybe Mirv when you come on? ^
[02:10] <imgbot> [03:35] <imgbot> [03:36] <imgbot> [04:24] <Mirv> kgunn: assigned and kicked a build: https://ci-train.ubuntu.com/job/landing-008-1-build/83/console
[04:41] <plars> ogra_: 61 and 62 still have dbus-x11 installed it seems, so they are still going to be broken. I guess from the suggests in dbus? That's the only rdepends I can find for it that we have installed
[04:49] <Mirv> plars: I can see there's a new line for reverting the split greeter, I'm not sure if that's because this previous fix failed to work or if it's just in case it's needed
[04:49] <Mirv> plars: Suggests: does not bring a package in, Recommends would
[04:50] <Mirv> so, weird
[04:56] <Mirv> oh, right, so it's in case the dbus split wouldn't be done
[06:02] <Mirv> it does not seem that at least simply again installing dbus-x11 and removing /etc/X11/Xsession.d/75dbus_dbus-launch would make #62 show more than a black screen for me
[06:04] <Mirv> it might be of course also because of my 5.3 experiments so I could need a fresh wipe
[06:21] <Mirv> I'll assign a silo and kick a build of the revert anyhow, better to have it ready
[06:36] <ToyKeeper> Nice.  Image 62 crashed four times after flashing, before I even turned the screen on to try it...  and all the indicators are missing.
[06:39] <Mirv> interestingly, now that I upgraded my #62 + dbus-x11 - 75dbus_dbus-launch to the Qt 5.3 PPA, everything seems working correctly including indicators
[06:40] <Mirv> so maybe it was that my black screen was because of non-clean wipe (I've seen it before), but that restoring dbus-launch binary makes things work. or alternatively Qt 5.3 is simply that much better :)
[06:40] <Mirv> note that the unity8 rebuild does have the split greeter etc anyhow, everything's up-to-date.
[06:45] <ToyKeeper> This was a fresh flash.  Maybe it was a boot fluke, but it's not a good sign when the phone tries to melt itself on first boot.
[06:46] <ToyKeeper> It was getting hot enough that I worry it could cause damage...  so I shut it off completely for now.
[06:55] <ToyKeeper> Er, and one of the crashed processes was /sbin/init ... which really worries me.
[06:58] <Mirv> I seem to have /sbin/init .crash file from last Wednesday, so nothing totally new apparently
[07:10]  * sil2100 sighs
[07:17] <pete-woods> cihelp: can anyone help me figure out what happened to the packages in silo #009? https://ci-train.ubuntu.com/job/check-publication-migration/17381/console
[07:17] <pete-woods> "WARNING hud (14.04+14.04.20140528-0ubuntu1) is in no known space (and time). We didn't find it anywhere. It could have been rejected, or you run it too quickly and it's not published in proposed yet, or a network issue happened. If this persistent some time after the publication, you need to ping a landing team member to get more informations."
[07:17] <sil2100> ogra_: ok, I understand from the e-mails that the current unity8 and such are causing indicators not appearing, but I wonder why some application tests still fail completely
[07:18] <sil2100> pete-woods: I will try looking at this, wanted to do it yesterday already but there was too much chaos
[07:18] <sil2100> pete-woods: since the package is in -proposed now when ai last checked
[07:19] <sil2100> pete-woods: actually, wait, no
[07:19] <pete-woods> sil2100: that one was a failed SRU
[07:19] <sil2100> pete-woods: ok, this needs some intervention
[07:20] <pete-woods> sil2100: just let me know if I need to change anything
[07:22] <Mirv> sil2100: read the backlog from #ubuntu-touch if you didn't yet, regarding pete's landing
[07:22] <Mirv> it was probably filtered out ie never copied to archives
[07:22] <sil2100> Mirv: will do that and poke some archive admins for help here
[07:23] <Mirv> sil2100: poking was also done, so if you combine the #ci-eng and #touch discussion you should have the whole picture I think
[07:24] <Mirv> so probably you'll need to let didrocks know if you want that filter changed or something else, and then probably republish is needed
[07:25] <Mirv> sil2100: http://irclogs.ubuntu.com/2014/06/02/%23ubuntu-ci-eng.html#t10:42 + aha we don't have #ubuntu-touch logs??
[07:26] <Mirv> + http://pastebin.ubuntu.com/7578497/ then
[07:28] <sil2100> Mirv: thanks! I have this in my logs at least... but hm, why did it suddenly use the sru-staging PPA?
[07:29] <sil2100> I didn't configure it to do so
[07:29] <sil2100> I'll check the code and see what's going on
[07:32] <sil2100> Mirv: so, I'll have to chat with didrocks again, since it seems to be the default behavior so it should have done the same the first time the SRU was published
[07:33] <sil2100> Mirv: we don't have logs of that though since it was long ago
[07:34] <sil2100> Mirv: so not sure why suddenly now it would get 'filtered out'
[07:34] <Mirv> sil2100: ok, sounds good (to have a chat). I thought the abandoning of sru-staging was something you had agreed to last week or such.
[07:35] <Mirv> so I didn't have much idea what should be the case
[07:35] <sil2100> It was nothing that has been discussed with me around at least
[07:51] <ogra_> sil2100, ugh ... that looked totally different last night, 61 was mostly green
[07:53] <sil2100> ogra_: looking at 61 now it's similar though, makes me feel a bit uneasy
[07:54] <ogra_> sil2100, yeah, dropping dbus-x11 didnt help at all it seems
[07:54] <ogra_> sil2100, see the mail discussions though
[07:55] <ogra_> sil2100, it seems we need 50% of dbus-x11
[07:55] <sil2100> Yeah, saw that discussion more or less
[07:55] <ogra_> (dbus-launch, but not the Xsession.d part)
[07:56] <ogra_> and pitti seems to have a good suggestion for a fix by dropping a config option
[07:59] <sil2100> ogra_: right, I see that now - need to read up about that option though
[07:59] <sil2100> ogra_: ah, so this way the dbus session won't launch even with dbus-x11 installed?
[08:00] <Saviq> o/
[08:00] <Saviq> sil2100, can you kick https://launchpad.net/~ci-train-ppa-service/+archive/landing-019/+build/6064416 ? I hope for a flaky test - only failed on amd64
[08:01] <ogra_> sil2100, gdbus uses dbus-launch to fire up a dbus when it first tries to connect and finds one
[08:02] <ogra_> sil2100, the first gdbus call seems to happen before the Xsession script is processed
[08:02] <ogra_> this then starts another dbus-daemon
[08:06] <sil2100> Saviq: sure
[08:08] <ogra_> hmm, no answer from bfiller at all ... so we have to roll back i guess
[08:08] <ogra_> :(
[08:09] <sil2100> He'll be like in around 5 hours
[08:09] <sil2100> Which is quite long...
[08:10] <sil2100> It's really a shame though, such a big landing reverted
[08:10] <ogra_> sil2100, well, pitti just proposed a fix for which we need to roll back the dep dropping and he needs to upload a fix to dbus ...
[08:11] <sil2100> ogra_: remember on Friday when I was saying about getting ready for this big thing landing and you were like "it's nothing risky, it was in testing for months!" ;) ?
[08:11] <ogra_> but we will have the same prob as yesterday
[08:11] <Mirv> I've #62 working just fine with Qt 5.3, after installing dbus-x11 back in and removing the X related script :)
[08:11] <ogra_> needs to be tested in the lab
[08:11] <ogra_> Mirv, right
[08:11] <ogra_> Mirv, and thats what we tested with plars yesterday
[08:11] <sil2100> Right
[08:12] <ogra_> i didnt think of the fact that dbus-launch could play any role by being called directly
[08:12] <ogra_> which means we need exactly 50% of dbus-x11
[08:12] <sil2100> But what is the cause of all the current failures we have in smoketesting?
[08:13] <ogra_> but pitti agrees its a dbus bug that the Xsession part gets processed at all
[08:13] <ogra_> sil2100, that we completely dropped dbus-x11
[08:13] <ogra_> we need to keep half of it
[08:13] <sil2100> ogra_: wasn't is mentioned that 'smoketesting is fine after dropping dbus-x11' on the ML?
[08:13] <ogra_> or in other words, make the Xsession script a no-op if gdbus fired one up already
[08:14] <sil2100> Ok, so it's like, everything has one cause
[08:14] <ogra_> sil2100, yes, before i went to bed mako was all green (not all tests had run)
[08:14] <ogra_> http://paste.ubuntu.com/7578684/
[08:14] <ogra_> thats the proposed fix ... i will test that in a minute and pitti will upload it
[08:15] <sil2100> Let's wait for this to happen, the big revert silo might build itself in the meantime
[08:15] <ogra_> but we still have to make a decision if we want to risk it or complketely roll back
[08:15] <sil2100> So that we have a fallback in case of nothing helping
[08:15] <ogra_> the prob is that we tested with dbus-launch installed ... where it worked fine ... my change dropped that alongside
[08:15]  * ogra_ gets his flo and fresh coffee ...
[08:16] <sil2100> I would try risking it, really, as such a big revert is never 100% sure as well
[08:16] <ogra_> then i'll test
[08:16] <ogra_> sil2100, i agree
[08:21] <brendand> cihelp - can someone help me understand these jenkins failures? https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/1027/console
[08:23] <sil2100> pete-woods: so, I need to change something in our CI Train code to get this moving
[08:23] <sil2100> pete-woods: will try to finish it up today, but there's a lot going on
[08:23] <pete-woods> sil2100: okay, thanks for the update :)
[08:24] <vila> brendand: RO file system despite phablet-config writable-image, that's beyond my understanding, you want plars or doanac
[08:25] <vila> brendand: is this a recent failure ?
[08:26] <mandel> sil2100, I forgot the channel of the train, can you telll it to me?
[08:26] <sil2100> mandel: #ubuntu-ci-choo-choo ? :)
[08:26] <mandel> sil2100, thx!
[08:27] <mandel> sil2100, malta has drained my brain
[08:27] <brendand> vila, semi recent. a specific mr keeps failing for that reason
[08:28] <brendand> vila, since the end of last week i think
[08:29] <vila> brendand: add fginther to your ping then since it's a s-jenkins job
[08:29] <vila> brendand: they are all in US
[08:29] <brendand> vila, i'll take one more try and see if it happens again
[08:30] <popey> sil2100: ogra_ landing meeting?
[08:30] <sil2100> popey: yep
[08:31] <ogra_> yeah, sorry, still in debug mode ... on my way
[08:32]  * ogra_ cant connect ... 
[08:34] <Saviq> sil2100, ogra_, train is happy with revert silo, what do we do?
[08:34] <ogra_> Saviq, we have the landing meeting right now ... discussing that ... wanna join ?
[08:34] <sil2100> Saviq: come over, let's have a chat
[08:35] <ogra_> https://plus.google.com/hangouts/_/canonical.com/landing-meeting
[09:16] <brendand> cihelp - i have my vpn up but can't reach s-jenkins
[09:17] <ev> brendand: interesting. Having a look now
[09:17] <sil2100> brendand, ev: bfiller had a similar issue yesterday already
[09:17] <sil2100> It seems after relogging 10 times it started working...
[09:17] <brendand> ev, some people mentioned similar yesterday
[09:18] <ev> being able to reach it and being able to log in are different problems, no?
[09:19] <vila> brendand: funny you mention that, I just had to fix my laptop and desktop configs following instructions from https://wiki.canonical.com/UbuntuEngineering/CI/VPN
[09:19] <vila> brendand: I was using a config that didn't followed the updated instructions
[09:20] <brendand> vila, but i used this yesterday
[09:20] <brendand> vila, did it change in that time?
[09:20] <vila> brendand: yeah, I used mine for months
[09:20] <brendand> vila, ok i'll check the config
[09:21] <vila> brendand: I suspect that some pieces were left in place to let people update to the new (long term supported) bits so nobody realized they had to change the relevant bits
[09:21] <vila> brendand: for NM based config I had to change to 10.99.244.1 for the ubuntu-ci DNS server (I was using an old IP)
[09:22] <vila> brendand: for the openvpn based I had to stop using my hand-crafted scripts and switch to /etc/openvpn/update-resolv-conf for 'up' and 'down'
[09:22] <brendand> vila, so that seems to have done the trick
[09:23] <brendand> vila, but all i did was remove some whitespace for the up and down lines
[09:23] <brendand> vila, not even sure how the whitespace got there
[09:23] <brendand> bad copy and paste i guess
[09:24] <vila> brendand: and you did 'service openvpn restart' ?
[09:24] <brendand> vila, no i just run openvpn from the command line
[09:25] <vila> brendand: and you had a previous running but not giving you the right infos correct ?
[09:25] <brendand> vila, well yes
[09:25] <vila> brendand: so may be it was relying on some old IP that got cleaned up recently
[09:26] <brendand> vila, perhaps
[09:27] <vila> brendand: anyway, if it works now, I would keep that explanation in mind and ask retoaded for some confirming bits
[09:56] <ev> thanks vila
[09:57] <vila> ev: you didn't have any issues with your vpn I suspect ?
[10:18] <ev> not at present
[10:19] <vila> ev: right, so you probably had an up-to-date config already
[10:33] <sil2100> pete-woods: ok, let's hope that now HUD goes forward
[10:33]  * sil2100 did some hacks to push it without a rebuild
[10:35] <sil2100> pete-woods: yesss! hud re-appeared in the unapproved queue :)
[10:36] <pete-woods> sil2100: :D
[11:49]  * Mirv gone for a while, will check irc etc still today
[12:02] <sil2100> Mirv: o/
[13:08] <popey> sil2100: was there not going to be another catch up?
[13:08] <sil2100> popey: yeah, let's wait for the image first though
[13:08] <popey> k
[13:10] <pmcgowan> imgbot, stunt
[13:10]  * imgbot rolls on its back and purrs
[13:10] <ogra_> :)
[13:10] <popey> hah
[13:11] <ogra_> publisher has both packages in proposed now ...
[13:11]  * pmcgowan waits for 62
[13:11] <ogra_> next publisher run is ours
[13:11] <ogra_> then we can start a build
[13:11]  * sil2100 spams rmadison
[13:12] <ogra_> popey, i guess we wont have the image before the evening meeting ... at least not much ... and we all worked together over the last few hours anyway
[13:12] <ogra_> (in #ubuntu-devel mostly)
[13:12] <ogra_> so i dont think we need another meeting right now
[13:12] <popey> ok
[13:30]  * ogra_ is afk for a moment
[13:34]  * Mirv back
[13:40] <sil2100> ogra_: it's in!
[13:40] <sil2100> ogra_: or wait
[13:40] <sil2100> hmmm
[13:40] <sil2100> ogra_: ok, so actually rmadison says it's still in -propsoed, but citrain thinks otherwise
[13:43] <Mirv> sil2100: citrain is too fast afaik
[13:43] <sil2100> I thought that with the latest changes it should work similar to how rmadison works
[13:43] <Mirv> it requires the usual 10-15min more so that rmadison agrees
[13:44] <Mirv> ah, I don't know if it has changed recently
[13:45] <sil2100> I remember it always being accurate since some time
[13:45] <sil2100> But hm, dunno
[13:47] <pmcgowan> Mirv, all set for that webkit landing? I just wanted to be sure it got properly tested
[13:50] <Mirv> pmcgowan: oSoMoN is reviewing the webbrowser branch still (or maybe done now), I can start builds and testing as soon as traincon-0 is over.
[13:51] <oSoMoN> Mirv, webbrowser-app branch reviewed and approved
[13:52] <Mirv> oSoMoN: thanks!
[13:52] <pmcgowan> Mirv, whats the webbrowser branch for?
[13:54] <ogra_> [13:55] <sil2100> o/
[13:55] <sil2100> ogra_: thanks!
[13:55] <ogra_> bot shoulld announce it soon
[13:57] <mhr3> sil2100, reconf of 010 pls?
[13:58] <sil2100> mhr3: done
[13:59] <mhr3> ty
[13:59] <sil2100> np
[14:00] <imgbot> [14:01] <ogra_> there we go
[14:01] <ogra_> with luck we should have the first smoke results when the meeting starts
[14:03] <Mirv> pmcgowan: https://code.launchpad.net/~dbarth/webbrowser-app/webapp-container.remove-qtwebkit-support/+merge/221773 <- oSoMoN can probably elaborate (or dbarth). I'm not 100% sure if it'd be required, since we do continue to have qtwebkit (just a newer version).
[14:03] <pmcgowan> Mirv, we need some sort of test plan to validate that webkit is still working properly independent of our not using it anymore
[14:04] <pmcgowan> Mirv, we didnt include it originally for a reason, to do with bad dpr, not sure thats an issue or not
[14:05] <Mirv> pmcgowan: I think the DPR got fixed, the only issue we had with 5.2 (as we were going to ship it originally) at the end was that WebGL sites didn't work properly with it
[14:06] <Mirv> but yes, I added now a tab to create a test plan at https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjuCdq68GSyVdFI4QzNQdWpfME5aMEV2VXo0cUpOMkE#gid=23
[14:08] <pmcgowan> Mirv, thanks
[14:09] <sil2100> ogra_: as with every Tuesday, I might not be able to attend the meeting
[14:09] <ogra_> ok
[14:09] <sil2100> ogra_: but I will be back around 20 if anything
[14:09] <Mirv> dbarth: can you check ^ url (it's editable). I'd mostly want at least one line for every theoretical webkit user, and status if it's something that is needed to be retested with 5.2 or has already switched to oxide
[14:09] <ogra_> yeah, thats fine
[14:09]  * sil2100 is battling the bot
[14:09] <dbarth> Mirv: yup
[14:10] <ogra_> sil2100, since the AP tests wont be done anyway we should probably skip ... unless people feel an urge to talk
[14:10] <dbarth> Mirv: there is an additional apparmor change required to do a transparent switch though
[14:10] <ogra_> i assume we'll be somewhere in the middle
[14:10] <dbarth> trying to set that up properly
[14:13] <Mirv> thanks, it's starting to look good. I wasn't sure if OA switched, but indeed it did.
[14:47] <pmcgowan> Mirv, can you look at https://bugs.launchpad.net/qt/+bug/1318584, I cannot seem to assign it to you
[14:56] <mhr3> sil2100, could you click the rebuild button on https://launchpad.net/~ci-train-ppa-service/+archive/landing-010/+build/6065421 pls?
[14:56] <mhr3> i was too quick to build it, the ppc -api pkg wasn't published yet
[14:57] <mhr3> Mirv, or you ^?
[14:57] <sil2100> mhr3: after my meeting
[15:00] <sil2100> mhr3: click
[15:01] <mhr3> thx
[15:07] <mterry> kgunn, Saviq: how do I initiate a new silo request?  Ask here?
[15:07] <Saviq> mterry, added to the spreadsheet?
[15:07] <mterry> Saviq, no not yet, I'm new to "adding new silos to spreadsheet" -- wasn't sure of order of operations
[15:07] <Saviq> mterry, so just add your data at the end of https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=0
[15:16] <Saviq> mterry, now you want to set the "Ready" column to Yes
[15:16] <Saviq> mterry, and start begging sil2100 to get us the last silo available ;)
[15:16] <mterry> Saviq, well...  I'll have to poke tiagosh about getting the checklist right for his MP
[15:16] <mterry> If I'm going by book
[15:17] <Saviq> mterry, we'll probably have to wait until image 63 results are in, so there's time
[15:17] <sil2100> ;p
[15:17] <sil2100> I like the description!
[15:18] <Saviq> sil2100, see!
[15:19] <sil2100> Saviq, mterry: assigned! Silo 020 for you
[15:19] <Saviq> sil2100, we'll be quick, promise
[15:19] <mterry> heh, that's a bit confusing but makes sense since it was just cleared by us
[15:19] <Saviq> indeed ;)
[15:19] <mterry> Saviq, tiagosh is going to add a checklist to his merge
[15:20] <Saviq> mterry, sure, we can build in the mean time
[15:20] <Saviq> mterry, as that doesn't affect the process
[15:20] <mterry> Saviq, yup, just saying
[15:20] <Saviq> kk
[15:20] <Saviq> mterry, you pushing the button on this?
[15:21] <mterry> Saviq, the build button?  I guess the fact that landing-020 sheet has content means its configured with those 3 branches already?
[15:23] <Saviq> mterry, when sil2100 says it's ready, that's when it's ready ;)
[15:23] <sil2100> hm, should be safe to do operations
[15:23] <sil2100> But the spreadsheet is behaving strangely
[15:24] <sil2100> Could anyone of you press the build button?
[15:25] <imgbot> [15:25] <sil2100> o/
[15:26] <imgbot> [15:26] <ogra_> yippie !
[15:26] <sil2100> Image testing begiiin!
[15:26] <sil2100> \o\ /o/
[15:26] <ogra_> now the anxious waiting til the smoke infra picks it up
[15:29] <popey> updated to #63 and i have no wifi ☹
[15:30] <sil2100> Reboot
[15:30] <sil2100> Oh
[15:30] <sil2100> On the other hand
[15:30] <popey> bah
[15:30] <popey> just did
[15:31] <sil2100> My landing might have kicked us in the balls
[15:31]  * ogra_ watches the update animation idly 
[15:31] <sil2100> popey: still no internet?
[15:31] <popey> works after reboot
[15:32] <sil2100> Ah, phew
[15:32] <sil2100> Still, let's see if ogra_ will have the same
[15:32] <ogra_> wlan oon flo is fine here
[15:32] <ogra_> right after upgrade ... no extra reboot
[15:33] <ogra_> mtp also behaves
[15:33] <sil2100> Indicators present?
[15:33] <ogra_> yep
[15:33] <popey> yes
[15:33] <ogra_> all like it should here
[15:34] <sil2100> Ossum
[15:35] <ogra_> hmm, going back after adding a U1 account is weird
[15:35] <ogra_> you see system settings for s split second ... then it slides away and shows you systme settings
[15:37] <ogra_> on first sight it looks all fine
[15:37] <ogra_> so lets hope the AP tests confirm that
[15:52] <ogra_> popey, do you feel the need to have a landing meeting now ? would be only us two and i think we know what we wait for now to drop traincon-0
[15:52] <popey> i do not
[15:53] <ogra_> great, then lets skip
[15:53] <ogra_> and just watch smoke tests to chug along
[15:53] <ogra_> mediaplayer had no failures !
[15:53] <ogra_> that hasnt happened in a while
[16:04] <pmcgowan> ogra_, 63 looks better then
[16:04] <pmcgowan> nice job cross fingers
[16:04] <ogra_> pmcgowan, from a user POV it looks ok
[16:04] <pmcgowan> hah
[16:04] <pmcgowan> implying not from an engineers I suppose
[16:04] <ogra_> cant say much about the AP tests yet
[16:04] <plars> sil2100: no landing meeting?
[16:05] <ogra_> plars, we decided to skip ... all we wait for is anyway that the AP tests finish
[16:05] <ogra_> plars, to drop TRAINCON-0
[16:06] <ogra_> (i didnt know you are back today)
[16:06] <plars> ah
[16:06] <plars> ogra_: I am
[16:06] <ogra_> ok
[16:06] <plars> ogra_: fyi, I'm gone all next week though
[16:06] <ogra_> well, we hpefull have all fixes proper now
[16:06] <ogra_> so waiting for #63 to finish testing
[16:07] <ogra_> if that looks okayish we'll drop TRAINCON-0
[16:07] <ogra_> plars, why does mako look so much different while the tests are running ... i.e. the tablets both list all tests, mako seems to be missing 1/3
[16:08] <plars> ogra_: so I didn't really look into or understand the fix for this yesterday, but I do see that dbus-x11 is still installed. is that expected?
[16:08] <ogra_> it isnt installed
[16:08] <plars> ogra_: could be part haven't started yet, I'll take a look
[16:08] <plars> ogra_: it is installed, I'm looking at it right now on 63
[16:08] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/61.changes
[16:08] <plars> root@ubuntu-phablet:~# apt-cache policy dbus-x11
[16:08] <plars> dbus-x11:
[16:08] <plars>   Installed: 1.6.18-0ubuntu6
[16:09] <ogra_> i definitely dont have it on a fresh flash on 63
[16:09] <plars> that's running in the lab right now
[16:09] <ogra_> ugh
[16:09] <plars> so something is bringing it in then
[16:09] <ogra_> thats evil
[16:09] <plars> ogra_: that's what I was trying to say last night
[16:09] <popey> yeah, my #63 has it
[16:09] <plars> So I don't expect 63 to look any more green
[16:10] <ogra_> root@ubuntu-phablet:~# dpkg -l |grep dbus-x11
[16:10] <ogra_> root@ubuntu-phablet:~#
[16:10] <ogra_> root@ubuntu-phablet:~# system-image-cli -i|grep "version version"
[16:10] <ogra_> version version: 63
[16:10] <ogra_> how can you have it ... i dont get that
[16:10] <ogra_> popey, ?
[16:11] <ogra_> did you install any AP tests ?
[16:11] <popey> nope
[16:11] <popey> oh hang on
[16:11] <popey> it's possibly I'm an idiot
[16:11] <popey>   Installed: (none)
[16:11] <ogra_> PHEW !
[16:11] <popey> sorry ☻
[16:11] <plars> ah, found it
[16:11] <popey> carry on taking the pills
[16:11] <plars> messaging-app-autopilot brought it in
[16:12] <ogra_> plars, well, if that got pulled in by any AP this is super evil
[16:12] <ogra_> it will cause all sorts of dbus flakyness
[16:12] <ogra_> i hipe the autoremove at least purges it after testing ?
[16:12] <plars> ogra_: http://paste.ubuntu.com/7581296/
[16:12] <ogra_> there is a fixed dbus-x11 too, that shouldnt spawn any dbuses anymore
[16:13] <ogra_> oh
[16:13] <ogra_> ofono-phonesim
[16:13] <plars> will find out, that's the one its on now
[16:13] <ogra_> i think ofono-phonesim-autostart depends on it for whatever reason
[16:14] <ogra_> if we get dbus-x11 1.6.18-0ubuntu8  in that shouldnt be an issue anymore though
[16:14] <ogra_> but i see you are on ubuntu6 in the lab
[16:14] <ogra_> so lets cross fingers
[16:15] <ogra_> anyway, the trigger that made it start random dbus-daemons is gone so it shouldnt break
[16:15] <ogra_> we re-ordered the greeter session startup so that you have a dbus before anything  wants to talk to it
[16:15] <plars> ogra_: well, we don't apt-get update
[16:16] <ogra_> which hopefully makes dbus-x11 less harmful
[16:16] <ogra_> i dont think ubunt8 has migrated yet anyway
[16:16] <ogra_> likely still in proposed ... it has a gazillion of deps for which it runs all tests
[16:17] <ogra_> https://launchpad.net/ubuntu/utopic/+source/dbus/1.6.18-0ubuntu8
[16:17] <ogra_> hah
[16:17] <ogra_> Published 13 minutes ago
[16:17] <ogra_> bad timing
[16:18] <plars> ogra_: autoremove didn't take it out :(
[16:18] <ogra_> crap
[16:18] <ogra_> i wonder fi thats not responsible for flaky tests we saw in the past then
[16:18] <plars> ogra_: quite possibly
[16:18] <ogra_> well, messaging-app at least passed fine
[16:26] <ogra_> ARGH!
[16:26] <ogra_> dialer-app failed all tests
[16:27] <ogra_> :((((
[16:28] <robru> ogra_, also, no indicators on #62
[16:28] <ogra_> robru, 62 is dead and buried
[16:28] <ogra_> it was horribly broken
[16:29] <robru> ogra_, is there a new one? I just flashed and got 62...
 root@ubuntu-phablet:~# system-image-cli -i|grep "version version"
 version version: 63
[16:29] <robru> ogra_,
[16:30] <robru> ogra_, ha!
[16:30] <ogra_> robru, 63 is fine from locally running tests and from a few mins usage testing
[16:30] <ogra_> but it seems dbus-x11 is still causing issues in the lab
[16:33] <ogra_> sigh calendar is also failing
[16:33] <ogra_> mterry, ^^^
[16:33] <ogra_> http://ci.ubuntu.com/smokeng/utopic/touch/mako/63:20140603.1:20140530/8381/
[16:34] <ogra_> plars, for a test, can you re-run any of the failing ones after manually purging dbus-x11 again ?
[16:34] <ogra_> we definitely had them pass in local tests
[16:38] <robru> ogra_, so what happened in 63? did that have the greeter revert?
[16:38] <ogra_> nope
[16:38] <ogra_> that would have been a gigantic revert
[16:38] <ogra_> we didnt want to do that
[16:38] <ogra_> we fixed it instead
[16:38] <robru> ogra_, yeah, i don't want that either ;-)
[16:38] <robru> great
[16:38] <ogra_> apparently not enough though
[16:38] <robru> ah
[16:39] <ogra_> looking at the currently running AP tests
[16:39] <ogra_> but thats seemingly caused by a leftover dbus-x11 package that should not be on the device at all
[16:40] <plars> ogra_: sure, of course. I could do it locally right now, or I could do it in the lab after the runs are done
[16:40] <ogra_> plars, in the lab please, i want to be sure you use the same env and setup
[16:41] <ogra_> plars, we need to find a way to purge dbus-x11 though ... i dont get why teardown doesnt pull it out
[16:42] <plars> ogra_: 'sudo apt-get autoremove --purge -y messaging-app-autopilot' was what got run, I suppose maybe because it didn't follow the dep chain far enough down
[16:43] <ogra_> well, autoremove should actually follow the chain
[16:53] <ogra_> plars, could we somehow ass dbus-x11 as a permanent entry to the teardown packageset ?
[16:54] <ogra_> *add
[16:54] <plars> :)
[16:54] <ogra_> heh
[16:54] <plars> probably, let me take a look - it would be a temporary hack I guess right?
[16:54] <plars> ogra_: is it even worth it though? from what you said, in the version of dbus-x11 we pull in next it shouldn't have this problem
[16:54] <ogra_> well, we definitely dont want that package ever installed ... except for ofono-phonesim tests ...
[16:55] <ogra_> well, the new version will only make sure that the Xsession script wont run if there is already a dbus running
[16:56] <ogra_> but if you have any code that calls gdbus this will spawn a session dbus via the dbus-launch binary which dbus-x11 ships
[16:56] <ogra_> in which case you can end up with multiple dbuses again
[16:56] <ogra_> which will get you flaky tests most likely
[16:57] <ogra_> so it might or might not fix it in the lab
[16:57] <ogra_> it will fix one case we know about
[16:58] <ogra_> but there can be more ...
[16:59] <ogra_> in whicch case it is safer to always purge it
[17:03] <plars> ogra_, doanac: provided I didn't do something stupid, https://code.launchpad.net/~pwlars/ubuntu-test-cases/kill-dbus-x11/+merge/221925 ought to take care of it. Have to force that to pass in case we ever end a test where it didn't get installed, which will certainly happen
[17:04] <plars> ogra_: when I get an ack on it I'll merge it and this branch will get used to test after 63 is done. since dialer app failed I'll include it, which should also bring in dbus-x11 and we'll make sure it gets removed properly
[17:04] <ogra_> plars, looks ok to me, did you try it on a local device ...
[17:05] <ogra_> not sue about the quoting now that you have multiple packages
[17:05] <plars> not yet, about to. I just need to dig out my phone
[17:05] <plars> actually...
[17:05] <plars> I may have a better way
[17:06] <ogra_> our issue is that we need to get out of TRAINCON-0 ... so even if you can re-run the tests with purging it manually after dialer-app and messaging-app have run would help a lot
[17:06] <ogra_> we need some reliable data, things are piling up
[17:09] <plars> ogra_: we'll get there, I'm testing that branch now and once 63 finishes I'll rerun things with this
[17:09] <ogra_> awesome
[17:09] <plars> it has my full attention right now
[17:10] <ogra_> heh, thanks :)
[17:10] <plars> well, except for part of my lunch sitting on my desk here
[17:10] <ogra_> right, eat first, we dont want you to fall over starving, then we dont have anyone over there anymore :)
[17:10] <plars> ogra_: hah, you just saw me last week, I would hardly describe me as "starving" :)
[17:11] <ogra_> haha
[17:11] <ogra_> we all gained some wieght over the years
[17:11] <ogra_> a *little*
[17:51] <mterry> ogra_, sorry was out to lunch.  63 is expected to have some rough edges.  silo 020 should fix them?  (i.e. work with dbus-x11)
[17:51] <Saviq> huh, so we didn't get any improvement on 63 re: smoke testing...
[17:56] <Saviq> ah, probably because it still has unity from yesterday...
[17:56] <Saviq> or well, Friday, actually
[18:12]  * sil2100 back
[18:12] <sil2100> ogra_: do we have results?
[18:18] <josharenson> cihelp, I need a parameter added to mir-mediumtests-runner-mako
[18:18] <sil2100> ogra_: 63 doesn't look any better...
[18:19] <plars> sil2100: we're working on it, turns out dbus-x11 gets installed with some of the AP tests, but autoremove doesn't clean them
[18:19] <sil2100> phew
[18:19] <doanac> josharenson: what sort of parameter are you needing?
[18:19] <sil2100> plars: thanks! So there's still chance we might not have to revert? ;)
[18:19] <josharenson> I need "mir_performance_tests" added to the test_suite section
[18:19] <plars> sil2100: I just pushed a patch to force the removal, but trying to get complete results on mako first. I just noticed that one of the makos never installed though because it never went into fastboot. We seem to have a new problem...
[18:19] <plars> ogra_: ^
[18:20] <josharenson> ChrisGagnon and I added it last week, but it looks like it never stuck
[18:20] <plars> ogra_: sometimes when I do 'adb reboot-bootloader', it looks like it just reboots the device back into the OS
[18:20] <plars> so it never actually goes to fastboot, and it just gets stuck trying to run ubuntu-device-flash
[18:20] <doanac> josharenson: i'll have to check with fginther about that. i'm not sure the exact mechanics involved for that
[18:21] <josharenson> doanac, ok
[18:25] <fginther> josharenson, doanac, hello. I can help with that
[18:26] <plars> sil2100: I've restarted the failed ones (except gallery since we know that's a different problem) on mako, this time it should remove dbus-x11 by force
[18:26] <fginther> josharenson, it sounds like all you need is to add another test to the list of test suites?
[18:26] <josharenson> fginther, correct
[18:29] <sil2100> plars: \o/
[18:29] <sil2100> plars: thank you, you're our hero!
[18:31] <plars> sil2100: :( I much prefer to play the villain. I must work harder on this handlebar mustache
[18:31] <sil2100> hah!
[18:31] <sil2100> ;)
[18:31] <mterry> sil2100, I built silo 020, and it seemed to have worked (packages in PPA), but the status of the build job is aborted?
[18:31] <fginther> josharenson, doanac, https://code.launchpad.net/~fginther/cupstream2distro-config/mir-perf-tests/+merge/221939
[18:32] <fginther> josharenson, can you make sure that added test name is correct?
[18:32] <sil2100> mterry: hm, let me take a look
[18:32] <sil2100> huh
[18:32] <sil2100> mterry: ok, now this creeps me out - it has been aborted by 'anonymous'
[18:33] <sil2100> I don't remember we had a user like that, maybe that's some sabotage?
[18:33] <josharenson> fginther, approved MP
[18:33] <sil2100> mterry: if you re-run the build job with 'watch only' checked, it will finish what it started
[18:33] <mterry> sil2100, ok
[18:33] <sil2100> mterry: i.e. finish with success
[18:33] <sil2100> :)
[18:40] <fginther> josharenson, I'm leaving my wifi for a while. When I get back online, I'll deploy the job updates
[18:40] <ogra_> plars, where does the dash in "adb reboot-bootloader" come from ?
[18:40] <ogra_> (back btw... had some dinner)
[18:40] <josharenson> fginther, sure thing. i'm about to go to lunch, but when I get back I'll monitor new builds.
[18:41] <josharenson> fginther just ping me on irc when you deploy. Thanks for the help.
[18:41] <plars> ogra_: we have to do that in our provisioning script because ubuntu-device-flash does not
[18:41] <ogra_> plars, yes, but the command should be adb reboot bootloader without dash
[18:42] <plars> ogra_: oh? I think both might be valid. That's always worked for us
[18:42] <ogra_> hmm, i only know the no-dash version :)
[18:42] <plars> ogra_: yeah, both of them are in the help
[18:42] <ogra_> could be that maguro required a dash
[18:42] <ogra_> ah, k
[18:43] <plars> ogra_: I have one phone where the problem is pretty reproducible, let me play with it a bit
[18:44] <plars> perhaps they are slightly different and the no-dash one is better now
[18:44] <plars> nope
[18:44] <plars> still getting right back to device mode
[18:44] <ogra_> yeah, its a flag that gets handed to the kernel who hands it to the bootloader ... from there it ends up on the cmdline as value of bootreason=
[18:44] <plars> I wonder if it's just this device... I've seen other devices work just fine
[18:44] <ogra_> chekc the cmdline
[18:44] <plars> bootreason=watchdog
[18:44] <ogra_> hmm, never seen that
[18:45] <plars> ogra_: I'm starting to fear maybe this device is doing bad
[18:45] <ogra_> well, perhaps the bootloader is
[18:46] <plars> ogra_: yeah, I took this device offline for now and I'll see if it shows up on any others
[18:46] <ogra_> try re-flashing it with plain android ... also check the rest pf the cmdline and compare it with a working one
[18:46] <ogra_> androidboot.bootloader= should be interesting
[18:47] <plars> last successful flash on this phone was with 61
[18:47] <plars> so it's worked recently
[18:47] <ogra_> shoudl show you the version
[18:47] <ogra_> right, but if the last android that was flasshed had a different bootloader version that could be related
[18:48] <ogra_> so you might hit a bug with that ... we never touch bootloader or radio firmware
[18:50] <ogra_> lol .. the watchdog logs are funny ...
[18:50]  * ogra_ just looks into some 
[18:50] <ogra_> [335722.400536] Watchdog bark! Now = 335722.400519
[18:50] <ogra_> [335722.400908] Watchdog last pet at 335711.092920
[18:50] <ogra_> [335722.401116] cpu alive mask from last pet 0-3
[18:50] <ogra_> [335722.401314] Causing a watchdog bite!
[18:50] <ogra_> *woof*
[18:51] <bfiller> robru: trying to use citrain host-install 20 script and getting these errors: http://pastebin.ubuntu.com/7582208/
[18:51] <bfiller> robru: any ideas?
[18:52] <bfiller> robru: actually is that the right command? want to install silo 20 on my device
[18:52]  * sil2100 prepares some dinner
[18:53] <bfiller> nm
[18:53] <robru> bfiller, hehe, no you want device-install. or probably device-upgrade for a unity silo
[18:53]  * ogra_ goes afk for a bit again ... hopefully we have greener tests when i return :)
[18:54] <bfiller> robru: ok right, got confused because when I ran citrain-slurp it said deprecated to use citrain host-install
[18:54] <robru> bfiller, yeah... slurp and host-install are the same... ;-)
[18:54] <robru> bfiller, you would have wanted citrain-push with the old tools
[18:54] <bfiller> robru: ok got it, thanks
[18:55] <robru> bfiller, you're welcome!
[18:55] <robru> bfiller, although that error is odd anyway... it should have just installed those things on your computer, not sure why it wouldn't find the package.s
[18:58] <plars> ogra_: interesting, I'm talking to sciri now, looks like we have 3 makos that appeared to be stuck at the google screen but they were booted. All of them are behaving this way
[19:11]  * ToyKeeper wonders why apport keeps popping up and using half the CPU, with only like 10 seconds between instances.
[19:15] <sil2100> plars, ogra_, robru: so far results seem really good!
[19:17] <plars> sil2100: we haven't started to get to the interesting ones yet
[19:17] <plars> sil2100: but I suspect this will make things improve quite a bit
[19:25] <ogra_> sil2100, patience
[19:25] <ogra_> i said the same thing last night
[19:27] <ogra_> plars, well, take a close look at the bootloader version etc ... beyond that ... i would blame mmc wearout, take a look at syslog/dmesg on them ... its not like these phones get used "normal" :)
[19:51] <plars> yeah, look for the 97 failures to start dropping before getting excited. That will be a bit longer
[19:52] <ogra_> yup
[19:54] <tedg> Hmm, why are silos rebuilding? Are we decided on the greeter in/out thing?
[19:54] <tedg> Or is the bot just going crazy.
[19:57] <ogra_> tedg, i would suspect the latter
[19:57] <ogra_> the greeter in/out thing will be decided once we have complete test results
[19:57] <ogra_> then the channel topic will also be updated
[19:58] <ogra_> (it is looking promising  fwiw)
[19:59] <tedg> ogra_, okay, thanks. Didn't realize that was in the topic, it was ellipsized for me.
[20:01] <ogra_> yeah, topics arent a good place ... but easy to point to ;)
[20:02] <ogra_> now there comes an exciting one ...
[20:03]  * ogra_ sees clock-app running 
[20:05] <ogra_> and passed !!!!
[20:08] <ogra_> oooh ... thats looking so promising !!!
[20:08] <ogra_> i terminal app failure ... we had that before ...
[20:09] <sil2100> :D
[20:17]  * sil2100 writes the e-mail
[20:18] <sil2100> I guess the results look far better than before, so the chances of us going down from TRAINCON-0 are highish
[20:23] <ToyKeeper> Hello jet lag...  how are you today?
[20:24] <plars> sil2100: ok, weather is running now, after it completes we should actually see the failures start to drop quickly
[20:25] <sil2100> plars: \o/
[20:25] <plars> it appears to be passing now, and was completely failing before
[20:31] <plars> sil2100: down to 77 now
[20:32] <plars> filemanager will pass too
[20:32] <sil2100> plars: so far it looks very similar to what we had before
[20:32] <sil2100> So I'm really really happy!
[20:32] <plars> sil2100: when will the next image build?
[20:37] <sil2100> plars: the cronjob I think is around 3 UTC I guess?
[20:39] <plars> sil2100: ok, since this experiment seems successful and mako is the one getting the most attention, are you ok to leave things as-is on flo/manta and let them run on the next image?
[20:39] <plars> sil2100: mako will have a complete set of results with the workaround for the dbus-x11 removal in 63 though
[20:43] <sil2100> plars: so the fix is only for mako for now, right?
[20:43] <ogra_> looking good...
[20:43] <sil2100> plars: what will we need to do to get all others working?
[20:43] <plars> sil2100: no, it's generic enough. I can rerun them if you really need, will just require some babysitting on my part
[20:44] <ogra_> nah
[20:44] <ogra_> we'll get a new image by cron is a few hours
[20:44] <sil2100> Nah
[20:44] <sil2100> Just asked out of curiosity
[20:44] <ogra_> should be enough to have proper data tomorrow
[20:44] <sil2100> As long as other images will be ok
[20:44] <ogra_> sil2100, first thing we land tomorrow should be the gallery-app fix
[20:44] <sil2100> ogra_: right, I think we can land it even now
[20:45] <ogra_> now that the rest looks so nice that red really sticks out :)
[20:45] <sil2100> I mean, we wait until we get full results, we drop TRAINCON and BLAM, UITK lands!
[20:45] <ogra_> i would like to see what dialer app does
[20:45] <sil2100> Then BOOM and the image is broken
[20:45] <ogra_> that behaved very odd
[20:45] <sil2100> BOOOOOM AND BROKEN
[20:45] <ogra_> and sadly uses dbus-x11
[20:45] <sil2100> Sorry, got carried away
[20:45] <ogra_> haha
[20:50] <sil2100> btw.
[20:50] <sil2100> ogra_, robru, Mirv: we might consider moving the landing-related discussions to -release
[20:51] <ogra_> you mean in general ?
[20:51] <sil2100> As slangasek mentioned, it's a release related thing, so it should be discussed somewhere more public
[20:51] <sil2100> Yeah
[20:51] <ogra_> ok
[20:51] <ogra_> no prob with that
[20:51] <sil2100> I know we were worried about spamming channels with our landing 'bla bla', but well... slangasek gave us the blessing!
[20:52] <ogra_> prepare for a lot of critics from ScottK then :)
[20:52] <sil2100> :|
[20:52] <sil2100> He didn't vote for my MOTU application!
[20:52] <sil2100> Yet!
[20:52] <ogra_> he is a grumpy nitpicker ... but usually has a point
[20:55] <ogra_> but while he is a pita he also kind of is our community conscience ... it is good to get reminded soemtimes that we dont forget about community
[21:01] <sil2100> Indeed
[21:02] <sil2100> But he's a bit rude I noticed, this is my only complaint about him
[21:02] <cjwatson> I think this basically a result of feeling largely ignored
[21:02] <ogra_> so how about i do something ... like ...
[21:03] <cjwatson> *this is
[21:03] <sil2100> ogra_: ++
[21:03] <ogra_> weheee :)
[21:03] <sil2100> Sending out the e-mail :)
[21:03] <ogra_> (i removed TRAINCON-0 )
[21:03] <cjwatson> (IOW, he feels he has to be, um, "direct" in order to get anywhere at all)
[21:03] <ogra_> in case someone misse dit
[21:03] <ogra_> cjwatson, yeah
[21:04] <sil2100> robru: ^ and as per e-mail, we're off from TRAINCON-0
[21:04] <ogra_> sil2100, so do you want to let the gallery-app fix in now so we get it in the cronned image ?
[21:04] <sil2100> Yes :)
[21:04] <sil2100> Pressing teh button
[21:04] <ogra_> or if rob works today we can leave it to him :)
[21:04] <ogra_> yay
[21:05] <sil2100> (have some connectivity problems though)
[21:05]  * ogra_ is so happ ywe finally got that sorted
[21:05] <ogra_> that were two painful days and nights
[21:06] <ToyKeeper> Hmm, 22 KiB/s from Click's servers to my phone.
[21:06] <ToyKeeper> Er, unity8 probably shouldn't be sustaining 50% to 60% cpu load while the phone is idle with the screen off.
[21:06] <sil2100> I published something, hope I published the right UITK landing ;p
[21:07] <ogra_> ToyKeeper, it also shouldnt consume twice the amount of ram :)
[21:08] <ogra_> ToyKeeper, what kept us in TRAINCON-0 and caused so many issues was a pretty giant landing ... watch out for more regressions there are surely some nobody has found yet
[21:08] <ogra_> its like an easteregg hunt :)
[21:08] <ToyKeeper> Seems that the app scope's app preview screen uses 50% to 70% of the CPU, regardless of whether the screen is on.
[21:08] <ogra_> definitely worth a bug
[21:09] <ToyKeeper> I think I'm going to be up rather late tonight filing all the bugs I found today.
[21:09] <ogra_> well, i hope you test with 63
[21:09] <ToyKeeper> This was on #63.
[21:09] <ToyKeeper> Much better than 62, BTW.  :)
[21:10] <ogra_> everything between 59 and 63 was konwn to have very serious issues
[21:10] <ogra_> yeah, still not the final fixes, mterry is currently replacing the workarounds
[21:10] <ogra_> but surely also wants to know about all regressions
[21:11] <ogra_> *but he
[21:11]  * ogra_ cant type anymore after two 16h days 
[21:11]  * ToyKeeper facepalm...  just realized I flashed #63 over the notes for the bugs I found in #62 this morning
[21:11] <ogra_> and on that note ...
[21:12] <ogra_> oh my
[21:12] <ToyKeeper> Yeah, sounds like bed time.
[21:12] <ToyKeeper> I'm jetlagged and barely conscious, but nowhere near done with today's tasks.
[21:17] <robru> hey i'm around, was just on lunch. what needs landing?
[21:17] <robru> sil2100,  ^
[21:17] <sil2100> robru: landed UITK just now
[21:17] <robru> sil2100, what about gallery in silo 11?
[21:18] <robru> sil2100, also do you know what's going on with the spreadsheet? seems the bot is going crazy pinging things
[21:18] <sil2100> robru: it's not tested
[21:19] <robru> sil2100, true.
[21:19] <sil2100> robru: well, the spreadsheet does do some crazy stuff today
[21:20] <sil2100> Ok, it's late now, time to get a life!
[21:20] <sil2100> :D
[21:21] <sil2100> robru: don't worry about the bot, the spreadsheet did break for me just now, so it can also be related...
[21:21] <sil2100> robru: keep an eye on the spreadsheet reverting itself
[21:22] <sil2100> You can find the backups here:
[21:22] <sil2100> http://sil2100.vexillium.org/citrain-backups/
[21:23] <slangasek> ogra_, sil2100: I don't think ScottK would object to having more of the discussions around things that are landing happening in the "traditional" channels; my guidance is that people should in general be less afraid of offending someone by talking in the "wrong" channel
[21:23] <tedg> Hmm, it's late, but would test results for silo 18 be valid now?
[21:23] <tedg> Do I need a rebuild?
[21:25] <ogra_> slangasek, i didnt mean we would annoy him, i said sil2100 should be prepared for more critics in a channel where he is around (and will see the landing process or even occasionally look at patches)
[21:25] <robru> tedg, when was the last build?
[21:25] <tedg> robru, Sunday
[21:26] <ogra_> slangasek, i aslo dont think thats a bad thing ... but he can be quite a nitpicker at times :)
[21:26] <slangasek> ogra_: ah, you mean more community oversight ;-)
[21:26] <ogra_> right :)
[21:27] <tedg> robru, I believe you said there was a way to test a silo with upgrade only?
[21:27] <robru> tedg, yeah, 'citrain device-upgrade 18'
[21:28] <robru> tedg, I just checked your silo contents, of all the packages in your silo, I don't see any new releases for any of them since may 26th, so I guess you don't need a rebuild (it seems all the latest panic fixes didn't touch any pckages in your silo)
[21:28] <tedg> robru, Great! I'll retest, but looking at the greeter changes I'm not too worried.
[21:29] <tedg> Trying to get kenvandine off my back, he's heavy!
[21:30] <tedg> ;-)
[21:30] <robru> hmmmm, hang on a sec
[21:30] <robru> tedg, I was checking the dates in the version numbers, which would be build dates, not publish dates...
[21:30] <robru> should check again
[21:30] <tedg> How does one get publish dates?
[21:31] <robru> tedg, http://people.canonical.com/~rbpark/citrain/ click on the package names, it links to the lp source package pages, it shows version numbers and date uploaded
[21:32] <robru> tedg, so ubuntu-touch-session was uploaded on the 1st... but according to the build log that's in there. so now I'm doubly sure your silo is safe to test ;-)
[21:33] <tedg> Heh, great!
[21:33] <slangasek> ogra_: regarding your latest mail on the smoke tests - could I talk you into writing something on https://wiki.ubuntu.com/LandingTeam/IncidentReports to explain how the test envs were different / why ?
[21:33] <tedg> Reflashing first though.
[21:33] <ogra_> slangasek, sure, but not tonight anymore :)
[21:34] <slangasek> ogra_: ack - thanks
[21:35] <ogra_> slangasek, i think it is still not clear to us why apt-get autoremove --purge didnt remove the package alongside though ... the workaround i wrote about is simply adding dbus-x11 to that apt command
[21:45] <josharenson> fginther, looks like the new test is running and generating artifacts just fine. Thanks.
[21:52] <slangasek> ogra_: alright
[21:54] <cjwatson> tedg: if it's expired from robru's citrain pages, then https://launchpad.net/ubuntu/+source/SOURCE-PACKAGE/+publishinghistory is a good thing to have smart-bookmarked/memorised
[21:55] <cjwatson> (for things that have been published to the primary archive and are no longer in silos)
[21:59] <tedg> cjwatson, Ah, cool. Thanks!
[22:02] <robru> cjwatson, hmmmm, suddenly I want to create a package that contains a ton of smart-bookmarks for all these little things (i have dozens...)
[22:04] <robru> ogra_, hey, what's going on in silo 20? if the fix already landed, then what's this silo doing just being "built" without being published yet?
[22:05] <ogra_> robru, the real fix hasnt landed ... its hacks all the way down ... 20 has the proper fixes
[22:05] <robru> ogra_, ooooooh, ok thanks.
[22:05] <ogra_> :)
[22:06] <robru> mterry, Saviq you guys need any help testing silo 20?
[22:06] <ogra_> talk to mterry and Saviq for details
[22:06] <ogra_> heh, snap :=
[22:06] <ogra_> :)
[22:06] <robru> ;-)
[22:20] <sil2100> o/
[22:44] <tedg> robru, sil2100, testing looks good.
[22:44] <tedg> robru, How do you want to handle landing 18?
[22:56] <tedg> robru, I'm going to EOD. Bear in mind that a publish requires a NEW queue ack.
[22:57] <tedg> Not sure if that means DO IT so it can get in the queue, or wait :-)
[22:57] <robru> tedg, well, probably DO IT
[22:57] <tedg> DO IT!
[22:57] <robru> tedg, because everything else will just get stuck in -proposed anyway
[22:57] <robru> ;-)
[22:57]  * tedg invokes peer pressure
[22:58] <robru> tedg, well we're out of TRAINCON-0, so there's no reason I can't. and I know it wont' get through NEW before the next image builds, so I think it's fine
[22:58] <robru> ;-)
[22:58] <tedg> Heh, okay.
[23:00] <robru> tedg, https://ci-train.ubuntu.com/job/landing-018-2-publish/29/console ;-)