2014/07/01/#ubuntu-ci-eng.txt

[02:33] <fginther> cjwatson, yes, I ran a test with your coverage changes. The MP was updated with the comments.
[03:05] <cjohnston> ~/3
=== josharenson1 is now known as josharenson
[06:58] <tvoss> sil2100, ping
[06:59] <tvoss> sil2100, I need some help with silo 11
=== dbarth-afk is now known as dbarth
[07:09] <thostr_> trainguards: can anybody reconfigure silo 8?
[07:32] <sil2100> tvoss: hi! What's up?
[07:33] <sil2100> thostr_: sure
[07:33] <tvoss> sil2100, some seed changes for silo11 pending, rsalveti is helping out
[07:53] <dbarth> sil2100: hi
[07:53] <dbarth> with traincon-0 lifted, i'd like to resume landing of line 7 (desktop SRU)
[07:54] <dbarth> the branch has been updated and tested, i need a silo to check and land
[07:55] <sil2100> dbarth: hi, let me take a look at that one
[07:57] <sil2100> dbarth: just to make sure - are those changes already in utopic?
[07:59] <dbarth> sil2100: not yet
[07:59] <dbarth> sil2100: that's to land on utopic, and then do the sru
[08:01] <sil2100> dbarth: ok, so you want the silo for line 7 to be assigned for utopic for now, right?
[08:04] <dbarth> sil2100: yes, please
[08:04] <dbarth> sil2100: robru can help us on the SRU side once that's in utopic
[08:09] <jibel> could someone have a look at bug 1336189 ?
[08:09] <ubot5> bug 1336189 in android (Ubuntu) "Device enters a suspend/exit suspend loop" [Undecided,New] https://launchpad.net/bugs/1336189
[08:12] <ogra_> jibel, is that with USB plugged in ?
[08:13] <jibel> ogra_, no, only when I go outside
[08:14] <jibel> ogra_, the test case is basically, put the device in my pocket and have a walk
[08:20] <jibel> ogra_, there might be other condition but I noticed it because last week end after 1h the device was off and the battery empty
[08:21] <ogra_> well i know we have the modem keeping a wakelock (binary blob, we cant do much about that) but that shouldnt drain your battery that heavily
[08:24] <davmor2> ogra_: my battery normally uses between 4-10% over night I was testing tvoss silo so it used a bit more
[08:24] <ogra_> right
[08:25] <tvoss> davmor2, ogra_ but that should really only happen if the positioning is/was used
[08:26] <ogra_> (i have a wireless charger in the bedroom, so my phone charges over night ... )
[08:26] <davmor2> tvoss: I think it use 12-15% instead it might of been other things
[08:27] <davmor2> tvoss: it was still better than the 51% batt drain the other time :)
[08:27] <tvoss> davmor2, ack :)
[08:27] <ogra_> tvoss, so i see your seed change has been taken care of
[08:29] <tvoss> ogra_, yup
[08:31] <sil2100> ogra_: meeting!
[08:31] <ogra_> sil2100, bah ! my phone FAILS !
[08:34] <rsalveti> jibel: ogra_: it's known that wifi is blocking suspend on mako
[08:34] <rsalveti> same for 3g
[08:34] <ogra_> rsalveti, wifi too ?
[08:35] <rsalveti> yup, not that frequently, but yeah
[08:35] <ogra_> ok
[08:35] <rsalveti> Jul 1 08:47:08 ubuntu-phablet kernel: [ 214.162246] wakeup wake lock: msm_hsic_host
[08:35] <rsalveti> in his case
[08:35] <ogra_> ok
[08:36] <rsalveti> happens with android as well
[08:36] <rsalveti> http://forum.xda-developers.com/nexus-4/help/msmhsichost-wakelock-t1999368
[08:36] <rsalveti> it's a firmware issue
[08:36] <davmor2> rsalveti: I know it is prevented from deep sleep
[08:37] <rsalveti> yeah, that's basically this scenario
=== vrruiz_ is now known as rvr
[09:02] <camako> sil2100, landing006 is failing with http://pastebin.ubuntu.com/7730415
[09:02] <camako> sil2100, almost as if there is a newer papi than its trunk
[09:02] <camako> would you please take a look?
[09:02] <sil2100> camako: yes, that's true
[09:03] <sil2100> camako: there is a platform-api in -proposed currently
[09:03] <sil2100> camako: once it migrates out of proposed and then gets merged into trunk, a rebuild should work
[09:03] <camako> sil2100, ok.. Is this expected soon? today perhaps?
[09:04] <sil2100> camako: yes :) Something is blocking it in -proposed, but I'll try getting it migrated somehow
[09:04] <camako> sil2100, where do I look to know it's moved?
[09:07] <cjwatson> sil2100: It's not blocked, it's just landing now
[09:08] <cjwatson> final: location-service,platform-api,qtubuntu-sensors,ubuntu-touch-meta
[09:08] <sil2100> cjwatson: ok, didn't look at update_output yet, just saw that excuses had it as a valid candidate
[09:08] <sil2100> So I was expecting something else blocking it still, but it seems it's moved already
[09:08] <sil2100> cjwatson: thanks!
[09:11] <ogra_> sil2100, brendand, looking at the calendar-app failures they also seem typing input related
[09:12] <sil2100> ogra_: uh, as well?
[09:12] <brendand> ogra_, at least one of them has been around for a while
[09:12] <brendand> the new_event failure. which has a fix in the works
[09:13] <brendand> the other one is new, it might be keyboard related
[09:19] <jibel> ogra_, something else drains the battery. I still have these messages but the discharge rate is ok. I'll continue searching.
[09:21] <ogra_> jibel, great, thanks
[09:27] <sil2100> camako: ok, the platform-api change has been merged into trunk now
[09:27] <camako> sil2100, ok thanks
[09:28] <sil2100> camako: just be aware that platform-api is also in silo 007, which we hope will land today as well - it was an important fix to make our autopilot tests behave better
[09:28] <camako> sil2100.. ok will keep in mind... Thanks for the heads up!
[09:31] <thostr_> sil2100: can I get a silo for line 27
[09:32] <sil2100> thostr_: ok, I see robru didn't assign it because it's locked by silo 008, but I guess it's not a problem in your case right?
[09:32] <sil2100> camako: yw!
[09:33] <thostr_> sil2100: yes, as silo 8 is kind of test silo for time being
[09:33] <sil2100> Assigning
[09:33] <thostr_> sil2100: thanks
=== psivaa_ changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #105 promoted | CI Train Sheriff: trainguards | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[10:10] <rsalveti> sil2100: ogra_: can we trigger a new image soon?
[10:10] <rsalveti> now that location-service and my apparmor related changes landed
[10:11] <ogra_> sil2100, ^^^ ?
[10:11]  * ogra_ wouldnt mind
[10:11]  * sil2100 wouldn't mind as well
[10:11] <ogra_> then let me trigger one
[10:12] <sil2100> psivaa_: do we have complete results for 106 already?
[10:12] <sil2100> ogra_: sure :)
[10:13] <ogra_> triggered
[10:14] <psivaa_> sil2100: not yet, uitk is still running, the rest has finished and there are no surprises
[10:17] <rsalveti> ogra_: thanks
[10:17] <rsalveti> ogra_: and what a game yesterday
[10:17] <rsalveti> was able to see the last 30 minutes
[10:17] <rsalveti> crazy
[10:18] <sil2100> psivaa_: thanks o/
[10:19] <imgbot> === trainguard: IMAGE 107 building (started: 20140701 10:20) ===
[10:54] <oSoMoN> sil2100, c
[10:54] <oSoMoN> sil2100, can silo 2 be published?
[10:55] <nik90_> tedg, charles: With TRAINCON-0 behind, can we get https://code.launchpad.net/~charlesk/indicator-datetime/lp-1318997-customizable-alarm-sounds into a silo and merged today?
[10:57] <nik90_> tedg, charles: I see that it is in landing task 27, thnx
[11:00] <mandel> sil2100, do you think I could get a silo for line 14?? Is kind of urgent for the location work
[11:31] <sil2100> mandel: sure ;)
[11:31] <mandel> sil2100, AWESOME! thx!
[11:32] <sil2100> mandel: oh, it's ready now? :)
[11:32] <sil2100> oSoMoN: looking
[11:32] <mandel> sil2100, -silo 008 thx
[11:34] <sil2100> mandel: ok, so with line 14 the problem is as follows:
[11:34] <sil2100> mandel: there is a lot of components in there that are locked already, sometimes even twice ;p
[11:34] <mandel> sil2100, :-/
[11:35] <sil2100> Let me see how it looks
[11:35] <sil2100> So, for instance platform-api is in 2 silos now ;/
[11:35] <sil2100> I could assign a silo for you, but I just hope we won't loose track of what is where
[11:36] <sil2100> oSoMoN: published :)
[11:36] <sil2100> Thanks!
[11:38] <mandel> sil2100, ok, le me know and I'll do my best to test everything
[11:38] <mandel> sil2100, is a rebuild, that is, only code changes are in dbus-cpp
=== MacSlow is now known as MacSlow|lunch
[11:44] <imgbot> === trainguard: IMAGE 107 DONE (finished: 20140701 11:45) ===
[11:45] <sil2100> \o/
[11:45] <imgbot> === changelog: http://people.canonical.com/~ogra/touch-image-stats/107.changes ===
[11:45] <sil2100> mandel: ok, so... I'll assign a silo, but you make sure you rebuild things if other components land in the meantime, ok?
[11:45] <mandel> sil2100, ofcourse!
[11:58] <Saviq> psivaa_, hey, think I could run the gatekeeper on silo 4?
[11:59] <psivaa_> Saviq: Not sure about ci-train related issues, may be sil2100 knows?
[12:01] <sil2100> What's up?
[12:02] <Saviq> sil2100, just asking whether I can kick http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper to test silo 004
[12:02] <Saviq> it doesn't look busy
[12:02] <Saviq> FYI, really
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #105 promoted | CI Train Sheriff: sil2100 | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[12:02] <Saviq> unless you tell me I can't
[12:02] <sil2100> Saviq: I don't see any reason why not ;) Sure thing, if the CI guys have nothing other pending in there I guess
[12:03]  * Saviq kicked the job
=== alan_g is now known as alan_g|lunch
[12:07] <Saviq> sil2100, can you please dput http://people.canonical.com/~msawicz/qt/ to silo 17 then?
[12:07] <sil2100> Saviq: sure :)
=== psivaa_ changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #105 promoted | CI Train Sheriff: sil2100 | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[12:12]  * sil2100 has to re-sign the package
[12:13] <sil2100> One moment
[12:14] <davmor2> sil2100: 1 pet peeve bug that raised it's head again when I was camping is that Auto download On wi-fi is still ignored meaning people on limited data packages are likely to hit limits
=== psivaa_ is now known as psivaa-lunch
[12:21] <davmor2> tvoss: is gps and location both meant to default to on in the indicator?
[12:21] <tvoss> davmor2, yes, that's fine. Need to track the state correctly -> known
[12:22] <sil2100> davmor2: ouch, for me it's like a really important feature
[12:23] <davmor2> tvoss: okay that's good as long as it is on the list of things to work on :)
[12:23] <tvoss> davmor2, yup
[12:25] <davmor2> sil2100: yeah iirc barry thought the settings app was meant to take care of it because the system-image doesn't know about wifi only connections and setting app team believed that system-image was meant to be handling it
=== MacSlow|lunch is now known as MacSlow
[12:26] <davmor2> sil2100: that was the last time I talked about it at any rate :)
[12:26] <camako> sil2100, unity-mir strangely failed to build in landing-006 due to some "unmet dependencies"... Did I miss something?
[12:29] <sil2100> camako: let me take a look
[12:30] <Saviq> sil2100, oh noes, there's a qtbase change in distro that isn't in kubuntu-packaging https://launchpadlibrarian.net/179076520/qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu5_5.3.0%2Bdfsg-2ubuntu5.diff.gz :|
[12:31] <Saviq> same for qtdeclarative https://launchpadlibrarian.net/179076602/qtdeclarative-opensource-src_5.3.0-3ubuntu5_5.3.0-3ubuntu5.diff.gz :|
[12:31] <sil2100> Oh noes, rsalveti!
[12:31]  * Saviq finds it weird to have the kubuntu branch at all if MPs don't get into it...
[12:32] <sil2100> Yeah... normally Mirv was around to make sure everything is synced up, but he's on holidays still
[12:32] <Saviq> sil2100, what should I do? shall I just rebase on top of the ubuntu source branch or do we want to push to kubuntu somehow/
[12:33] <Saviq> (I can't, not on that team)
[12:33] <rsalveti> sil2100: that's fine, we can just merge that
[12:33] <rsalveti> which package/branches? qtbase and qtdeclarative?
[12:33] <Saviq> rsalveti, yes
[12:33] <rsalveti> lemmelook
[12:34] <Saviq> rsalveti, https://code.launchpad.net/~aacid/kubuntu-packaging/qtdeclarative-opensource-src/+merge/225119 and https://code.launchpad.net/~aacid/kubuntu-packaging/qtbase-opensource-src/+merge/225134
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #105 promoted | CI Train Sheriff: sil2100 | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[12:50] <rsalveti> Saviq: qtdeclarative done
[12:52] <rsalveti> Saviq: qtbase done
[12:52] <rsalveti> Saviq: any other package?
[12:52] <Saviq> rsalveti, nope
[12:52] <rsalveti> cool
[12:52] <Saviq> rsalveti, did you push to ppa or?
[12:53] <sil2100> davmor2: hey! Mister grumpy! How about we check promotion-wise 106? ;) It looks really nice from the autopilot POV
[12:54] <Saviq> rsalveti, ah no, I need to remerge
[12:54] <rsalveti> Saviq: both were already in the archive
[12:54] <rsalveti> Saviq: I just updated the kubuntu branches
[12:54] <Saviq> rsalveti, yeah, I'm taking over now, thanks
[12:54] <rsalveti> yeah, you need to rebase your changes again
[12:54]  * sil2100 sighs
[12:55] <sil2100> Saviq: just give me the packaging branches when you're ready and I'll upload
[12:55] <Saviq> sil2100, ok
[12:55] <rsalveti> yeah, I can upload as well, just didn't know if I should have done that
[12:55] <rsalveti> as I just got the latest ping :-)
[12:55] <sil2100> Will you also upload the -gles version?
[12:56] <rsalveti> sure
[12:56] <rsalveti> I already need to sync them anyway
[12:58] <davmor2> sil2100: 106 or 107?
[12:59] <sil2100> davmor2: I would say 106, as 107 is still under testing
[12:59] <davmor2> sil2100: no worries I'll get on it now
[13:00] <ogra_> sil2100, ugh, gallery app looks really bad
[13:01] <ogra_> (did we discuss the two new errors in 106 this morning ? seems they turned into 10)
[13:01] <barry> davmor2: actually, i think u-d-m is supposed to handle wifi-only.  but i guess we might need to get all three of us together some time to hash that out :/
[13:02] <davmor2> barry: I'm assuming it will be needed for RTM at least
[13:03] <sil2100> ogra_: I remember us looking at those briefly, but yeah... didn't suspect it to change to 10 failures
[13:03] <barry> davmor2: probably
=== alan_g|lunch is now known as alan_g
=== psivaa-lunch is now known as psivaa
[13:32] <barry> davmor2: if we were going to get a meeting together on the subject, who would be the best representative from the system-settings folks?  didrocks?
[13:34] <davmor2> barry: no idea I don't know who works on what.  I think it was seb128 who originally told be that U-S-C should handle if the system is on wifi to auto download.
[13:37] <seb128> davmor2, barry: hey, what's the question?
[13:38] <davmor2> seb128: finguring out who should do what and how on setting auto download to on wifi
[13:39] <davmor2> seb128: for updates
[13:39] <seb128> davmor2, barry: gatox is the one who is doing most of the work on the updates panel, talk to him for that I guess?
[13:39] <davmor2> seb128: thanks dude
[13:39] <barry> seb128: i think we need to get the system-settings folks, mandel for u-d-m, and myself together to figure out how this wifi-only setting is supposed to work
[13:40] <seb128> yw
[13:40] <barry> seb128: ok
[13:45] <mandel> barry, whenever/wheever you need me I'm there
[13:46] <barry> mandel: cool, i'll set something up by email
[13:47] <davmor2> mandel: 10 minutes ago.......this test if he kidnapped the tardis
[13:48] <mandel> davmor2, nah just spanish, we take 10 mins naps between pings ;)
[13:56] <davmor2> hmmmm sil2100 how much do we care about manta?
[13:57] <sil2100> davmor2: it's an officially supported platform so we should care, but I guess it wasn't much usable for a while I remember... what's up?
[13:58] <davmor2> sil2100: on 107 if the system suspends you can't wake it
[13:58] <sil2100> uh
[13:59] <sil2100> davmor2: is that reproducible? And did we have it in 106?
[13:59] <davmor2> sil2100: you just get a black screen no interaction,  I'm going to do a bootstrap on it to 106 and double check, I can't remember if I was testing silos on it or not now
[14:09] <sil2100> ogra_` / ogra_: I won't be around for the evening meeting as always on Tuesdays, could you lead it?
[14:10] <ogra_`> sure
[14:10] <ogra_`> nothing special today i guess ?
[14:11] <sil2100> Yeah, I guess maybe you could discuss promotion of 106 and maybe poke Leo/Brendan about the gallery-app craziness
[14:11] <sil2100> In 107
[14:11] <ogra_`> well, it was there in 106 too
[14:11] <ogra_`> davmor2, could you put special focus on gallery-app testing when doing your dogfood run ?
=== ogra_` is now known as ogra_
[14:12] <davmor2> ogra_: are there any videos on the devices?
[14:12] <ogra_> shouldnt, nope
[14:13] <ogra_> davmor2, oh, you mean in the lab ?
[14:13] <davmor2> ogra_: I just noticed that videos now show in the gallery app which might balls up photo editing
[14:13] <ogra_> ah
[14:13] <ogra_> that might be rsalveti's landig
[14:13] <rsalveti> what
[14:13] <ogra_> he fixed mediascanner permissions
[14:14] <davmor2> ogra_: ie if the test is click on the first image which is meant to be a photo and it is a video it will display different screen
[14:14] <ogra_> right
[14:15] <ogra_> i would expect the test setup to ship the files it needs ... (and that such files get removed when the test is done ... if that didnt happen for some other test there will be videos around)
[14:21] <davmor2> rsalveti: we are just randomly blaming you for stuff ;)
[14:21] <rsalveti> yeah, that's fine
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #105 promoted | CI Train Sheriff: sil2100 | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[14:46] <bfiller> sil2100: can we have silo's for line 28 and 33 please? we're going to ignore the conflict with silo 4 and Saviq and I will manage
[14:48] <sil2100> bfiller: will do after the meeting
[14:49] <bfiller> sil2100: thanks!
[14:50] <boiko> sil2100: thanks
[14:54] <brendand> sil2100, is silo007 getting merged today?
=== dpm__ is now known as dpm
[14:58] <davmor2> sil2100: so fresh install of 106 contact sync and calendar sync don't seem to of happened.  I'm digging into it
[15:00] <davmor2> sil2100: seems cancelling it and starting the sync again is enough so it might just of been a network hiccup
=== Guest38857 is now known as renatu
=== renatu is now known as renato_
=== renato_ is now known as renato__
[15:06] <stgraber> sil2100: ^ hopefully that makes those slightly easier for landers to track
[15:08] <davmor2> sil2100: 106 on manta is good I'll update to 107 again and see if I have the same issue
[15:09] <sil2100> davmor2: ok, thanks!
[15:09] <sil2100> stgraber: \o/
[15:09] <sil2100> stgraber: is it also supporting multiple landers? We allowed multiple landers separated by whitespace or / signs
[15:10] <davmor2> sil2100: on the whole mako 106 has no more issues that 105 that we promoted so I see no reason this couldn't be either.
[15:10] <stgraber> sil2100: yes, it'll show them comma separated
[15:14] <davmor2> sil2100: manta and 107 are not getting on
[15:15] <sil2100> stgraber: excellent ;) Thanks
[15:15] <davmor2> sil2100: I'm updating mako and flo to see if I have  the same issue there
[15:15] <sil2100> davmor2: hm, not good, let me check what happened
[15:15] <sil2100> Ah, we landed the location-bits
[15:15] <ogra_> whats the issue ?
[15:16] <ogra_> (sorry, missing backlog on this machine)
[15:16] <sil2100> ogra_: 107 doesn't seem to wake from suspend on manta
[15:16] <ogra_> i cant really imagine thats a location service thing
[15:16] <brendand> 007 landing \o/
[15:17] <davmor2> sil2100: this is things like click play on a piece of music in the scope then it, it's fine, hit pause however and it goes crazy flashing grey and black, if it suspends you get a grey flash and then it's black and that's it
[15:17] <sil2100> http://people.canonical.com/~lzemczak/landing-team/107.commitlog :|
[15:17] <ogra_> davmor2, does it not wake up or does the screen stay off but you can log in via adb ?
[15:17] <brendand> tomorrow will be a sunny day with rainbows and unicorns
[15:17] <sil2100> brendand: it finally lands?!
[15:18] <brendand> sil2100, why do you seem surprised :)?
[15:18] <sil2100> ricmm, sergiusens: when can I press publish on silo 007?
[15:18] <sil2100> brendand: ricmm mentioned that sergiusens needs to review a branch first for papi or something ;)
[15:18] <sergiusens> sil2100: I think I solved the example test crash
[15:18] <sergiusens> rebuilding to test
[15:19] <sil2100> Awesome
[15:19] <brendand> ooooh, i misread the status
[15:19] <davmor2> ogra_: I think it is awake just displaying a black screen, but the same tests on 106 were fine I'm leaving it plugged in this time see what happens
[15:19] <sil2100> bfiller: assigning silos for you
[15:21] <davmor2> ogra_: ah damn it I bet I left the cable plugged in on 106 now I have the cable in it works fine.  /me resets  to 106 again
[15:22] <stgraber> sil2100: the bot will also now list the LP projects that are part of the silo, I may tweak the format a bit later though
[15:22] <ogra_> davmor2, seems we have seen black screen issues on other platforms too ...
[15:23] <davmor2> ogra_: only seems to be effecting manta for me looking at flo and mako now they both seem fine
[15:23] <ogra_> they use the same graphics HW
[15:23] <ogra_> davmor2, anything in /var/cash
[15:23] <davmor2> ogra_: ah okay
[15:24] <rsalveti> wonder if location service got crazy or similar
[15:24] <davmor2> let me try 106 with no cable again and see what happens
[15:25] <ogra_> davmor2, check /var/crash
[15:26] <davmor2> ogra_: I've triggered a fresh 106 let me  have a look once I know if it is working there
[15:26] <ogra_> ok
[15:26] <ogra_> would be good if any of the new services crash and cause this
[15:27] <ogra_> (i think it is unlikely  though)
[15:29] <davmor2> ogra_: okay so happens in 106 too
[15:29] <ogra_> davmor2, yeah, i suspect it is older
[15:30] <davmor2> _usr_bin_system-settings-wizard.32011.crash
[15:30] <davmor2> _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash
[15:30] <davmor2> _usr_lib_arm-linux-gnueabihf_url-dispatcher_update-directory.32011.crash
[15:30] <ogra_> davmor2, people see it on the nexus5 too
[15:30] <davmor2> ogra_: that is all that is in /var/crash
[15:30] <ogra_> right, doesnt look like anything it couldnt recover from
[15:31] <ogra_> i blame the graphics driver
[15:32] <davmor2> ogra_: I'll show you what happens on the call if you press buttons :D
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #105 promoted | CI Train Sheriff: trainguards | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[15:41] <sergiusens> sil2100: is the choo choo bot dead now that we have the queuebot?
=== gatox is now known as gatox_lunch
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #105 promoted | CI Train Sheriff: trainguards | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[16:17] <dobey> wow this bot is noisy
[16:19] <seb128> who decided to move the bot in there?
[16:40] <stgraber> dobey, seb128: wasn't moved so much as being merged into queuebot but that was something which came up with robru, sil2100, slangasek and barry about some changes wrt the landing team. It's indeed a bit more noisy than we'd like it to be, I need to tweak it so it only posts notices when an action is needed.
[16:41] <davmor2> ogra_: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1336411 for the mail
[16:41] <ubot5> Ubuntu bug 1336411 in unity-system-compositor (Ubuntu) "Manta on recent images doesn't wake correctly from suspend" [High,New]
[16:42] <ogra_> sil2100, ^^^^ for the mail
[16:42] <ogra_> oh, i nearly forgot ...
[16:42]  * ogra_ goes and promotes 106
[16:43] <ogra_> === IMAGE 106 Promoted ===
[16:45] <popey> wow
[16:46] <ogra_> high frequency promoting :)
[16:47] <dobey> davmor2: hah. that's the same bug the nexus5 had, but which seems to be gone now. currently the backlight is staying on even when the screen is off. not sure why it would be doing so though
[16:48] <dobey> davmor2: i filed it as https://bugs.launchpad.net/unity8/+bug/1328146 when i saw it
[16:48] <ubot5> Ubuntu bug 1328146 in Unity 8 "Screen stays off after upgrade to Image #71 on N5" [Low,New]
[16:49] <dobey> don't know if that helps/hurts though
[16:50] <davmor2> dobey: yeah ogra_ already pointed that out, however I've not had issues with manta till recently
[16:50] <davmor2> dobey: so maybe n5 discovered a race that is now being triggered in manta too
[16:52] <dobey> davmor2: maybe
[16:56] <jibel> davmor2, can you confirm bug 1336428
[16:56] <ubot5> bug 1336428 in ubuntu-system-settings (Ubuntu) "system-settings-wizard crashed with SIGSEGV in Wifi setup step" [Undecided,New] https://launchpad.net/bugs/1336428
[16:56] <jibel> ?
[16:57] <davmor2> jibel: give me 5
[16:57] <jibel> very likely a dup of 1334203
=== gatox_lunch is now known as gatox
=== alan_g is now known as alan_g|EOD
[17:20] <davmor2> dobey: https://code.launchpad.net/~albaguirre/unity-system-compositor/fix-1336411/+merge/225209 you might want to try that on n5
[17:28] <dobey> davmor2: hmm, well, it appears to be "fixed" on latest builds on n5, but now the backlight stays on. was the backlight staying on, on manta too?
[17:29] <dobey> anyway, ping me when there's a deb in a silo or something, and i'll be happy to test it to see if there's any change on n5
[17:33] <davmor2> dobey: no backlight is off for me as far as I can tell
[17:36] <dobey> ok
=== dpm is now known as dpm-afk
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #105 promoted | CI Train Sheriff: trainguards | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[18:29] <sil2100> ogra_: thanks!
[18:30] <sil2100> ogra_, davmor2: yay for promotions \o/
[18:30] <ogra_> :)
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #106 promoted | CI Train Sheriff: trainguards | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does. Long mako wait times on s-jenkins.
[18:31] <davmor2> sil2100, ogra_: looks like AlbertA has fixed the manta issue to but I'll test that in the morning now I think to close to EOD and shopping :)
[18:31] <sil2100> davmor2: ACK :)
[18:31] <ogra_> enjoy ... dont spend all your money !
[18:32] <davmor2> ogra_: who enjoys shopping I'd do it online if it wasn't for the wife wanting to go ;)
[18:38] <sil2100> hm, I enjoy shopping myself! I don't buy much, so it's more like window shopping
[18:38] <sil2100> But sadly (or luckily?) my girlfriend hates shopping, so we don't do that too often
=== dpm is now known as dpm-afk
[19:15] <plars> sergiusens: I heard you are working on a fix for the problem where autopilot tests take way longer than they should, do you know how far off that is? I think fginther is having quite a bit of trouble with the stuff on sjenkins from it
[19:15] <sergiusens> plars: silo 7
[19:15] <sergiusens> ready to land
[19:15] <plars> sergiusens: awesome!
[19:16] <sergiusens> well, it's upto the train team now
[19:22] <sil2100> sergiusens: it's marked as 'needs QA signoff' - is that really needed? We're not in traincon right now
[19:23] <sil2100> So, maybe we could simply publish it? You tested it, right?
[19:23] <sergiusens> sil2100: since it affects QA so badly; I thought I set it like that
[19:23] <sergiusens> so they can at least verify
[19:23] <sil2100> sergiusens: I think brendand tested it already previously
[19:23] <sil2100> And said it was ok
[19:24] <sergiusens> sil2100: ok, just consider I did a rebuild after
[19:24] <sergiusens> should be the same in any case
[19:24] <sil2100> sergiusens: right now there's no one assigned to do any QA sign-off, so this landing might be stalled because of this ;)
[19:24] <sergiusens> sil2100: I'll leave it up to you ;-)
=== dpm-afk is now known as dpm
[19:24] <sergiusens> you should have the power to override, right?
[19:24] <sil2100> plars: do you feel lucky today? Should we simply publish the fix? ;)
[19:25] <sil2100> sergiusens: sure
[19:26] <plars> sil2100: sergiusens isn't in the habit of pushing stuff that he hasn't tested, I certainly feel a lot better knowing it came from him
[19:26] <plars> sil2100: was the needs QA signoff because it pertained to autopilot though?
[19:26] <sergiusens> lol
[19:27] <sil2100> Well, anyway I publish it, since as I said QA is not really 'prepared' for any sign-off ;)
[19:27]  * sil2100 closes his eyes and pushes the button
[19:27] <ogra_> SHIPIT !
[19:27] <plars> sil2100: make sure to first say "what could possibly go wrong?"
[19:27] <sil2100> (and well, Brendan gave a +1 on the previous version)
[19:27] <sil2100> Ah, right!
[19:27] <plars> that's QA signoff then :)
[19:27] <sil2100> ...what could possibly go wrong?
[19:27] <sil2100> ;D
[19:28] <ogra_> sil2100, for the next mail ... we dont update the "stable" channel :)
[19:29] <ogra_> it is "devel" (you wrote that in a former mail already and i forgot to ping you about)
[19:29] <sil2100> Ok, published, so now the would should be fixed
[19:29] <sil2100> ogra_: argh! Right! That's what happens when I try to avoid too many 'image promoted' sentences one after another
[19:30] <ogra_> haha, yeah
[19:30] <sil2100> ogra_: then I start inventing sentences which do not particularily make sense ;)
[19:30] <ogra_> no worries ... i just noticed it before
[19:30]  * sil2100 notes it down
[19:41] <sil2100> o/
[20:25] <sergiusens> robru: care for line 35; should be a 15' landing
[20:25] <sergiusens> ?
[21:03] <Saviq> davmor2, you're probably not up for QA sign-off on a silo at this hour are you?
[21:03] <Saviq> unless ToyKeeper you're back around?
=== t1mp_ is now known as t1mp
[22:04] <AlbertA> trainguards: can I get a silo for line 34?
[22:22] <alecu> trainguards: can I ask for these two branches to be added to silo 13? https://code.launchpad.net/~dobey/pay-service/fix-script-path/+merge/225061
[22:22] <alecu> https://code.launchpad.net/~dobey/pay-service/detach-thread/+merge/225220
[23:53] <rsalveti> AlbertA: mind testing/validating silo 07? want to land that asap :-)
[23:53] <rsalveti> brb