2014/02/17/#ubuntu-ci-eng.txt

[08:33] <thostr_> sil2100: can you give me a silo for line 39?
[08:42] <sil2100> thostr_: one moment ;)
[08:44] <sil2100> Good thing that the spreadsheet seems in a better state today
[08:44] <sil2100> thostr_: done
[08:48] <sil2100> didrocks: morning! Do you have a moment for some packaging ACKs?
[08:48] <sil2100> didrocks: these are for the unity7 stack
[08:51] <didrocks> sil2100: sure
[08:55] <sil2100> didrocks: http://162.213.34.102/job/landing-003-2-publish/15/artifact/packaging_changes_unity_7.1.2+14.04.20140214.1-0ubuntu1.diff http://162.213.34.102/job/landing-003-2-publish/15/artifact/packaging_changes_unity-scopes-shell_0.3.1+14.04.20140214-0ubuntu1.diff and http://162.213.34.102/job/landing-003-2-publish/15/artifact/packaging_changes_bamf_0.5.1+14.04.20140214.1-0ubuntu1.diff for starters
[08:55] <sil2100> didrocks: there's also compiz: http://162.213.34.102/job/landing-003-2-publish/15/artifact/packaging_changes_compiz_1%3A0.9.11+14.04.20140214-0ubuntu1.diff <- there are some migrations there as well
[08:56] <sil2100> Reminds me of the 'good' old times
[08:56] <didrocks> sil2100: hum, have you checked that we actually want to remove the decoration? I remember that seb128 was seeing the new decorations as regressions
[08:56] <didrocks> no right click on the title bar and so on
[08:57] <didrocks> +1 on bamf and u-s-c
[08:57] <seb128> hey there
[08:57] <didrocks> salut seb128 !
[08:58] <seb128> didrocks, trevinho got a branch to fix the lack of menu, not sure if they included in that landing, but I see that as an ok tradeoff to get things moving, there has been no landing for those components in years so the first one is going to be a little bumpy
[08:58] <didrocks> seb128: ok then, as long as you are happy :)
[08:58] <didrocks> sil2100: I think you checked that unity-autopilot was in universe, and so, it's ok to have it depending on mesa-utils :)
[08:58] <sil2100> seb128, didrocks: there were some branches I added to this landing on Friday morning, so it's in most probably
[08:59] <seb128> oh right, they are there
[08:59] <didrocks> sil2100: +1 on unity
[08:59] <didrocks> remains compiz to check
[09:00] <seb128> not that robert_ancell did some manual uploads meanwhile
[09:00] <seb128> I would say to override those
[09:00] <vila> didrocks, sil2100, Mirv (vacations ?): qa-intel-4000 was out-of-disk ( fginther fixed that on Friday but it happened again last night), fixed now but some jobs may have failed because of that
[09:00] <sil2100> hmmm... I see one problem though!
[09:01] <didrocks> vila: thanks !
[09:01] <sil2100> didrocks: I don't see nux in the landing ;/
[09:01] <sil2100> Craaaap
[09:01] <didrocks> sil2100: no nux or no nux packaging change?
[09:02] <seb128> https://launchpad.net/~ci-train-ppa-service/+archive/landing-003/ has it
[09:02] <sil2100> didrocks: wait, I'm blind, I see it now
[09:02] <sil2100> didrocks: thought it got reverted during the spreadsheet problems, phew
[09:02]  * sil2100 is blind
[09:03] <didrocks> sil2100: packaging changes for it or none?
[09:03] <sil2100> didrocks: none
[09:03] <vila> didrocks, sil2100: Indeed http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1556/console, http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1557/console and http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1558/console failed because they couldn't even create the script containing the commands to execute...
=== psivaa-afk is now known as psivaa
[09:04] <sil2100> vila: huh, out of disk space so frequently?
[09:05] <vila> sil2100: under investigation but it seems that one container was consuming ~500M for raring, ~1G for saucy and ~3G for trusty
[09:05]  * sil2100 hopes bregma tested the migration script for compiz
[09:05] <vila> sil2100: so either it's "normal" and we need a bigger disk or something wrong is going on
[09:08] <didrocks> sil2100: all migrations scripts for compiz: + 1
[09:10] <didrocks> so all ok for me
[09:10] <sil2100> \o/
[09:11] <sil2100> Then publishing!
[09:11] <sil2100> bregma will be happy ;)
[09:12] <sil2100> didrocks: thanks!
[09:13] <sil2100> eeek
[09:17] <sil2100> didrocks: so, publishing failed since 5 hours ago there has been a direct upload of compiz and unity - now, the directly uploaded versions deal with the unity-control-center and similar dependencies
[09:18] <didrocks> sil2100: this is what seb128 told above
[09:18] <didrocks> 10:00:01   seb128 | not that robert_ancell did some manual uploads meanwhile
[09:18] <didrocks> 10:00:08   seb128 | I would say to override those
[09:18] <didrocks> sil2100: did you miss that? ^
[09:18] <sil2100> didrocks: hah! Yes ;)
[09:19] <mhr3> sil2100, silo for #40 pls?
[09:19] <sil2100> mhr3: will do in a moment :)
[09:19] <sil2100> didrocks: so hm, override? People are going to yell at me again for 'removing changelog history' ;D
[09:19] <didrocks> sil2100: ignore or direct those to seb128 or I
[09:19] <mhr3> also, you evil people deleting lots of landing requests :P
[09:20] <didrocks> mhr3: look at the ubuntu-touch ML, google issue
[09:20] <sil2100> mhr3: it was the spreadsheet!
[09:20] <mhr3> yea, right :P
[09:20] <didrocks> everything is explained dude :p
[09:20] <seb128> didrocks, sil2100: don't worry, robert_ancell is not like that ;-) (and I'm going to email him about those)
[09:20] <mhr3> i know it is, i read it, still evil :P
[09:20] <didrocks> ahah
[09:21] <sil2100> ;)
[09:21] <didrocks> mhr3: TBH, I would prefer not having that, we had to reconciliate the state which was totally out of sync with jenkins
[09:21] <didrocks> one by one
=== Ursinha is now known as Ursinha-afk
[09:22] <sil2100> I wonder if those problems will be back again
[09:22]  * didrocks hopes not
[09:23] <sil2100> mhr3: ok, so please wait until the unity7 landing arrives in the archive, since right now it's blocking assignment of 40
[09:23] <mhr3> do we know why did it even happen?
[09:23] <sil2100> mhr3: since we had to bump a build-dep there
[09:23] <mhr3> sil2100, how long is that going to take?
[09:24] <sil2100> mhr3: they're migrating now, not sure how long it usually takes for unity7 to migrate, but I wouldn't assume anything longer than like 2 hours max?
[09:25] <mhr3> sil2100, could you ping me once you assign it?
[09:25] <sil2100> mhr3: sure
[09:28] <seb128> sil2100, didrocks: I promoted libunity-core-6.0-9 for you, should avoid hitting component mismatch and having to wait some extra publisher runs later on
[09:28]  * seb128 is used by now at the new binaries being copied to universe
[09:28] <didrocks> seb128: thanks
[09:28] <sil2100> seb128: thanks!
[09:28] <seb128> yw ;-)
[09:29] <vila> didrocks, sil2100: I got my numbers wrong, it's 30G to 3G, apparently record-my-desktop accumulate sessions under /tmp but only on qa-intel-4000
[09:29] <vila> s/to 3G/not 3G/
[09:29] <sil2100> oh shit
[09:30] <vila> sil2100: s/oh/of/ ? :-D
[09:31] <sil2100> ;D
[09:31] <sil2100> No no no
[09:31]  * ogra_ has some browser issues ... might be late 
[09:31] <didrocks> ogra_: should we start without you?
[09:32] <ogra_> there we go
[09:33] <popey> bug 1281026
[09:33] <ubot5> bug 1281026 in dialer-app (Ubuntu) "Putting call on hold no longer gives notification mako #188" [Undecided,New] https://launchpad.net/bugs/1281026
[09:34] <seb128> popey, is you "screen turn off when using power settings" happening with the indicator as well?
[09:42] <popey> seb128: having troublr reproducing that now ⍨
[09:49] <popey> ApplicationManager: application 'webbrowser-app' died unexpectedly!
[09:50] <popey> is it normal to see that in unity8.log?
[09:53] <didrocks> Saviq: ^
[09:53] <didrocks> I would have said we use upstart, so should be in the log
[09:54] <didrocks> but the application manager (in unity-mir) is running in the unity8 process?
[09:54] <didrocks> (IIRC)
[09:54] <Saviq> didrocks, popey, yes, that basically means upstart "lost" the app instance
[09:54] <popey> seeing that a lot
[09:54] <ogra_> it is loosing a lot lately
=== Ursinha-afk is now known as Ursinha
[10:02] <popey> any way to debug why the welcome screen isn't appearing for me when I lock the phone?
[10:02] <popey> by "lock" I mean "press the power button"
=== vrruiz_ is now known as rvr
[10:11] <didrocks> Saviq: any idea on that one? Seems it's from some images ago ^
[10:11] <didrocks> popey: you don't have any reliable reproducer, right ?
[10:12] <Saviq> popey, didrocks, nope, only thing I saw is sometimes it won't wake up on first power press, but lock screen's always there
[10:15] <seb128> didrocks, sil2100, mhr3: just as a fyi, compiz/unity migration is going to take some extra hours, they stopped the ppc64el builders to change configs, it's going to need to build there before migrating (which means waiting for builders to be back, then build compiz, they building unity once it's published)
[10:16] <didrocks> thanks for keeping us posted seb128
[10:16] <seb128> yw!
[10:17] <mhr3> sigh, hate when things take so long
[10:17] <mhr3> but yea, thx for update
[10:17] <seb128> you got unlucky, they are reboostrapping that new arch, which is a one time thing
[10:18] <popey> didrocks: Saviq seems wedged in some kind of phone call mode. The "near my ear sensor" is active, if I wave my hand over the phone it blanks the screen.
[10:18] <Saviq> popey, sounds like ofono / powerd got stuck indeed
[10:20] <didrocks> yeah, can be powerd, will need a good and detailed bug report I guess
[10:23] <sil2100> seb128: thanks
[10:27] <ogra_> didrocks, maguro looks okayish
[10:27] <didrocks> ogra_: excellent, let's promote then!
[10:27] <sil2100> \o/
[10:28] <popey> Saviq: didrocks initctl is spinning 100%
[10:28] <popey> and my phone will die as a result, battery level 1%
[10:29] <popey> which app should I file a bug against while I can
[10:30] <ogra_> === Image 188 Promoted ===
[10:30] <ogra_> popey, upstart-app-launch i guess
[10:30] <didrocks> popey: hum, noy sure filing a bug will give us more infos. It's a one time thing again?
[10:30] <didrocks> upstart-app-launch changed a lot recently
[10:30] <didrocks> maybe thostr_ can help you with that ^
[10:30] <popey> didrocks: no, it's not the first time this has happened
[10:30] <didrocks> so you can't even bisect the image :/
[10:31] <popey> root       598 16.2  4.5  88792 86892 ?        R    Feb15 431:02 initctl emit boot-hooks WHEN=new-version OLD_BUILD=176 NEW_BUILD=181
[10:31] <popey> thats what's eating the cpu
[10:32] <Saviq> no idea what triggers that :/
[10:32] <Saviq> sounds like upgrade mechanism
[10:32] <didrocks> yeah
[10:33] <didrocks> popey: can you try flashing an older image like 181, and see if we get that event again? (if it's an upgrade?)
[10:33] <popey> that _is_ 181
[10:33] <popey>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
[10:33] <popey>  1981 phablet   20   0  679256 665744   1160 S   0.3 34.7  33:23.17 init
[10:34] <popey> http://paste.ubuntu.com/6948119/
[10:38] <ogra_> popey, i think mhall opened a bug for that quite a while ago ...
[10:38] <ogra_> havent seen it in a long time
[10:38] <popey> thanks.
[10:39] <popey> I'm guessing many people here don't see it because they're always rebooting their phones. these things come out for me during the weekend when it's left on
[10:40] <ogra_> mine runs all the time
[10:40] <ogra_> popey, do you notice weird battery behavior when the battery is low (around and below 20%) ?
[10:41] <ogra_> mine gets very jumpy ... hops around between 12 and 20 then, with the indicator going red when it drops to 12
[10:41] <popey> not noticed
[10:42] <popey> my dmesg is spammed with battery notifications though - filed that bug
[10:42] <popey> bug 1280124
[10:42] <ubot5> bug 1280124 in linux-mako (Ubuntu) "kernel log getting spammed every 10s with battery notifications" [Undecided,New] https://launchpad.net/bugs/1280124
[10:43] <ogra_> popey, duplicate of bug 1270248
[10:43] <ubot5> bug 1270248 in logrotate (Ubuntu) "/var/log fills up disk space on phone" [High,Confirmed] https://launchpad.net/bugs/1270248
[10:52] <popey> i think ofono getting wedged might be related to me running out of phone credit and trying to make a call
[10:58] <popey> damnit, phone died before I could get bug data out of it.
[12:18] <sil2100> didrocks: I'm afraid the spreadsheet problems are starting to appear again
[12:22] <popey> bug 1281082
[12:22] <ubot5> bug 1281082 in unity8 (Ubuntu) "Empty sidestage pops out when not wanted" [Undecided,New] https://launchpad.net/bugs/1281082
[12:26] <sil2100> hmmm
[12:28] <sil2100> thostr_: I'll try assigning you a silo now, but it's all very risky as the spreadsheet is b0rken again and I'm doing it manually
[12:29] <thostr_> sil2100: ok
[12:31] <sil2100> thostr_: ok, silo assigned
[12:32] <sil2100> thostr_: be advised that google might say 'f**k it' and simply revert my changes now, so just give me a sign if by any chance your landing assignment gets erased
[12:33] <sil2100> didrocks: it seems some parts work correctly and some don't - the Oops error pops up again and assigning silos doesn't work - it generates the UID but doesn't do the assignment in metadata
[12:33] <sil2100> didrocks: I was doing it manually
[12:33] <sil2100> didrocks: the rest seems to work though
[12:33] <sil2100> (like the syncstatus bits)
[12:39] <didrocks> sil2100: not sure what to say but "ggg" :/
[12:39] <didrocks> I guess the unassignement won't work
[12:40] <thostr_> anybody has a clue what "jettisoned without merging" means?
[12:41] <thostr_> ci sheet line 32
[12:42] <didrocks> not sure as well
[12:45] <boiko> hi guys, one question: I had one MR in the spreadsheet that had a conflict, and it now got updated, do I need to do anything, or will the silo build be triggered automatically again?
[12:46] <didrocks> boiko: you  pushed to the same MP?
[12:46] <didrocks> (or rather, branch)
[12:46] <boiko> didrocks: yep
[12:47] <didrocks> boiko: so, you need to rerun the build job yourself to take into account
[12:47] <didrocks> boiko: if you have more than one component, you can just ask to rebuild one with the build only parameter
[12:47] <didrocks> tell me if there is anything unclear to you
[12:50] <boiko> didrocks: nice! let me try that
[12:52] <boiko> didrocks: so, I think I need to build two of the MRs from the branch, what separator should I use? spaces?
[12:54] <didrocks> boiko: it's not per MP, it's per component
[12:54] <didrocks> boiko: so, for instance, if you set "dialer-app messaging-app
[12:54] <didrocks> "
[12:54] <didrocks> it will rebuild all MPs for dialer-app and messaging-app
[12:54] <didrocks> that are part of the list
[12:55] <boiko> didrocks: ah yes, sorry, I didn't write it correctly, that's what I need, rebuild telephony-service and messaging-app, thanks
[12:55] <didrocks> (and not, let's say indicator-session if it was in the same request)
[12:55] <didrocks> ok, so just put telephony-service messaging-app"
[12:55] <didrocks> boiko: space to separate those :)
[12:55] <boiko> didrocks: yep, thanks
[12:55] <boiko> didrocks: "boiko is missing the Job/Build permission"
[12:56] <didrocks> oh
[12:56] <didrocks> I thought I added you to the team
[12:56] <didrocks> boiko: when you logged in, have you checked the ci-train-users" checkbox in launchpad sso?
[12:56] <didrocks> (you need to do that the first time)
[12:57] <boiko> didrocks: hmm, I didn't have that option there
=== alan_g is now known as alan_g|lunch
[12:58] <didrocks> ah, yeah, I didn't add you, one sec
[12:58] <didrocks> boiko: you should see the option now
[12:58] <sil2100> didrocks: after lunch, around 15 of our time, I'll have to drive with my rat to the vet - depending on the diagnosis it might take more or less time
[12:58] <didrocks> boiko: btw, please come to the bootcamp now :)
[12:58] <didrocks> sil2100: oki, you should you will be back before the meeting,
[12:59] <boiko> didrocks: it's tomorrow, right?
[12:59] <didrocks> yeah
[12:59] <sil2100> didrocks: I'm sure I will, unless they decide to operate her like NOW ;) Which is highly improbable
[12:59] <didrocks> sil2100: oki, ttyl!
[12:59] <boiko> didrocks: now it works, thanks
[13:00] <didrocks> boiko: yw ;)
[13:23] <mhr3> sil2100, can we add 2 pkgs to the seed?
[13:23] <mhr3> sil2100, those being unity-scope-mediascanner2 and unity-scope-scopes
[13:26] <bregma> didrocks, once my ci-train stuff has landed completely does the line in the spreadsheet disappear automagically?
[13:26] <didrocks> bregma: it will become "landed" once you merge and clean
[13:26] <didrocks> (if sil2100 hasn't done it)
[13:27] <didrocks> it's up to you to do it, as you will see in tomorrow's bootcamp
[13:28] <bregma> didrocks, everything's merged and the silo has been cleaned and repurposed but the line in Pending is still there,  perhaps there was a burp somewhere
[13:29] <didrocks> bregma: ah, we keep them for some days
[13:29] <didrocks> bregma: so that you can see it was landed
[13:29] <didrocks> then, it's moved to the archive one
[13:29] <bregma> so I can just start adding new landings then?
[13:30] <sergiusens> didrocks, hey; going to need some hand holding for landing 33 (as it requires a seed change); when can we get that done
[13:30] <didrocks> bregma: see #ubuntu-desktop, there is one landing we need for one MP that was incorrect (missing -0ubuntu4), we are going to quickly land that
[13:31] <didrocks> sergiusens: we need to have "ready" set to yes first
[13:31] <didrocks> sergiusens: do you know why ubuntu-settings doesn't have MP? I would prefer we use a branch
[13:31] <didrocks> (of course, not for ubuntu-touch metapackage)
[13:32] <sergiusens> didrocks, https://code.launchpad.net/~bfiller/ubuntu/trusty/ubuntu-settings/touch-settings-click/+merge/206530
[13:32] <didrocks> sergiusens: it's not a branch as the others
[13:32] <didrocks> sergiusens: the bot has no access to it
[13:32] <sergiusens> didrocks, that situation is very ugly, we will most likely need to change it as the version won't be that; but until I get a lock on camera && gallery, I won't know what version it will be
[13:33] <sergiusens> didrocks, where does system settings live, I'll move the mr to there; just noticingit's against an ubuntu branch
[13:33] <sergiusens> *noticing
[13:33] <didrocks> sergiusens: I don't know, if there is no lp:ubuntu-settings, I would prefer we setup one
[13:33] <didrocks> that can bzr bd and build the package
[13:36] <sergiusens> ogra_, do you know if we have one?
[13:37] <sergiusens> didrocks, there is no lp:ubuntu-settings at least
=== alan_g|lunch is now known as alan_g
[13:37]  * ogra_ reads backlog
[13:38] <ogra_> sergiusens, ask seb128 or Laney
[13:38] <sergiusens> forward ^
[13:38] <seb128> bregma, didrocks: I need https://code.launchpad.net/~seb128/unity/restore-gsd-override/+merge/206714 to land, fine if the landing includes other fixes
[13:38] <seb128> sergiusens, ogra_: what?
[13:39] <ogra_> seb128, the branch for touch-settings
[13:39] <sergiusens> seb128, do we have a regular lp branch for lp:ubuntu/ubuntu-settings
[13:39] <mhr3> sil2100, #40 rdy to publish
[13:39] <mhr3> or didrocks ^
[13:39] <sergiusens> seb128, as didrocks wants it under citrain
[13:39] <seb128> sergiusens, ogra_: hum, 'application://com.ubuntu.camera_camera_2.9.1.223.desktop' ... is that version? please tell me we are not going to need to update the key every time the click is updated?
[13:40] <ogra_> seb128, i think we do
[13:40] <seb128> no way
[13:40] <sergiusens> seb128, that seems to be, unity can't do matching yet
[13:40] <ogra_> well, upstart-app-launch does it for you
[13:40] <seb128> that's crazyness
[13:40] <ogra_> that logic needs to be moved into unity too i think
[13:40] <didrocks> mhr3: doesn't seem to be ready, see the comment
[13:40] <sergiusens> seb128, talk to ted or ken about it
[13:40] <ogra_> seb128, complain to ted
[13:41] <rsalveti> sergiusens: haha, didrocks published the qtubuntu one already
[13:41] <mhr3> seb128, does the comment in 003 still apply?
[13:41] <rsalveti> right before
[13:41] <bregma> seb128, didrocks I have 3 other small MPs for unity I want to land, shall I set one up?
[13:41] <seb128> mhr3, no
[13:41] <sergiusens> rsalveti, that means the sheet is outdated... didrocks can you check landing 007?
[13:41] <mhr3> didrocks, ^
[13:42] <seb128> bregma, yes please, as long as you include https://code.launchpad.net/~seb128/unity/restore-gsd-override/+merge/206715 and that we get that assigned soon
[13:42] <bregma> ASAP
[13:42] <seb128> bregma, current landing made g-s-d not run in trusty
[13:42] <didrocks> sergiusens: is it outdated? not for me
[13:42] <seb128> e.g no theme, no appmenu, no multimedia key
[13:42] <seb128> bregma, it makes me wonder how you guys tested the landing btw...
[13:43] <didrocks> bregma: seb128: just decide between you too what you want to include, but it needs to be quickly released, so don't take risks
[13:43] <sergiusens> didrocks, it says packages built and rsalveti tells me you already published... going to manually refresh sheet
[13:43] <seb128> didrocks, +1, thanks
[13:43] <didrocks> sergiusens: it says migrating as expected to me
[13:44] <sergiusens> didrocks, yeah, just refresh manually; wasn't getting the update
[13:44] <didrocks> mhr3: ok, publishing
[13:44] <didrocks> sergiusens: yeah, google backend is really flaky since last week
[13:45] <seb128> sergiusens, ogra_: ubuntu-settings is on https://code.launchpad.net/~ubuntu-desktop/+junk/ubuntu-settings atm, we should move that to a proper project indeed
[13:45] <mhr3> didrocks, ty
[13:45] <didrocks> mhr3: done
[13:45] <seb128> sergiusens, ogra_: I'm going to talk to ted/ken about the versionning
[13:46] <ogra_> seb128, i think you also need to involve jamie ... iirc there are security reqs as well wrt keeping the versiooning in the names
[13:49] <bregma> didrocks, I have line 44 ready
[13:49] <didrocks> bregma: assigning
[13:49] <ogra_> didrocks, can we let ubuntu-themes in soon ? i would like to be able to read email again :P
[13:50] <bregma> sweet
[13:50] <didrocks> ogra_: is there anything in ci train? I don't see it
[13:50] <ogra_> (evo has black bg without the new themes package)
[13:50] <didrocks> ogra_: or we'll need a lander
[13:50]  * sil2100 hates that his google spreadsheet is out of sync
[13:50] <ogra_> didrocks, i think seb128 has added it to the old spreadsheet
[13:50] <ogra_> manual upload etc
[13:50] <sil2100> ogra_: when did he add it?
[13:50] <ogra_> just needs approval
[13:50] <sil2100> Oh, he added it today
[13:50] <sil2100> ogra_: I can do it soon
[13:51] <seb128> didrocks, it has proven difficult to find somebody wanting to own that one
[13:51] <ogra_> no idea ... he just told me in -desktop
[13:51] <seb128> sil2100, thanks
[13:51]  * ogra_ hugs sil2100 
[13:51] <didrocks> seb128: well, we'll need to find someone, we'll shutdown the daily release at some point
[13:52] <ogra_> luckily the font isnt black too ... so with a lot of patience i can read the dark grey on black :)
[13:52] <seb128> didrocks, right, working on it, but you know how it goes with the italian mafia, not easy to convince :p
[13:52] <didrocks> heh, yeah ;)
[13:52] <didrocks> thanks
[13:52] <ogra_> seb128, pasta helps !
[13:52] <didrocks> seb128: you can run the build job on landing-006
[13:52] <didrocks> even if you don't see it associated
[13:52]  * didrocks grrr at the timeouts of the spreadsheet
[13:52] <seb128> didrocks, thanks
[13:53] <seb128> bregma, didrocks: unity build started on http://162.213.34.102/job/landing-006-1-build/25/console
[13:54] <didrocks> great
[13:54]  * didrocks continues to try to assign manually
[13:56] <didrocks> ah, good news, IS opened a request at google
[14:04] <sil2100> \o/
[14:05] <sil2100> ogra_, seb128: I'm building new packages of ubuntu-themes right now
[14:06] <seb128> sil2100, thanks
[14:07] <ogra_> yay, thanks !
[14:23] <didrocks> psivaa: do you have the link for the camera-app failing tests on public jenkins?
[14:33] <mhr3> didrocks, how is the upcoming distro freeze going to affect our landings?
[14:33] <didrocks> mhr3: everything that's on desktop will be impacted
[14:33] <didrocks> mhr3: things are touch only are not discussed yet
[14:34]  * ogra_ would assume we do the same as last release for touch ... 
[14:34] <mhr3> didrocks, i meant there's a real freeze period for the archive, right? if we try to land something touch-only during that time, will it actually land?
[14:35] <ogra_> general exception for all touch only stuff ... FFE for stuff in touch that touches other areas too
[14:37] <didrocks> mhr3: right now, the first freeze is feature freeze one
[14:37] <didrocks> nothing enforced
[14:37] <didrocks> just that things that will land on the destkop shouldn't change features
[14:37] <mhr3> didrocks, ah, ok, then all is cool :)
[14:41] <didrocks> and the spreadsheet reverted again :/
[14:42] <sil2100> THe fuuck...
[14:42] <didrocks> sil2100: do you have time to try to reconcialiate?
[14:42] <didrocks> like I'm sure the unity7 one is landed
[14:42] <didrocks> and we miss the additional bregma's/seb128 unity7 one
[14:43] <didrocks> I wonder if we don't have a client opened which is going crazy
[14:44] <didrocks> I can't even get the revision history…
[14:44] <seb128> didrocks, sil2100: the indicator-datetime one is missing as well
[14:44] <seb128> didrocks, the gdoc says "last edit 3 hours ago", that sounds wrong
[14:44] <mhr3> eh, how do i get to my merge&clean link now?
[14:44] <seb128> mhr3, what was your silo?
[14:45] <mhr3> seb128, 3
[14:45] <seb128> mhr3, http://162.213.34.102/job/landing-003-3-merge-clean/
[14:45] <didrocks> seb128: it is wrong
[14:45] <mhr3> seb128, not all is migrated yet though
[14:45] <mhr3> seb128, but thx :)
[14:45] <seb128> yw
[14:45] <didrocks> mhr3: you still have the link, just not the icon
[14:46] <sil2100> didrocks: I need to jump out to that vet now, but when I'm back then will try to fix up all which I remember ;/
[14:46] <didrocks> ok
[14:46]  * didrocks changes the status refresh to 5 minutes to see if this changes
[14:47] <didrocks> What do you think if I try to copy and paste this spreadsheet to another one?
[14:48] <didrocks> send an email to everyone to use the new one instead
[14:48] <didrocks> and see how it goes
[14:48] <didrocks> seb128: mhr3: thostr_: thoughts? ^
[14:48] <seb128> didrocks, wfm
[14:49] <didrocks> maybe let's give a day for google to look at it
[14:49] <didrocks> and move to that tomorrow
[14:50] <mhr3> didrocks, fine with me
[15:10] <psivaa> didrocks: https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-mako-smoke-daily/45/ has camera app failures. with image 184
[15:11] <didrocks> psivaa: thanks a lot!
[15:12]  * didrocks goes for a run
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
=== gatox is now known as gatox_lunch
[16:00] <ogra_> didrocks, on my way to the bootcamp but will be a min late or two
[16:05] <ogra_> ah, bah
[16:05] <ogra_> totally mixed up the days
[16:06] <sil2100> ;
[16:06] <sil2100> ;)
[16:16]  * sil2100 tries fixing the spreadsheet contents
[16:16] <sil2100> I feel it will be pointless, since google will revert anyway
[16:24] <sil2100> Damn, it's all so broken
[16:39] <asac> cyphermox_: will you be around for CITrain support today?
[16:40] <didrocks> asac: robru will probably be late FYI, so cyphermox_ is our only hope
[16:40] <cyphermox_> asac: you mean the usual meeting in 30?
[16:40] <asac> yeah
[16:40] <cyphermox_> yes
[16:40] <cyphermox_> 20 minutes actually I guess
[16:40] <didrocks> shower + 10 minutes for me :)
[16:41] <asac> cyphermox_: thanks! you are THE man tonight
[16:41] <asac> thostr_ will need you later
[16:41] <sil2100> didrocks: ok, I restored what I could from the backend to the spreadsheet
[16:41] <didrocks> sil2100: thanks dude
[16:41] <didrocks> we should do a walkthrough with cyphermox_ as well
[16:42] <didrocks> if this happens again
[16:42] <sil2100> didrocks: I still get the Oops'es though ;/
[16:42] <didrocks> "last edit was 5 hours ago"
[16:42] <didrocks> it's so so so wrong
[16:42] <didrocks> asac: we'll really need some google support…
[16:42] <asac> didrocks: you wont get that
[16:43] <sil2100> Then yeah, it will be reverted again I guess, just a matter of time
[16:43] <asac> didrocks: even the most influential person wont be able to get you more than filing a ticket
[16:43] <sil2100> I think we'll have to find another backend :<
[16:43] <asac> didrocks: check with #is etc. ... they can file you a ticket
[16:43] <cyphermox_> didrocks: bugs...
[16:43] <didrocks> asac: they did that (after 3 days)
[16:44] <didrocks> asac: I thought we got some contract support as being a customer
[16:46] <asac> didrocks: google apps is a mass user product
[16:46] <asac> didrocks: your tickets might get looked at at some point
[16:46] <asac> thats afaik the only support you get
=== gatox_lunch is now known as gatox
[16:46] <didrocks> asac: ok, I thought we got more support contract by buying google apps product license for company
[16:46] <asac> didrocks: https://support.google.com/a/answer/1047213?hl=en
[16:46] <didrocks> was so optimistic for once :)
[16:47] <didrocks> ok, it's like opening a bug then
[16:47] <asac> didrocks: yeah sorry. i really have never heard about anyone ever getting "real" support
[16:47] <asac> there is a phone number, but they wil just open a ticket for yo
[16:48] <didrocks> yeah, seeing that
[16:49] <asac> didrocks: so maybe think bout how to write the ticket so that you as a dev would look at it
[16:49] <asac> :)
[16:50] <asac> but thats the only way you can probably influence it
[16:50] <asac> call out REGRESSION :)
[16:50] <asac> in bold letters
[16:50] <asac> in subject
[16:50] <asac> and name a regression window
[16:56] <didrocks> asac: IS already opened it earlier today
[16:56] <didrocks> so I guess too late
[16:56] <asac> right
[16:56] <asac> didrocks: guess we could file duplicates :)
[16:56] <asac> doubt google cares
[16:56] <asac> just make it unobvious
[16:56] <didrocks> asac: do we have a special account to open a case?
[16:56] <popey> rewrite it in go
[16:56] <didrocks> popey: tsssssssss :)
[16:57] <popey> :D
[16:57] <asac> didrocks: check with the guy who opened the ticket i would think
[16:57] <popey> I love triggering your "tsssssssss"
[16:57] <asac> who was that
[16:57] <asac> didrocks: ?
[16:57] <didrocks> asac: I'll do that, finishing prepping the meeting
[16:57] <didrocks> popey: I'm expecting you are giving such argument at next Linux Unplugged :)
=== jasoncwarner__ is now known as jasoncwarner
[17:03] <popey> hah
[17:11] <bregma> sil2100, is it OK to re-add stuff to ci-train that disappeared this morning in the kerfuffle (I had a compiz landing disappear before being allocated)
[17:15] <sil2100> bregma: yes, we're sadly still cursed by spreadsheet problems and entries get reverted ;/
[17:20] <popey> ☻  didrocks
[17:34] <sil2100> robru: I'll try publishing silo 004 if anything
[17:35] <sil2100> robru: ok?
[17:35] <robru> sil2100, sure...
[17:38] <elopio> ping cihelp, have any of you seen this error in other apps? http://91.189.93.70:8080/job/generic-mediumtests-trusty/1332/artifact/ubuntu_clock_app.tests.test_stopwatch.TestStopwatch.test_create_lap.ogv
[17:39] <elopio> qmlscene doesn't seem to be properly loading the qml.
[17:42] <sil2100> didrocks: ok, it seems to have finished
[17:43] <sil2100> didrocks: now it's waiting for stuff to build
[17:44] <vila> elopio: that rings no bells sorry, US guys are on holiday, try again tomorrow ? But I don't think they look at a lot of videos either
[17:48] <didrocks> sil2100: yeah, all .project files are here
[17:48] <didrocks> sil2100: oh no sorry
[17:48] <didrocks> sil2100: only 2
[17:48] <didrocks> dbus-test-runner.project
[17:49] <didrocks> libdbusmenu.project
[17:49] <thomi> fginther: if you have a moment - how often are the medium test runner machines (or VMs or whatever) dist-upgraded?
[17:49] <didrocks> sil2100: oh, I know why it's looking at the others, because they are on the ppa
[17:49] <didrocks> hum no
[17:49] <didrocks> that doesn't make any sense :/
[17:50] <didrocks> sil2100: oh, found the bug
[17:50] <sil2100> wtf
[17:50] <sil2100> Oh?
[17:50] <didrocks> ./indicator-network/unity-greeter-session-broadcast.project
[17:50] <didrocks> ./indicator-network/libdbusmenu-qt.project
[17:50] <didrocks> ./indicator-network/url-dispatcher.project
[17:50] <didrocks> I guess when there is no packaging diff, I don't come back to root
[17:50] <didrocks> sil2100: ok, let's kill the build and cook a quick fix
[17:51] <sil2100> hah! In the wrong directory!
[17:51] <sil2100> didrocks: good catch ;)
[17:51] <sil2100> Cancelling
[17:52] <didrocks> sil2100: pushed, mind deploying in production? and rerun :)
[17:56] <sil2100> Sure ;)
[17:56] <didrocks> hum
[17:56] <didrocks> you rerun the build job?
[17:56] <didrocks> ah no :)
[17:56] <didrocks> it's landing-001 :p
[17:56] <didrocks> ignore me
[17:57] <sil2100> didrocks: re-runing the build job now ;p
[18:03] <mandel> didrocks, sil2100 do you have any feedback about udm?
[18:03] <didrocks> sil2100: ok, it works now
[18:03] <sil2100> \o/
[18:03] <didrocks> mandel: you mean, new bugs are anything?
[18:03] <didrocks> or*
[18:04] <didrocks> sil2100: I'll let you handle that one and get that published?
[18:04] <mandel> didrocks, as in, did we add it to the new img? (188)
[18:04] <mandel> didrocks, the branches we talked about last friday (maybe it was with sil2100 and not you)
[18:05] <sil2100> didrocks: sure ;)
[18:05] <didrocks> mandel: is it merged in your trunk?
[18:05] <sil2100> mandel: I guess all landed from Friday that was tested, and it seems to be in the image since the weekend already
[18:05] <sil2100> No noticible regressions ;)
[18:06] <didrocks> 239. By PS Jenkins bot on 2014-02-14
[18:06] <didrocks> Releasing 0.3+14.04.20140214.1-0ubuntu1
[18:06] <didrocks> mandel: it's in your trunk, so it's in ubuntu :)
[18:06] <didrocks> as easy! :)
[18:06] <mandel> didrocks, sil2100 superb, so know we have the following => lp:~ps-jenkins/ubuntu-download-manager/trusty-proposed
[18:06] <didrocks> (also, you have the email I sent few minutes ago)
[18:06] <mandel> didrocks, sil2100 any idea of that branch?
[18:06] <didrocks> mandel: it's a transit branch
[18:06] <didrocks> while it's published, but not yet in the release pocket
=== alan_g is now known as alan_g|EOD
[18:07] <didrocks> you can ignore it, it will push it everytime to there
[18:07] <mandel> didrocks, I was asking 'cause I saw the email and I was wondering about that branch
[18:07] <mandel> didrocks, ah, ok, so I can tell my brain no to read that, awesome
[18:07] <didrocks> mandel: exactly ;)
[18:07] <didrocks> if that annoys you, I can delete it once it's merged on the release pocket
[18:07] <mandel> didrocks, other question, know when we approve a branch they do not get merged to trunk and we have to do the ci train is that correct?
[18:08] <didrocks> mandel: exactly
[18:08] <mandel> didrocks, I want to make sure that we do not approve anything without doing it correctly
[18:08] <mandel> didrocks, awesome, no need to delete it, I was just curious :)
[18:08] <didrocks> mandel: no, everything's good :) ralsina will be bootstrapped tomorrow on the whole process for your team
[18:08] <didrocks> that should help spreading the info on how that works
[18:09] <didrocks> (we just did it in advance for you last week, before you are bootstrapped)
[18:09] <mandel> didrocks, ok, sounds great, I wanted to really understand the process
[18:12] <didrocks> yeah, I prefer people trying to understand that acking without getting a clue, that always helps :)
[18:39] <dobey> fginther: for https://bugs.launchpad.net/tarmac/+bug/1253770 is just printing the MP URL to STDOUT what you want?
[18:39] <ubot5> Launchpad bug 1253770 in Tarmac "No way to get list of merge proposals" [High,Confirmed]
[19:03] <sil2100> ogra_: hi! I need two packaging ACKs before going EOD ;) You around?
[19:05] <sil2100> cyphermox_: ^ maybe you? :)
[19:05] <cyphermox_> sure
[19:06] <ogra_> ah, thanks
[19:06] <ogra_> :)
[19:07] <sil2100> cyphermox_, ogra_: http://162.213.34.102/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_libdbusmenu-qt_0.9.2+14.04.20140217.1-0ubuntu1.diff and http://162.213.34.102/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_libdbusmenu-qt_0.9.2+14.04.20140217.1-0ubuntu1.diff
[19:10] <cyphermox_> sil2100: isn't that just one?
[19:10] <sil2100> Argh
[19:10] <sil2100> http://162.213.34.102/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_url-dispatcher_0.1+14.04.20140217.1-0ubuntu1.diff
[19:10] <sil2100> cyphermox_: sorry about that, didn't copy what I wanted ;)
[19:12] <cyphermox_> sil2100: libdbusmenu-qt is ok
[19:18] <cyphermox_> sil2100: go for url-dispatcher
[19:20] <sil2100> cyphermox_: thanks!
[19:27] <robru> sweet, internet is officially connected at my new place ;-)
[19:27] <cyphermox_> nice robru
[19:28] <robru> cyphermox_, I'm going to assign silos for 45 and 46
[19:28] <cyphermox_> alright!
[19:30] <robru> thostr_, ping
[19:31] <thostr_> robru: pong
[19:31] <robru> thostr_, landing 45 got silo 3. landing 46 failed to get a silo due to conflicts with silo 5...
[19:31] <robru> silo 5 has a big error, trying to figure out whats gone wrong there...
[19:32] <thostr_> robru: landing 46???
[19:33] <robru> yeah, libdbusmenu-qt appears in both landings. silo 5 needs to get merged & cleaned before landing 46 can be assigned a new silo, but there's some problem.
[19:33] <thostr_> robru: could you check line 42 in the sheet? sheet says nothing but this should have landed by now???
[19:34] <thostr_> robru: line 42 was in silo 4
[19:34] <robru> thostr_, ok checking...
[19:36] <robru> thostr_, looks like that's taken care of. the spreadsheet is in an inconsistent state, but silo 4 has been freed, and I see there's an upload of unity-scope-click from an hour ago
[19:36] <thostr_> robru: perfect. could you quickly reconfig silo 3
[19:36] <robru> thostr_, why, did you change the MPs?
[19:37] <thostr_> because one we figure had a conflict
[19:38] <robru> thostr_, ok
[19:39] <thostr_> robru: was that ok meaning configured or you'll configure?
[19:39] <robru> thostr_, heh. meant "i'll configure" at the time, but it's done now.
[19:39] <thostr_> robru: ok :)
[19:41] <robru> cyphermox_, do you have any idea what's going on in silo 5?
[19:43] <thostr_> robru: cyphermox_: i guess I figured the problem with silo5
[19:44] <thostr_> we did a null merge to get network indicator into ci
[19:44] <robru> thostr_, null merges should be find
[19:44] <robru> fine
[19:44] <thostr_> ah, ok
[19:44] <thostr_> never mind then
[19:44] <robru> thostr_, i'm just checking the archive... looks like *some* of the projects from silo5 are in -proposed as of 20 minutes ago, but not all of them.
[20:06] <bregma> robru, could I get a silo assigned for line 48?
[20:06] <robru> bregma, sure
[20:08] <robru> bregma, silo 4 is yours
[20:08] <bregma> sweet, thanks
[20:17] <robru> i'm stepping out for lunch but feel free to ping me with landing requests and i'll get to them later
[21:02] <robru> back
[21:25] <bregma> robru, until I earn my big-boy pants could you please press the build button for me in silo 4?
[21:26] <robru> bregma, oh sure. have you heard yet when they're training you?
[21:26] <bregma> tomorrow
[21:27] <robru> sweet
[21:27] <bregma> evidently it involves paddles to the britches, I look forward to it
[21:27] <robru> bregma, heh. ok it's building
[21:27] <bregma> thanks
[21:28] <bregma> with FF in a couple days we're going to be landing a lot of stuff
[21:36] <robru> bregma, text conflict in debian/changelog.
[21:37] <robru> bregma, http://162.213.34.102/job/landing-004-1-build/25/console
[21:37] <bregma> urgh
[21:38] <bregma> ah, OK, we landed other stuff today, he's going to have to merge trunk
[21:38] <bregma> lesson learned
[21:45] <bregma> robru, the MP has been updated to fix the conflicts, could be so kind as to restart silo 4 build for me?
[21:45] <robru> sure
[21:48] <robru> bregma, http://162.213.34.102/job/landing-004-1-build/26/console if you enjoy watching paint dry
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
[23:06] <balloons> ping cihelp
[23:06] <balloons> bah, timezones suck