[00:21] <ToyKeeper> Yeah, no network indicator.  Woot.  It still works if you access it by sliding from a different indicator though.
[03:24] <imgbot> [03:24] <imgbot> [07:10] <Mirv> sil2100: hey. you probably don't know if the qtcreator go plugin was preNEWed or not? it seems it was published anyhow and after didier poked rsync it's now in NEW queue
[07:10] <Mirv> so if it was not, now it'd need normal new review
[07:35] <sil2100> Mirv: so, I didn't ask Didier to preNEW it yet, but I checked the packaging quickly and it was fine
[07:35] <sil2100> Mirv: not sure if robru found someone for a preNEW
[07:35] <Mirv> sil2100: ok. yeah, there is no comment from robru about preNEWing, so I guess we'd need to ask didier (or some other arch admin) to do proper NEW review on the one that is in queue
[07:36] <sil2100> I explicitly left a comment on the landing that it needs a preNEW, hope robru didn't skip that!
[07:36] <didrocks> hum, I would prefer regular archive admins review it
[07:37] <didrocks> as the normal process "let it in the queue and it will be picked" is supposed to work
[07:37] <didrocks> you can't rely on me forever :)
[07:37] <didrocks> with the train, there is no really need for prenewing anyway
[07:38] <didrocks> it was more for daily-release, as another build would come
[07:40] <sil2100> True true!
[08:08] <ogra_> sil2100, so that slightly messy indicator-network landing broke it it seems ...
[08:11] <cjwatson> plars: it's possible I got some of the fine details of the script wrong, I suppose - check what it produced
[08:14]  * sil2100 sighs
[08:15] <sil2100> ogra_: well, it was the lander's responsibility to test if it doesn't break anything
[08:15] <sil2100> ogra_: I guess that even running unity8 AP tests should have failed for that landing
[08:16] <ogra_> well, it doesnt show up but seems functional
[08:16] <ogra_> and in fact there is no upstart job to start it in the package anymore
[08:18] <ogra_> hmm no, there should be
[08:24] <ogra_> -		stop; exit 0
[08:24] <ogra_> +		if [ "x$UPSTART_EVENTS" != "x" ] ; then
[08:24] <ogra_> +			stop; exit 0
[08:24] <ogra_> +		fi
[08:24] <ogra_> i'm pretty sure this is the issue ...
[08:24] <ogra_> will need to test after the meeting
[08:25] <sil2100> WTF
[08:26] <ogra_> though this should only kick in on non touch sessions ... hmm
[08:27] <ogra_> well ... we'll find out ... i really thought Wellark had tested this though :/
[08:28] <davmor2> Morning all
[08:28] <ogra_> psivaa, both results for 29 and 30 seem to be stuck in "Syncing" on the dashboard
[08:29] <davmor2> popey, sil2100: just updated I don't see nm indicator on the device
[08:29] <davmor2> I do however seem to have the ability to send sms and connect to the internet so I think it is only nm-indicator
[08:29] <davmor2> but you won't be promoting this image
[08:29] <ogra_> davmor2, see backlog :)
[08:29] <sil2100> davmor2: yeah, ToyKeeper already pointed that out on the mailing list, we're discussing this already ;)
[08:29] <sil2100> I don't want to revert the indicator landing, would prefer to just fix it
[08:29] <ogra_> i'll debug this after the meeting
[08:29] <davmor2> sil2100, ogra_: only just logged on
[08:29] <davmor2> :)
[08:29] <psivaa> ogra_: yes, i've asked ev to take a look at the instance where dashboard is running. i could not find any other reasons
[08:30] <popey> davmor2: bug 1319587
[08:30] <davmor2> popey: thanks
[08:34] <Mirv> dbarth: hey! one webbrowser-app landed again. I assigned the next one in order to osomon's "Minor fix for the default UA string on devices". there's another "image download support in browser" pending which is blocked now by that.
[08:38] <nik90> sil2100: hey, we might have a fix for the last alarm clock failure at https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/alarm-dow-fix/+merge/219637. Testing in progress.
[08:47] <Wellark> sil2100, Mirv, didrocks: ok, what's the issue with silo9?
[08:48] <Wellark> people have reported that indicator-network "disapeared" on images 29 and 30
[08:48] <ogra_> Wellark, so after yourt indicator-network change the indicator is gone from the panel ---
[08:48] <Wellark> did the unitu8 package land?
[08:48] <ogra_> nope
[08:49] <Wellark> well, there you go.
[08:49] <ogra_> and i guess we wont land anything til thats fixed
[08:49] <Wellark> well, silo9 contains a unity8 branch for a reason.
[08:49] <ogra_> you mean landing unity8 will fix it ? why were they not in the same silo then ?
[08:49] <Wellark> they are
[08:50] <Wellark> for a reason
[08:50] <ogra_> ah
[08:50] <Wellark> which is exactly that they have to land together
[08:50] <Wellark> and given the reports seems the unity8 branch did not land
[08:50] <ogra_> unity8 needs manual massaging by a release-team person to get out of proposed
[08:50] <Wellark> as if it's missing indicator-network "seems" to have dissaepared
[08:51] <ogra_> right ... looks like a race in the landing process :P
[08:51] <Wellark> we are talking proposed images here, right+
[08:51] <ogra_> Wellark, sorry for blaming you :)
[08:51] <Wellark> please tell me we did not make a promoted image..
[08:51] <ogra_> indeed we do
[08:51] <ogra_> last promoted was 28
[08:51] <ogra_> indicator landed in 29
[08:51] <seb128> ogra_, the packaging should have been adapted with appropriate depends/conflicts/...
[08:51] <ogra_> no worries
[08:51] <seb128> if things were interdependant
[08:51] <Laney> I bumped that version now
[08:52] <ogra_> seb128, tryick for packages that are unity7 and 8
[08:52] <seb128> ogra_, well, it's easy to make i-n breaks on unity8 << new-version
[08:52] <ogra_> seb128, Laney, btw, good to have you here, seems tzdata broke a timezone test in system-settings
[08:52] <seb128> did it?
[08:52] <sil2100> Uh oh
[08:52] <Wellark> seb128: i-n and unity8 do not depend on each other
[08:53] <ogra_> well, at leasst i assume it was that
[08:53] <seb128> Wellark, yet, updating one breaks the other
[08:53] <Laney> link please
[08:53] <Wellark> seb128: well, that's just unfortunate
[08:53] <ogra_> Laney, http://ci.ubuntu.com/smokeng/utopic/touch/mako/30:20140515:20140513.2/8026/ubuntu_system_settings/
[08:54] <ogra_> Laney, thats image 30 ... for 29 we see the same
[08:54] <Mirv> ogra_: I just pinged on #ubuntu-desktop too
[08:54] <Mirv> and filed a bug
[08:54] <Laney> At first sight I would not jump to the conclusion that this is caused by tzdata
[08:54] <Wellark> the real question here is why the unity8 from silo9 did not hit proposed
[08:54] <ogra_> Mirv, awesome,. thanks
[08:54] <Mirv> unity8 is in proposed, but it's stuck there
[08:54] <Mirv> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity8
[08:54] <ogra_> Laney, well, it started to show up after this changeset: http://people.canonical.com/~ogra/touch-image-stats/29.changes
[08:55] <Mirv> sil2100: was there still some special thing to do with unity8?
[08:55] <ogra_> Laney, if you see something else that could be at fault ... go for it :) seemsed tzdata was an obvious candidate
[08:55] <ogra_> *seemed
[08:55] <Wellark> what does this message mean?
[08:55] <Laney> The test is checking that you see the right text when nothing is entered in the search field
[08:55] <Wellark> In silo landing-009. Migration: One package at least is not available at the destination. unity8 (7.86+14.10.20140514.1-0ubuntu1) is in the proposed pocket.
[08:55] <Laney> So that seems very unlikely to me
[08:56] <Wellark> Mirv: devel-proposed images are built from proposed? right?
[08:56] <ogra_> well, it started reliably after the abvopve image changes ... not saying it must be tzdatza :)
[08:56] <Wellark> so at this point I don't care if unity8 is stuck there
[08:57] <ogra_> just smelled very related that a tz test fails after tzdata changed
[08:57] <Wellark> I need to know why didn't the unity8 package from silo9 hit proposed
[08:57] <sil2100> Mirv: no, we should be fine :)
[08:58] <sil2100> Laney: thanks for the version bump!
[08:58] <ogra_> sil2100, so lets have one image right after unity8 landed ... then i'll do the AP seed change and lezs have another one
[08:58] <Laney> sure
[08:59] <Wellark> sil2100, Mirv, didrocks: could someone please answer my question --^
[09:00] <Mirv> Wellark: no, the devel-proposed means it's proposed for evaluation and promotion to another channel, not that its packages would come from -proposed
[09:00] <sil2100> Wellark: ah!
[09:00] <sil2100> Wellark: sorry, missed your ping, unity8 was blocked in -proposed because there's an additional step that has to be performed with each unity8 release
[09:01] <Mirv> sil2100: didn't you just answer to me that "no, we should be fine" regarding special things/extra steps? ;)
[09:01] <sil2100> Mirv: that step has been done ;) Laney bumped the version didn't he? ;)
[09:02] <ogra_> Wellark, it *did* hit proposed ... it just didnt hit anything after this ;)
[09:02] <Mirv> sil2100: ok! so then it's stuck for some reason on build-depending on libunity-mir1 on the powerpc/ppc64el/arm64
[09:02] <Wellark> Mirv, sil2100: ok. thank you. then why was indicator-network moved out of proposed before unity8 that was explicitly on the same silo?
[09:02] <Mirv> Wellark: they aren't protected on that level unless a versioned dependency is added in packaging
[09:02] <ogra_> Wellark, unity8 needs special love from an archive admin to go from -proposed to the archive
[09:02] <Mirv> sil2100: oh, ok! now valid candidate.
[09:02] <Mirv> so it'll go in now.
[09:03] <ogra_> Wellark, you are missing a dependency to prevent it from moving alone
[09:03] <sil2100> Mirv: yep :)
[09:03] <Mirv> and we can launch an image build
[09:03] <ogra_> right
[09:03] <Wellark> Mirv: ok. fair enough. would have guessed the -proposed -> proper would be a manual or semi manual process as well.
[09:03] <ogra_> only for cewrtain packages
[09:04] <Wellark> these are both ci-train packages
[09:04] <ogra_> most of them move automatically ... unity8 is speacial ...
[09:04] <ogra_> so you need to add a dependency like seb128 mentioned above
[09:04] <ogra_> then indicator-network will be held back together with unity8 next time
[09:05] <Wellark> ok. that is not going to happen. as there is no dependency chain between individual indicators and unity8 which provides the indicator rendering
[09:05] <ogra_> just add that dependency with your next change ...
[09:05] <Wellark> and this kind of a "breakage" only happens if the "protocol" is modified
[09:05] <ogra_> err, there obviously is
[09:06] <ogra_> you just hit an issue because of it :)
[09:07] <dbarth> Mirv: hi, what would you like me to do with the webbrowser-app landings?
[09:08] <cjwatson> Wellark: that's what Breaks is for
[09:08] <ogra_> if a certain version of unity8 provides a needed protocol you need to have a dependency saying "only install me if at lest unitzy8 version xyz is availeble"
[09:08] <seb128> well, when a "protocol" change, you need to rename a binary, or use conflicts or something to ensure the clients of the protocols get updated in sync
[09:08] <ogra_> *available
[09:08] <seb128> what cjwatson said
[09:08] <Mirv> dbarth: tell/decide if that osomon's landing is good to go next while bfiller's can wait
[09:09] <dbarth> ok, checking
[09:09] <cjwatson> (I'm assuming that there's something else that depends on both indicator-network and unity8, so that the Breaks will be effective for proposed-migration)
[09:09] <ogra_> Wellark, you just say "breaks with anything before xyz" ... next time your protocol changes you bump that "before xyz"
[09:09] <Mirv> dbarth: in addition to that, would you like to work on landing "Corrective silo for OA" today? robert earlier removed the silo. we're still low on silos, but your request is still quite early so it'd be fine if it can be worked on today.
[09:09] <ogra_> that will guarantee that your protocol is in sync
[09:09] <cjwatson> Or you use Provides to declare a protocol version, and declare Breaks on the old versions (if it's suitably numbered)
[09:10] <cjwatson> (might be too much effort if the protocol isn't already versioned)
[09:10] <dbarth> Mirv: you did well to put it aside
[09:11] <dbarth> i'm just tying to land online account stuff and alex's manifest stuff as well
[09:12]  * Mirv merge & cleaning silo 009 now
[09:13] <sil2100> o/
[09:14] <sil2100> Mirv: do you know what that ghost landing is ;p ? By ghost landing I mean, there is a ghost as the lander
[09:14] <dbarth> Mirv: so, let bill's request pass
[09:14] <sil2100> Mirv: line 37
[09:14] <dbarth> Mirv: the whitespace fix is not a critical bug AFAICT
[09:14] <dbarth> Mirv: and the branch from Alex on silo 17 can also wait, we'll rebuild after bill's branch lands, no wories
[09:14] <dbarth> Mirv: all set?
[09:15] <Mirv> sil2100: haha! ;) oops.
[09:15] <sil2100> Mirv: now it's less spooky, thanks ;)
[09:16] <Mirv> dbarth: ok, so I'll assign silo to bill's branch instead of osomon's, thanks.
[09:20] <ogra_> Wellark, bug 1319728
[09:20] <cjwatson> sil2100: There's no EMEA webops vanguard coverage this week
[09:21] <cjwatson> err, echan, sorry
[09:25] <didrocks> sil2100: do you want me to deploy it? At least, that would be done, the only difference is that the new field will be mandatory until the plugin lands
[09:25] <sil2100> didrocks: if there is no risk involved, then let's deploy :)
[09:25] <didrocks> sil2100: yeah, keep me posted at your first publication :)
[09:27] <didrocks> sil2100: the charm will be needed to be updated to include the plugin though
[09:28] <didrocks> sil2100: deployed
[09:30] <sil2100> \o/ :)
[09:33] <sil2100> ogra_: so, rmadison says unity8 is in the archive now - did you kick a new image?
[09:33] <ogra_> not yet ... doing so now
[09:34] <sil2100> Thanks :)
[09:34] <psivaa> sil2100: so, dialer and messaging_app tests came back green with 30 on the rerun. but filemanager still had a failure
[09:34] <sil2100> psivaa: thanks, filemanager seems to have become a bit more flaky after the new AP it seems
[09:35] <ogra_> well, lets see with the python3 stuff
[09:36] <ogra_> i suspect we run the wrong tests in some places with the py2 bits installed
[09:39] <imgbot> [10:14] <sergiusens> sil2100 Mirv can you reconf silo 003 for me?
[10:14] <sil2100> sergiusens: reconfigure
[10:22] <sergiusens> sil2100: yes, reconfigure
[10:23] <sergiusens> I have this conflict with packaging practices; the golang packaging status quo, defacto in debian is to prepend golang- to the source package name; this is sort of in conflict with citrain it seems
[10:24] <sergiusens> I guess you'll just force me to change the source package name, so I guess I'll just do that
[10:24] <sergiusens> :-/
[10:27] <Mirv> :) I'm not sure what sort of citrain policy you're thinking about though.
[10:28] <dpm> hi all, is it a known issue that on image #28 the volume buttons don't work?
[10:28] <dpm> on a N4, that is
[10:29] <sergiusens> Mirv: the one where lp:branchname == source package name ;-)
[10:29] <sergiusens> Mirv: I couldn't reconf because I have lp:udm (to go get launchpad.net/udm), but named the source package golang-udm
[10:32] <didrocks> you should be able to, it's just a warning telling you are a bad confusing upstream :)
[10:32]  * didrocks has saw so many people bzr branch lp:<source_package_name> that I think it's valuable to match
[10:38] <sergiusens> didrocks: it doesn't let me reconf though ;-)
[10:39] <sergiusens> didrocks: I'm following policy now fwiw
[10:39] <didrocks> sergiusens: hum, it's a bug though, do you have the output?
[10:39] <didrocks> I can probably fix it
[10:39] <sergiusens> didrocks: it's in the choo choo
[10:39] <didrocks> well, a direct link will be appreciated :)
[10:40] <sergiusens> didrocks: (07:13:34) CI-SNCF: sergiusens (landing-003): Reconfigure failed: udm was not in the initial list of components for that silo. You can't reconfigure the silo yourself. Please ask the landing team to reconfigure it for you. (https://ci-train.ubuntu.com/job/landing-003-0-reconfigure/17/console)
[10:40] <didrocks> great
[10:40] <didrocks> and udm was in the initial list?
[10:41] <sergiusens> didrocks: lp:udm, yes; I didn't change the list; I only hit reconf because I don't like the ci bot message saying I rebuilt in the changelog, when the only reason I wanted to rebuild was to get a nicer changelog
[10:41] <sergiusens> yeah, I know, I'm a changelog freak
[10:41] <didrocks> sergiusens: if you just provide "udm" in the rebuild list, you don't need a reconfigure
[10:42] <didrocks> and it won't say "rebuilt force"
[10:42] <didrocks> fored*
[10:42] <didrocks> forced*
[10:42] <didrocks> in your changelog :p
[10:42] <sergiusens> didrocks: oh, interesting
[10:42] <didrocks> sergiusens: partial rebuilds of a stack (so explicit) is always possible
[10:43] <didrocks> but interesting, so there is obviously a bug in the reconfigure, it shouldn't then end up into that situation
[10:43] <didrocks> sergiusens: mind opening a bug? I may look at it whenever I can
[10:43] <didrocks> or if sil2100 beats me to it :)
[10:43] <didrocks> he needs to get his hand dirty a little bit in the train I think :p
[10:43]  * sil2100  in a meeting ;)
[10:43] <sergiusens> didrocks: where against? cupstream2distro still?
[10:43] <didrocks> sergiusens: yeah, cupstream2distro
[10:44] <didrocks> ok, so, first assignement was https://ci-train.ubuntu.com/job/prepare-silo/406/console I guess
[10:44] <didrocks> with: WARNING:root:Project name (udm) doesn't align with the source package name (golang-udm)
[10:46] <didrocks> sergiusens: ok, found the bug, not really sure how to fix it in a elegant way for now
[10:47] <sergiusens> didrocks: parse debian/control for Vcs-Bzr ?
[10:47] <didrocks> sergiusens: not resilient enough
[10:47] <didrocks> oh, I've got all needed infos actually
[10:48] <didrocks> sergiusens: mind if I reconfigure your silo?
[10:48] <sergiusens> bug 1319771
[10:48] <didrocks> not sure if you started to build yet
[10:48] <sergiusens> didrocks: yeah, but let me fall back to the original state, one sec
[10:48] <didrocks> sure
[10:51] <sergiusens> didrocks: good to go
[10:51] <didrocks> let's see…
[10:53] <didrocks> sergiusens: ah, this was before the new package name
[10:54] <didrocks> sergiusens: so, yeah, in that case, it will ask for someone to reconfigure
[10:54] <didrocks> but if you package name stays stable
[10:54] <didrocks> and package name != source branch name
[10:54] <didrocks> you will be able to self-reconfigure
[10:54] <didrocks> (which is the main case)
[10:54] <didrocks> I pushed the fix for it
[10:55] <didrocks> so let's try, I'm reconfiguring as the admin for your new package name
[10:55] <didrocks> and then, self-reconfigure
[10:57] <didrocks> sergiusens: here we go: https://ci-train.ubuntu.com/job/landing-003-0-reconfigure/20/console
[11:00] <sergiusens> oh, success, nice
[11:01] <sergiusens> I guess I should start a faq
[11:01] <sergiusens> didrocks: is most of this codebase migrating to the airline?
[11:01] <sil2100> I guess they have their own codebase
[11:01] <sergiusens> sil2100: might be imported :-)
[11:02] <sil2100> ;)
[11:02]  * sil2100 is back from meetings
[11:02] <didrocks> sergiusens: they are stealing pieces
[11:02] <didrocks> sil2100: FYI ^
[11:02] <didrocks> and everytime I do a relevant changes, I'm pinging them
[11:02] <sergiusens> yeah, this first part makes sense, and francis is familiar with it
[11:23] <sergiusens> didrocks: sil2100 I'm a bucket of problems today: https://ci-train.ubuntu.com/job/landing-003-1-build/49/console
[11:24] <sil2100> Looking
[11:24] <sergiusens> and these are the contents of my MP http://bazaar.launchpad.net/~sergiusens/udm/empty/revision/3
[11:25] <sergiusens> I honestly don't want to bring in issues :-) I swear!
[11:25] <sil2100> I wonder why the changelog looks so broken! As if there was some merge conflicts ;p But I don't see any message about that
[11:26] <ogra_> because it is CI :P
[11:26] <ogra_> all CI changelogs are a mess
[11:26] <didrocks> well, try the merge yourself…
[11:26] <didrocks> you will see a conflict
[11:26] <didrocks> rather than ogra_ being wrong and ranting wrongly
[11:26] <didrocks> http://people.canonical.com/~didrocks/citrain/silos/landing-003/udm/debian/changelog
[11:26] <sil2100> Ag
[11:26] <didrocks> is the result of merging your branch into it
[11:26] <ogra_> didrocks, well, i only see the output on -changes ... with lots of duplication etc
[11:26] <didrocks> ogra_: so it's rather people editing the changelog manually whic hare doing mess
[11:26] <sil2100> Forgot about the rsync mirror!
[11:26] <didrocks> ogra_: patch welcomes
[11:27] <ogra_> peope should just use dch proper in their commits :P
[11:27] <didrocks> ogra_: see, they don't, like this conflict ^
[11:27] <ogra_> and assemble a sane changelog
[11:27] <ogra_> yeah
[11:28]  * ogra_ will happily refuse to go through any debian/changelog enntries in five years when we need to find whom to attributs a certain change to because microsoft sued us or some such :P
[11:29] <sergiusens> didrocks: but everything below Initial packaging is autogenerated
[11:29] <davmor2> ogra_: somewhere is there a list of the images that got promoted from 1
[11:29] <sergiusens> didrocks: I thought if we provided a changelog it would not try and generate one
[11:30] <didrocks> sergiusens: it doesn't for this commit
[11:30] <ogra_> davmor2, yes, but that wont help if the chanelog attributes the changes to "CI Bot"
[11:30] <didrocks> sergiusens: it will for the previous ones
[11:30] <didrocks> since the latest release
[11:30] <ogra_> davmor2, you need a proper changelog in the package to have proper histroy ...
[11:30] <didrocks> ogra_: a bug that you are welcome to investigate
[11:30] <didrocks> ogra_: but you still have bzr commit authors anyway
[11:31] <ogra_> didrocks, yeah, i know ... if i ever find that much spare time i probably will :)
[11:31]  * didrocks is seeing so much negativness, it's tiring
[11:31] <didrocks> really dude…
[11:31] <didrocks> same for me
[11:31] <didrocks> but you have time to rant though
[11:31] <davmor2> ogra_: no I need a list to updat julien on what blockers were present in each promoted image.  I thought he only wanted it doing for the end of Trusty.  It turns out he wants it forever :)
[11:31] <ogra_> until then i'll just make sure to not be involved in that future lawsuit ;)
[11:31] <didrocks> anyway, back to work
[11:31] <sergiusens> didrocks: heh, the reason I wanted to do this was because I had 2 'Initial packaging', one from the commit message and another from the debian/changelog
[11:31] <ogra_> davmor2, ugh
[11:31] <sil2100> sergiusens: let me take a look at the exact mechanism
[11:32] <ogra_> davmor2, i guess you can only go through didrocks and sil2100's landing mails then
[11:32] <didrocks> sergiusens: yeah, hence the conflict, you can tag a release if you want to avoid that, but you will need a changelog entry with it
[11:32] <davmor2> ogra_: I know the blockers I just need to know the images that were promoted :)
[11:32] <ogra_> i doubt you will find any other summary of blockers despit that
[11:32] <didrocks> anyway, i'll let sil2100 guiding you, he has enough info
[11:33] <davmor2> I'll go through the mails :)
[11:33] <ogra_> davmor2, ah thats easy ...
[11:33] <sergiusens> sil2100: yeah, if I have a list of DOs and DONTs or point me to the code and I'll use that as my guideline :-)
[11:33] <ogra_> davmor2, http://system-image.ubuntu.com/ubuntu-touch/trusty/mako/index.json ... all promoted trusty images ... just grep for "description:"
[11:34] <davmor2> ogra_: cool thanks
[11:34] <ogra_> davmor2, http://system-image.ubuntu.com/ubuntu-touch/utopic/mako/index.json ... same for utopic
[11:35] <davmor2> ogra_: ah yeah trusty we have Utopic is the ones I'm after ta
[11:38]  * ogra_ wonders why imgbot didnt notify about 31 yet ... seems to be done ... 
[11:39] <ogra_> imgbot, stunt
[11:39]  * imgbot rolls on its back and purrs
[11:39] <ogra_> hmm, still alive
[11:40] <ogra_> oh, it was actually reconnecting exactly when the build finished ... bah
[11:40] <ogra_> [11:40] <ogra_> [11:51] <Mirv> dbarth: FYI your SRU bug is unverified https://bugs.launchpad.net/bugs/1302780 so it hasn't gone in even though it's 14 days old
[11:57] <sil2100> brb!
[11:59] <Mirv> dbarth: you can btw follow these things on http://people.canonical.com/~ubuntu-archive/pending-sru.html - green ones (=verification-done) with days >= 7 will be handled by the SRU team and migrate to release pocket
[12:03] <sil2100> sergiusens: give me some moments regarding that problem, ok :) ? Need to context switch for a small moment
[12:06] <davmor2> ogra_, sil2100: the unity8 fix doesn't show wifi/3g on the phone signal bars
[12:06] <davmor2> oh and now wifi is turned off again by default I'm assuming 3g might be the same
[12:06] <ogra_> sigh
[12:07] <davmor2> turned on wifi now I see it in the indicator
[12:07] <ogra_> sounds like the same issue we have with manta then
[12:08] <sil2100> geh
[12:08] <sil2100> Then even good that I didn't consider promoting anything today
[12:08] <sil2100> davmor2: after rebooting it's the same?
[12:09] <davmor2> sil2100: lunchtime i'll reboot it as I go down to eat and let you know when I get back
[12:09] <ogra_> sil2100, so i assume the fix lies somewhere between cyphermox and Wellark :)
[12:10] <sil2100> ;)
[12:10] <sil2100> Damn, have to jump out for lunch as well, didn't eat breakfast yet
[12:10]  * ogra_ has to go afk for a while too 
[12:10] <sil2100> davmor2: give us a sign after lunchtime, we then fill in a bug and poke those two bad persons
[12:13] <dbarth> Mirv: can i just mark the package verified? or i have to resubmit fully
[12:14] <dbarth> cause i can attest the fix works and doesn't create regressions; so will mark it done as well
[12:19] <sergiusens> sil2100: no worries
[12:20] <cjwatson> unity8 should no longer require manual attention from #ubuntu-release
[12:21] <ogra_> yay !!!
[12:22] <cjwatson> (tested as best I can considering, but do let me know if the next one explodes ...)
[12:34] <asac> manual attention for unity8 by ubuntu-release? anything interesting was going on there?
[12:38] <sil2100> yaay!
[12:38] <sil2100> cjwatson: thanks ;)
[12:39] <davmor2> sil2100: same thing after a reboot
[12:39] <sil2100> asac: yeah, so normally an additional step was required every time a new unity8 was released
[12:39] <sil2100> davmor2: uh, sucks... could you fill in a bug for easy tracking?
[12:40] <davmor2> sil2100: on it
[12:40] <sil2100> Thanks :)
[12:40] <cjwatson> asac: a hack to cope with a weird special case that I've now buried a bit more competently
[12:40] <asac> i like buried :)
[12:41] <asac> might eventually allow us to hire into roles like "technical archeologists", which could be a first :)
[12:42] <cjwatson> I kind of feel that's what my job already is half the time. :-)
[12:42] <cjwatson> "so, um, what did we intend by this ten years ago"
[12:43] <dbarth> sil2100: o/ silo 16 ready to land
[12:44] <sil2100> dbarth: awesome! Will publish after done with lunch
[12:45] <Mirv> dbarth: the SRU is process is there that once the fix goes into -proposed, someone installs it specifically from there, tests it, and marks it as verification-done. so it's not related to our landing (it has already landed), but whether the final SRU step of copying from -proposed to -updates happens or not
[12:46] <dbarth> Mirv: i know but was (again) trying to get external feedback
[12:46] <dbarth> but happy to mark verification-done myself
[12:47] <dbarth> thanks for the dashboard link btw, that really helps
[12:47] <Mirv> dbarth: yeah, it's sometimes hard to get as the people experiencing the bug might not necessarily find the LP bug or the SRU guidelines on how to proceed
[12:47] <Mirv> dbarth: you're welcome
[12:48] <sil2100> Mirv: will you publish silo 16;) ?
[12:48] <sil2100> Mirv: if you have a free moment
[12:49] <Mirv> sil2100: yes I was just going once more through the MP:s of it, actually
[12:50] <Mirv> err...
[12:50] <Mirv> /tmp/hudson1545565889933478490.sh: line 4: BUILD_USER_ID: unbound variable
[12:50] <Mirv> sil2100: are you aware of any recent changes to the code?
[12:50] <Mirv> https://ci-train.ubuntu.com/job/landing-016-2-publish/16/console
[12:51] <didrocks> argh, that wouldn't work then as long as we don't have the plugin
[12:51] <didrocks> I can fix that
[12:51] <didrocks> however Mirv, you should really read that channel :p
[12:51] <davmor2> sil2100: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1319812
[12:52] <didrocks> or, it's better for it to fail, it shouldn't fail if you set the value
[12:52] <didrocks> Mirv: did you set the launchpad user name id?
[12:52] <didrocks> see the new field
[12:56] <didrocks> yeah, confirmed it won't fail if you use the parameter
[13:00] <didrocks> sil2100: any news on the plugin deployement?
[13:01] <didrocks> Mirv: still with us? I'll leave for some exercise in 10 minutes, all good for the publication now?
[13:10] <didrocks> I take that as a yes :) away now.
[13:11] <sil2100> :)
[13:11] <sil2100> didrocks: so, still lunch, but working on that with webops and Evan
[13:11] <ogra_> asac, note that this had its good and bad sides ;) we found a good bunch of missing or broken dependencies over the last weeks due to unity8 being held :)
[13:11] <Mirv> didrocks: :) ok
[13:12] <ogra_> the last one just today
[13:12] <asac> cjwatson: cool, shall i change your title :)?
[13:12] <asac> hehe
[13:12] <asac> i think its like ying and yang
[13:12] <ogra_> yeah
[13:12] <asac> where there are architects, there need to be archeologists :)
[13:12] <Mirv> oh, now I connect the discussion to the actual result
[13:12] <asac> black matter
[13:13] <ogra_> it surely makes a good business card entry :)
[13:13] <didrocks> Mirv: so, just use your launchpad name until the plugin is installed in that field
[13:13] <didrocks> Mirv: then, you won't need it apart if you sponsor for someone else
[13:13] <didrocks> like there is a packaging change and you ack it
[13:13] <asac> Chief Technical Archeologists - call me when you lost sight of whats going on and i will dig through your dirt :)
[13:13] <ogra_> CTA :)
[13:14] <Mirv> didrocks: thanks!
[13:14] <didrocks> yw! hoping everything is fine :p
[13:14] <didrocks> ah, no, there is a typo (weird, it passed pyflake…)
[13:15] <cjwatson> asac: I will probably cope with it as it is :)
[13:15] <Mirv> (now I got AttributeError: 'module' object has no attribute 'get_person')
[13:15] <didrocks> yeah
[13:15] <Ursinha> Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: -
[13:15] <Ursinha> argh
[13:15] <didrocks> Mirv: I don't know why, it's obviously there…
[13:17] <didrocks> Mirv: bah, I prefer to not comment, let me redeploy
[13:19] <didrocks> Mirv: https://ci-train.ubuntu.com/job/landing-016-2-publish/18/console
[13:19] <didrocks> you have packaging changes :)
[13:19] <Mirv> new package!
[13:20]  * didrocks really away
[13:20] <Mirv> not really "No change rebuild" as it didn't exist earlier :S
[13:21] <davmor2> ogra_: that json was perfect thanks :)
[13:21] <ogra_> welcome :)
[13:21] <Mirv> mardy: do you have a summary of the story behind signon-apparmor-extension? looks like it has code history from last Autumn but it's not actually in the archives?
[13:21] <davmor2> all up-to-date again now 1 task less
[13:22] <didrocks> Mirv: you are picky, it's clearly a "no change rebuild"! :)
[13:23]  * didrocks goes ;)
[13:23] <Mirv> dbarth: or you ^ it says "No change rebuild" while I don't find a trace of existing signon-apparmor-extension anywhere
[13:23]  * Mirv doesn't believe the really really goes anymore
[13:25] <dbarth> Mirv: the no change rebuild was to ensure that the multi-arch changes problem we had the other day on one package, was not hiding another porblem due to other m-a changes
[13:25] <dbarth> Mirv: so mardy recommended to rebuild all packages that depend on the location of .so and plugin files, and veify that they keep working as well
[13:26] <Mirv> dbarth: the thing is that a package called signon-apparmor-extension does not exist in Ubuntu before...
[13:26] <dbarth> we went from /usr/lib/signon something to /usrlib/<arch>/signon
[13:26] <dbarth> uh
[13:26] <dbarth> hmm
[13:27] <dbarth> mardy: is that one a new package? ^^
[13:28] <Mirv> I need to quit though, so I'll let sil2100 and robru (when around) continue with that, but if it's truly a new package a "initial version" would be better description than "no change rebuild" :) the packaging should also be reviewed.
[13:28] <mardy> Mirv, dbarth: mmm... it may be that it never went to the archive, yes
[13:29] <dbarth> ah, so needs paperwork to be added i guess
[13:31] <ogra_> sil2100, so seems 31 is mostly done with testing ... shouldi upload the seed change to drop teh py2  AP bits now and trigger a new build ?
[13:35] <mardy> sil2100: please let me know if there's something I should do about signon-apparmor-extension
[13:40] <xnox> ogra_: mediascanner1 is still on the images, is that expected?
[13:41] <xnox> ogra_: at the moment it FTBFS and thus keeps holding boost1.54 on touch images.
[13:41] <ogra_> xnox, yeah, there was something still needing it ...
[13:41] <xnox> =(
[13:41] <ogra_> but i'm not up to date on that ... might have changed ... last time i talked about it with someone was about 6 weeks or more ago
[13:41] <davmor2> popey: by the way thanks for adding the videos for the messaging app bug
[13:42] <ogra_> (i forgot whom i talked about to)
[13:42] <Mirv> mardy: sil2100: now I do the same as Didier and not keeping my promises of going away, but with some quick testing there are no lintian errors or warnings, nothing seems wrong with packaging, copyrights look good. but since this was a bit quick glance, I don't hit publish yet.
[13:42] <Mirv> (now that preNEW is not really needed anymore apparently, there wouldn't be a problem otherwise but just let it go through normal NEW review)
[13:43]  * Mirv really really etc
[13:45] <ogra_> xnox, grilo-plugins-0.2-mediascanner keeps it in ... but that has no rdepds ...
[13:45] <xnox> ogra_: no rdeps... do clicks use it?
[13:46] <xnox> ogra_: well, it's not seeded in the sdk =)
[13:46] <xnox> ogra_:
[13:46] <xnox> # music-app is using mediascanner 1 and grilo. So seeding them for now
[13:46] <xnox>  * mediascanner
[13:46] <xnox>  * grilo-plugins-0.2-mediascanner
[13:46] <ogra_> ah, yeah
[13:46] <xnox> ogra_: has music-app been fixed to use mediascanner 2 and not use grilo?
[13:47] <ogra_> good question
[13:47] <ogra_> i think the music scope used to use it too
[13:47] <asac> i had mediascanner crashes again on my phone
[13:47] <ogra_> but that was probably before we switched to the new scopes
[13:47] <asac> (just a sidecomment, ignore for CI/LT)
[13:47] <ogra_> asac, stop listening to that weird music that ... that confuses it ;) )
[13:48] <ogra_> *then
[13:48] <asac> ogra_: funny thing is that i dont have a single media on device :)
[13:48] <asac> ogra_: all i did was taking two test photos (if thats realted)
[13:48] <ogra_> ah, thats the issue then :P
[13:49] <ahayzen_> xnox, we're currently migrating to mediascanner2 now
[13:49] <asac> for (*i=0; *i<1; i++) :)
[13:49]  * ogra_ wonders where sil2100 is gone
[13:50] <asac> ogra_: need him?
[13:50] <ahayzen_> xnox, this is our WIP branch https://code.launchpad.net/~music-app-dev/music-app/use-mediascanner2.0/+merge/214140
[13:50] <ogra_> asac, i want a "go" for the python2 drop ... but that can surely still wait until he returns
[13:50] <sil2100> You need me?
 sil2100, so seems 31 is mostly done with testing ... shouldi upload the seed change to drop teh py2  AP bits now and trigger a new build ?
[13:51] <xnox> ahayzen_: mediascanner fails to build from source in utopic at the moment (no-change rebuild), failures in the test-suite.
[13:51] <ogra_> from above :)
[13:51] <sil2100> It seems my notification on nick is down, service died
[13:51] <ahayzen_> xnox, once that is in grilo can be removed \o/
[13:51] <xnox> ahayzen_: is anyone looking into that or do you want me to open a bug about it?
[13:51] <sil2100> ogra_: ah ha!
[13:51] <ahayzen_> xnox, is that mediascanner 1 or 2?
[13:51] <xnox> ahayzen_: mediascanner1
[13:51] <sil2100> ogra_: so...
[13:52] <ahayzen_> xnox, hmm well we'll likely be moving off it very soon, i'm not sure who is/was working on it?
[13:52] <sil2100> ogra_: I see the tests are rather ok, so yeah, please proceed with the seed update and let's kick a new image!
[13:52] <ogra_> hmm, seems the "syncing" issue is still there with 31
[13:52] <xnox> ahayzen_: ok.
[13:52] <ogra_> sil2100, thanks !
[13:53] <sil2100> mardy: let me take a look
[13:53] <ahayzen_> xnox, is it affecting you guys with anything or can it stay on its current build?
[13:54] <ogra_> ahayzen_, there is a policy to remove binaries that cant be built from source ... but if it is planned to go away asap that can probably slip for a few days
[13:55] <xnox> ahayzen_: it's using boost1.54, and needs a rebuild against boost1.55. It's one of the last 5 packages holding up boost1.54 in the archive. (out of total 205, most of which use boost1.55 by now)
[13:57] <ahayzen_> ogra_, xnox, ok with our current plans we hope to merge it next weekish so shouldn't be too long hopefully
[13:57] <asac> ahayzen_: FTBFS should be the highest priority level we have ... its the stereotype of "grave" basically :)
[13:58] <ogra_> asac, well, this is "FTBFS of something planned to be dropped soon"
[13:58] <asac> so next week we drop it?
[13:58] <ogra_> i wouldnt call it grave if "soon == berarble timeframe"
[13:58] <asac> thats fine then
[13:59] <ogra_> yeah, next week sounds cool ... if xnox can live with that
[13:59] <ahayzen_> ogra_, xnox, the last item we have is supporting genres, but mediascanner2 doesn't have any genre models (jamesh is working on adding these) but victor is also investigating if there is a workaround until then so can speed up the migration..then once AP tests pass we're good to go
[14:02]  * ogra_ dedicates the recent ubuntu-touch-meta upload to xnox 
[15:09] <ogra_> triggering a build for image 32
[15:09] <ogra_> sil2100, ^^^
[15:14] <imgbot> [15:15] <xnox> ogra_: that's very bad, and will break AP tests =) thanks for not following the landing plan for dropping python2, ahead of everything being in place.
[15:15] <xnox> ogra_: as discussed in #ubuntu-meeting right now.
[15:15] <sil2100> \o/
[15:15] <ogra_> xnox, yes, i see that, robru pinged me, subscribed me to a MP and referred to barry that these two packages need to be dropped asap
[15:16] <bzoltan> sil2100:  any chance to win a silo for the line38?
[15:16] <ogra_> xnox, i can roll that back ... i only reacted to these requests
[15:16] <cjwatson> I can just add ~ps-jenkins to a team to allow the CI Train to upload a package whose trunk is owned by that team, right?
[15:17] <ogra_> xnox, what else should i do but react to the lander and developer requesting that change from me ?
[15:17] <xnox> ogra_: check the related blueprint, ask for the testing plan, which is written down in the blueprint.
[15:17] <popey> davmor2: lock your device then unlock your phone/tablet with two fingers.
[15:17] <popey> davmor2: do you get this.. welcome stuck half out.. http://popey.mooo.com/screenshots/device-2014-05-15-161700.png
[15:18] <ogra_> xnox, i would expect both of these persons to know theior landing plan
[15:18] <xnox> ogra_: talk to people assigned to drop python2 from touch images in a coordinated manner?
[15:18] <ogra_> xnox, which i thought barry was
[15:18] <bfiller> sil2100: silo 1 ready to be released
[15:18] <sil2100> bfiller: o/
[15:18] <bzoltan1> seb128: I do not want to be pushy :)
[15:18] <xnox> ogra_: between barry, myself and thomi we did agree on the landing plan, and it's me who is suppose to land ubuntu-touch-meta update, when ready.
[15:18]  * sil2100 is getting pings back
[15:18] <sil2100> bzoltan: will try ;)
[15:19] <xnox> ogra_: please wait for me to respond when reverting changes from one person, upon request from somebody else.
[15:19] <xnox> ogra_: or we can release 3 clicks very quick and keep everything as is.
[15:19] <ogra_> xnox, ok ... i'll revert the change in image 33 then
[15:19] <xnox> ogra_: trunks of gallery-app, camera-app and sudoku-app need to be in-store and on image.
[15:19] <xnox> ogra_: if you can land all of those three clicks in store for image 33, no revert will be needed.
[15:19] <ogra_> xnox, oh, they are there already ? then we should probably do that
[15:20] <ogra_> yeah
[15:20] <ogra_> sounds better
[15:20] <xnox> ogra_: what do you mean "there" =)
[15:20] <ogra_> we'll just have bad results in 32 ... i'll make sure everyone is aware
[15:20] <xnox> ogra_: their trunks are all correct.
[15:20] <ogra_> thats what i mean with "there" ;)
[15:20] <xnox> ogra_: but the clicks on image, where not up to date. I don't know what needs to happen to land those.
[15:20] <ogra_> i.e. we can land them and its all fixed
[15:21] <xnox> ogra_: right. if we have a store uploader, approver and the AP tests pass.
[15:21] <ogra_> sergiusens, ^^^^ can we land gallery-app, camera-app and sudoku-app today ?
[15:22] <bfiller> sil2100: also need a reconfigure on silo 8 to add address-book (new MR added) once silo 1 clears
[15:23]  * barry waves
[15:23] <sergiusens> ogra_: xnox ... popey is testing the clicks on the store
[15:23] <xnox> sergiusens: \o/
[15:23] <sergiusens> they are already in the store
[15:23] <ogra_> awesome
[15:23] <sergiusens> barry: ^^
[15:23] <sil2100> bfiller: ok, I'm reviewing the packaging changes right now in silo 001
[15:23] <bfiller> sil2100: thanks
[15:23] <sergiusens> ogra_: wrt to sudoku I had no request; Mirv can also upload fwiw
[15:23] <ogra_> ok
[15:24] <barry> is there anything i can help with?
[15:24] <ogra_> looks like we are all sorted now
[15:24] <barry> rock on
[15:25] <slangasek> what's the status, then?
[15:25] <sergiusens> ogra_: do you want me to upload a new sudoku? I don't have time to test, so it will be a blind upload
[15:25] <sil2100> ogra_: do you have a moment for a little packaging ACK? :) https://ci-train.ubuntu.com/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_address-book-app_0.2+14.10.20140514-0ubuntu1.diff and https://ci-train.ubuntu.com/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_telephony-service_0.1+14.10.20140514-0ubuntu1.diff <- new binary package, dependency added to it - looking good and saf
[15:25] <slangasek> pushing to get the clicks landed, AIUI
[15:25] <xnox> barry: maybe i'm out of date, but two things didn't happen yet: there are 3 remaining clicks not declaring py3 compat as shipped on the image (all correct in their trunks)
[15:25] <ogra_> slangasek, we need to land the remaining three click packages which are in the store already
[15:25] <xnox> barry: and autopilot-legacy didn't gain python-evdev dependency, which i'm uploading now.
[15:25] <slangasek> ok
[15:25] <sergiusens> slangasek: camera and gallery need store approval
[15:25] <slangasek> sergiusens: so, who does that?
[15:25] <sergiusens> and sudoku I wasn't aware of, so uploading now
[15:25] <ogra_> slangasek, popey
[15:26] <sergiusens> slangasek: store approvers, popey is one of them
[15:26] <slangasek> popey: ^^ can you help us get some click apps landed?
[15:26] <sergiusens> I used to be one, but I think I was booted :-P
[15:26] <popey> slangasek: specifically?
[15:26] <barry> xnox: odd about ap-legacy.  i thought that was working, but thanks for uploading the new version
[15:26] <xnox> sergiusens: *naughty*
[15:27] <slangasek> popey: camera and gallery - not sure if these are currently awaiting approval or if an upload needs to happen first, I guess sergiusens will have the details
[15:27] <popey> camera I have tested but there's a problem with the store, bueno needs to fix..
[15:27] <sergiusens> slangasek: he's already looking into those two ;-)
[15:27] <popey> gallery is autopilot testing right now
[15:27] <barry> xnox: of the three remaining, you say they're correct in trunk, so no new uploads are necessary?
[15:27] <sergiusens> oh, darn
[15:28] <xnox> barry: they are correct in trunk, but tests are executed based on the manifest from the click from the pre-installed image.
[15:28] <popey> sudoku will be next.
[15:28]  * barry nods
[15:28] <xnox> barry: those are only updated, if and only if a click from trunk is generated, uploaded into the store and approved there.
[15:28] <xnox> barry: and the last bits didn't happen yet.
[15:28] <barry> xnox: and that's gallery, camera, and sudoku as being discussed above?
[15:29] <ogra_> yep
[15:29] <xnox> barry: yeap.
[15:29] <barry> cool
[15:29] <davmor2> popey: sorry just got your ping let me try on n7 my n4 is tied up at the moment
[15:29] <popey> n7 is where I saw it
[15:29]  * barry hears johnny cash singing folsom prison blues
[15:30] <barry> "I hear the train a comin' It's rolling round the bend"
[15:30] <barry> is there anything else that needs to happen to remove py2 from touch?
[15:30] <xnox> barry: all of above to land, and spin an image with everything in place. as far as we can tell.
[15:31] <ogra_> well
[15:31] <ogra_> theroetically ... py2 should be gone from the image that is just building right now
[15:31] <ogra_> (which then will fail the tests fro the tree apps above)
[15:32] <xnox> ogra_: and all .deb python2 AP tests will fail as well due to http://launchpadlibrarian.net/175659410/autopilot-legacy_1.4.1%2B14.10.20140430-0ubuntu1_1.4.1%2B14.10.20140430-0ubuntu2.diff.gz not on that image.
[15:33] <davmor2> popey: on what image?
[15:33] <popey> uh #22
[15:34] <davmor2> popey: ah hang on then
[15:39] <popey> 3 test failures on gallery here.
[15:39] <popey> on image #22
[15:40] <xnox> popey: and did they all pass with currently released/approved gallery-app?
[15:40] <popey> http://paste.ubuntu.com/7468360/
[15:40] <xnox> popey: because gallery-app only changed manifest key, and it otherwise should be identical to the currently approved one.
[15:40] <popey> yes
[15:40] <popey> last approved gallery-app was a month ago
[15:41] <ogra_> note that we have a constant failure oin gallery since a while in the automated tests
[15:41] <popey> 16:00:26 < bfiller> popey: I believe gallery will have a known failure that we are still working on
[15:41] <ogra_> but thats only one
[15:41] <xnox> popey: image 22? i have image 31 locally
[15:41] <popey> i have multiple devices. happy to re-test on something newer to see if it's better
[15:42]  * popey does that
[15:42] <bfiller> ogra_: yup, we're working on that one
[15:42] <ogra_> yeah :)
[15:43] <xnox> bfiller: just one, or 3 as per http://paste.ubuntu.com/7468360/ ?
[15:43] <popey> sil2100: i have another urgent meeting so will miss landing call in 15 mins
[15:43] <ogra_> xnox, http://ci.ubuntu.com/smokeng/utopic/touch/mako/31:20140515.1:20140513.2/8028/gallery_app/
[15:43] <sil2100> popey: ok, no worries
[15:43] <ogra_> thats the last automated test run for gallery
[15:43] <sil2100> No promotions today anyway
[15:43] <ogra_> only add_photo fails
[15:43] <xnox> ogra_: thanks.
[15:44] <sergiusens> popey: xnox: i think this upload also has the QA refactors and they were fully passing, alas on python 2
[15:45] <sergiusens> oh, and py3
[15:45] <xnox> sergiusens: failures are interesting, something to do with toolbar not getting opened or closed when properly needed.
[15:45] <sergiusens> xnox: popey yeah, I'm fairly certain it's probably due to the uitoolkit changes for the new toolbar header/bottom swipe
[15:46] <ogra_> xnox, fyi ... https://code.launchpad.net/~robru/ubuntu-seeds/drop-python2/+merge/219617 whats what i got pointed to ...
[15:46] <popey> kk
[15:46] <sergiusens> popey: I ran the tests for these for you already https://myapps.developer.ubuntu.com/dev/click-apps/144/changerequest/ ;-)
[15:47] <ogra_> xnox, "... now that all autopilot tests have migrated to python3" kind of made me think it was ready :) ... (additionally to the IRC pings i got abnout it over night)
[15:47] <popey> sergiusens: yay, now just waiting on these gallery ones finishing and the store being fixed
[15:47] <xnox> ogra_: and why did you land that without a review?! =)
[15:47] <xnox> ogra_: please follow processes.
[15:47] <sergiusens> popey: what's the store issue btw?
[15:48] <popey> "Changes can not be accepted and published at this time. Please try again later.
[15:48] <popey> "
[15:48] <ogra_> xnox, what should i review there ? its a seed change ... and i have to trust the guys managing that
[15:48] <ogra_> xnox, admittedly i didnt know you were the autoritative instance here ... next time i'll check and ask
[15:49] <xnox> ogra_: remember when you had a "heart-attack" about me changing the seed and uploading meta adding those deps?
[15:49] <ogra_> xnox, yes, thats why i know that these are the bits we need to remove as the last step :)
[15:49] <xnox> ogra_: it was explicitely to avoid the current breakage: when autopilot & clicks land asynchronosly and not in the right combination yet.
[15:50] <xnox> ogra_: how did you know we are at the last step?
[15:50] <xnox> ogra_: are you at all involved in how many steps there are?
[15:50] <ogra_> xnox, i didnt, i relied on barry and robru
[15:51] <barry> i thought everything was in place to tweak the ap dependencies, which i thought was the last step.  unfortunately, it's a very complex stack of packages and process
[15:52] <ogra_> barry, right ... and i was expecting your lander (rob) to know ...
[15:52] <xnox> ogra_: next time, i'll just revoke your upload rights =))))))))))) </kidding>
[15:52] <sil2100> uh
[15:53] <boiko> sil2100: hey, bfiller mentioned a dialer-app failure yesterday, is it still happening on smoke tests? I couldn't reproduce it locally
[15:53] <xnox> barry: "$ adb shell click list --manifest -- and search for missing x-test keys" =) as per blueprint.
[15:53] <ogra_> xnox, well, i think this is a serious problem we need to find a solution for ... i kind of have to trust the landers, else i will have to verify their work twice and three times which just wastest manpower
[15:53] <barry> xnox: right.  we did that a few weeks ago
[15:53]  * ogra_ thinks thats a discussion we all should have together over a drink in malta :)
[15:54] <popey> \o/ Beer
[15:54] <ogra_> with an idea for a better plan
[15:54] <popey> http://drool.popey.com/
[15:54] <xnox> barry: ... and at the time there were still missing things.
[15:54] <sil2100> boiko: hi! Yes, but it's a flaky test it seems - I'll fill in a bug soon, but it seems sometimes we get a failure in test_call_log_item_opens_messaging
[15:54] <xnox> barry: on image 31 http://paste.ubuntu.com/7468461/ camera, gallery, sudoku  are not correct yet.
[15:55] <sil2100> boiko: it's happening quite frequently in smoketesting
[15:55] <sil2100> boiko: but re-runs usually help
[15:55] <barry> xnox: yes, i just verified that on #29
[15:55] <xnox> barry: i should have added a comment to execute that in the seed comment next to python-autopilot.
[15:55] <boiko> sil2100: I tried to run the smoketest script locally multiple times, no single failure :/
[15:55] <sil2100> grrr :|
[15:55] <sil2100> boiko: you can see it here for instance: http://ci.ubuntu.com/smokeng/utopic/touch/mako/28:20140514.1:20140513.2/8015/dialer_app/
[15:56] <sil2100> boiko: maybe you'll be able to read out something from the failure...
[15:56] <sergiusens> sil2100: any luck with my silo? I was thinking of just asking ogra_ to dput directly for the initial package as well
[15:56] <ogra_> i'm fine with that ... it will be held in NEW anyway
[15:56] <ogra_> and get an extra review
[15:56] <boiko> sil2100: so, from the failure it seems the history database is not being correctly replaced when starting the test, but I can't figure out a case where this could be happening
[15:57] <davmor2> sil2100: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1319906 this is wifi off by default on 31 the other bug is now for the missing icon for 3g/utms
[15:57] <sergiusens> popey: heh,  had that issue before :-P
[15:57] <sil2100> sergiusens: I found the problem in citrain, but I'm thinking of a way to work-around it - the thing is that the case of 'a new package without any versions tagged' is a bit tricky ;)
[15:58] <ogra_> sergiusens, the http://drool.popey.com/ issue ?
[15:58] <sil2100> davmor2: thanks! :)
[15:59] <sil2100> sergiusens: give me like up to 30 mintues after the meeting and if I don't find an easy workaround, let's have ogra_ dput directly :)
[15:59] <boiko> sil2100: so, if it happens again, would you mind pinging me?
[15:59] <ogra_> oh,,. meeting ...
[15:59] <sil2100> boiko: sure, let me check if it happened in the latest image
[16:00] <bzoltan1> seb128:  do you see any chance to promote the qtcreator-plugin-go package still today? It would be cool to demo it on Monday on Malta for folks who are interested about Go-QML.
[16:00] <sergiusens> sil2100: thanks, just drop me a comment before you eod
[16:09] <popey> sergiusens: bfiller 4 gallery failures on #31 http://paste.ubuntu.com/7468524/
[16:10] <sergiusens> popey: I'd still let it in, but that's just me
[16:10] <sergiusens> popey: an autopilot failure indicates a regression not necessarily against the component it belongs to ;-)
[16:10] <xnox> i see FAIL: gallery_app.tests.test_album_view.TestAlbumView.test_add_photo
[16:11] <xnox> which is a known failure, what are the other 3?
[16:11] <bfiller> popey: yuck
[16:15] <bfiller> popey: are you talking about http://ci.ubuntu.com/smokeng/utopic/touch/mako/31:20140515.1:20140513.2/8028/? I see only one failure
[16:15] <bfiller> popey: or it's latest with python3 change?
[16:16] <xnox> bfiller: popey is talking about http://paste.ubuntu.com/7468524/ i see only one "FAIL:" yet autopilot summary at the end reports 4.
[16:16] <popey> bfiller: it's gallery revno 967 with image #31
[16:16] <xnox> bfiller: currently running tests locally as well to see what's going on.
[16:17] <bfiller> popey: does that correspond with bzr rev 967? just trying to understand exactly what's in it. trunk is rev 972 so would have expected that
[16:19] <popey> bfiller: i just tested what was uploaded to the store, which was 967, if you want 972 tested, sergiusens should upload that
[16:19] <sergiusens> 972 won't work with py3
[16:19] <popey> camera 269 approved
[16:20] <bfiller> sergiusens: thought we needed 972 to have python3??
[16:20] <dbarth> sil2100: o/ if you have a silo, i have line 16 which was ready and free to go no
[16:20] <bfiller> I'm confused
[16:20] <dbarth> now
[16:20] <sergiusens> popey: bfiller oh, ic...
[16:20] <sergiusens> other way around
[16:20] <sergiusens> bfiller: I was confused, not you...
[16:21] <bfiller> sergiusens: ok :)
[16:21] <bfiller> sergiusens: then we should upload 972 to store and test that right?
[16:21] <xnox> well i'm running 972 from http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/ on image #31 on mako at the moment.
[16:21] <xnox> it's still going....
[16:21] <sergiusens> bfiller: yeah
[16:21] <xnox> sergiusens: what's the difference between gallery-app-click & gallery-app-click-from-branch ?
[16:22] <bfiller> xnox, sergiusens : ok, once we validate that please upload to the store
[16:22] <sergiusens> xnox: since it can't be built in a chroot I added a job for people to build random branches
[16:22] <sergiusens> xnox: cross built that is
[16:23] <xnox> sergiusens: ah, cool. so i am using "the right one", that is gallery-app-click for the purposes to upload into the store?
[16:23] <popey> sergiusens: ping me when you need more testing done.
[16:23] <sergiusens> xnox: you can upload, right? I'll leave that to you
[16:23] <popey> or xnox ☻
[16:23] <sergiusens> popey: we should confide in xnox's results
[16:23]  * xnox moment of truth
[16:23] <xnox> pulling the logs....
[16:24] <popey> if someone else tests it and it passes I'm happy ☻
[16:24] <xnox> Ran 37 tests in 848.781s
[16:24] <xnox> FAILED (failures=3)
[16:24] <sergiusens> popey: he already is...
[16:24] <sergiusens> there we go
[16:25]  * xnox needs autopilot guru help =)
[16:26] <ogra_> and thomi isnt here
[16:26] <ogra_> xnox, probably elopio could help
[16:27] <elopio> xnox: I can probably help. Are you testing the gallery app?
[16:27] <elopio> also rvr can help with that.
[16:28] <elopio> no, sorry, robotfuel, not rvr :)
[16:28] <xnox> elopio: yes, in all of our logs generated we have e.g. 3 or 4 failures, yet only one "FAIL:". What are the other failures?
[16:28] <xnox> e.g. http://paste.ubuntu.com/7468524/
[16:28] <xnox> ah, they are ERRORS:
[16:29] <xnox> ERROR: gallery_app.tests.test_albums_view.TestAlbumsView.test_add_album_and_cancel
[16:29] <xnox> ERROR: gallery_app.tests.test_picker_mode.TestPickerMode.test_pick_named_photo
[16:29] <robotfuel> xnox: there is a real bug in the gallery app
[16:29] <xnox> ERROR: gallery_app.tests.test_photo_viewer.TestPhotoEditor.test_photo_editor_redo_undo_revert_enhance_states
[16:29] <robotfuel> at least when I checked yesterday there was
[16:31] <bfiller> artmello: ^^^^
[16:32] <sergiusens> robotfuel: in current gallery or proposed?
[16:32] <bfiller> robotfuel, xnox, artmello : the bug we know about is this https://bugs.launchpad.net/gallery-app/+bug/1319927 which should only cause one test to fail
[16:32] <sergiusens> reason I mention is that, if it's from before, we should just upload this new gallery
[16:32] <sergiusens> as it brings in py3 tests
[16:32] <bfiller> artmello: have you seen these other failures? http://paste.ubuntu.com/7468524/
[16:33] <sergiusens> or live with py2 for a couple more weeks if you want
[16:33] <bfiller> sergiusens: think we need to understand if py3 causing those additional failures as they weren't there yesterday
[16:33] <bfiller> but maybe something else has changed
[16:33] <sergiusens> bfiller: when this was tested back then, there were no errors
[16:34] <artmello> bfiller: no I haven't seem them
[16:34] <sergiusens> bfiller: I recall robotfuel saying he tested with py3 and so did I (with py2)
[16:34] <robotfuel> I am in a meeting I'll comment when I am out
[16:35]  * xnox is rerunning tests with both python2 and python3, will file logs on launchpad when complete.
[16:35] <xnox> bfiller: in addition to that one, we see 3 additional ERRORS aka autopilot exception StateNotFoundError.
[16:36] <bfiller> xnox: might mean the app is getting hung due to the first failure
[16:36] <bfiller> that's my guess
[16:37] <xnox> bfiller: oh, are CI not using phablet-test-run? or e.g. executing each test sequentially / restarting?
[16:37] <bfiller> xnox: hmn, not sure actually. maybe that's not the problem
[16:38] <robotfuel> bfiller: I thought the app restarted with each test
[16:38] <bfiller> you're right
[16:39] <imgbot> [16:39] <imgbot> [16:39] <robotfuel> Is failure this testing proposed image? if I flash my phone with today's image will I see it?
[16:40] <robotfuel> is this failure
[16:40] <robotfuel> my mouse jumped
[16:42] <bfiller> robotfuel: get the click from here: http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/ as it has the changes necessary to make it run with py3
[16:42] <bfiller> robotfuel: trying to verify if the failures are related to py3 or not
[16:43] <davmor2> ogra_, sil2100: image 29 has no indicator on mako at all
[16:43] <robotfuel> bfiller: I tested py3 on both the phone and the desktop and it worked
[16:43] <balloons> didrocks, perchance you are still about. Can you tell me why you removed the sphinx docs from uitk? http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/975
[16:43] <sil2100> davmor2: right, since unity8 is missing there - but do you have wifi network enabled?
[16:43] <davmor2> ogra_, sil2100: sorry it just has no image, the network indicator is there and shows wifi
[16:43] <didrocks> balloons: see the commit message :)
[16:44] <didrocks> "remove the doc generation for UITK autopilot emulator. Autopilot is in universe for now, it needs MIRing first
[16:44] <didrocks> "
[16:44] <balloons> didrocks, what is MIR?
[16:44] <davmor2> sil2100: also my mom has just sent 2 sms so network for that is working
[16:45] <sil2100> davmor2: oh, thanks
[16:45] <sil2100> ogra_: ^
[16:45] <sil2100> ogra_: so it must be broken in 31..?
[16:45] <xnox> balloons: https://wiki.ubuntu.com/MainInclusionProcess
[16:45] <didrocks> thanks xnox :)
[16:45] <davmor2> sil2100: also in the setting app I see connections
[16:46] <xnox> didrocks: it's funny how it's MIR yet wiki page describing it is MIP =)
[16:46] <xnox> balloons: MIR - Main Inclusion Report, a set of criteria that needs to be fulfilled for a package to be available in main.
[16:46] <didrocks> xnox: yeah :)
[16:47] <xnox> balloons: packages in main, may only build-depends & depends & recommends packages in main.
[16:47] <davmor2> sil2100, ogra_: want me to bootstrap 30
[16:47] <sil2100> davmor2: could you do the same for 30 and then 31? Just to make sure
[16:47] <davmor2> doing it now then
[16:50] <ogra_> xnox, hmm http://people.canonical.com/~ogra/touch-image-stats/32.changes ... interesting ... something keeps python2-autopilot in place despite unseeding
[16:50] <xnox> ogra_: interesting, let me check.
[16:53] <ogra_> sil2100, so it seems that this new libconnectivity-cpp0 might have something to do with it ...
[16:54] <ogra_> which means 30 and 31 should be broken the same way as 29
[16:54] <xnox> well python-evdev removal will fail deb based python2 tests, however many we have of those left.
[16:55] <xnox> but autopilot-legacy upload is fixing that, thus if -proposed is enabled they'll be fine.
[16:55] <xnox> or it will fix itself once arm64/powerpc builders catch up.
[16:55] <xnox> but it shouldn't affect an image at, once landed.
[16:55] <sil2100> ogra_: but hm, davmor2 said that 29 wasn't broken
[16:56] <sil2100> ogra_: he said that he had wifi when bootstrapping #29
[16:56] <ogra_> sil2100, because it didnt have the full landing
[16:56] <ogra_> iirc the indicator didnt even start on 29
[16:56] <sil2100> Not sure, I think it was there, but not visible? Or am I misunderstanding now, hm
[16:57] <ogra_> it seem that this new lib is for making the indicator manage the connections ... so when the indicator was fixed it startd using this
[16:57] <sil2100> hah
[16:57] <sil2100> Ok, then I know now why you're suspecting connectivity-api
[16:57] <ogra_> (thish is still total guesswork, but it seems veryy likely that this is involved)
[16:57] <sil2100> Yeah, it does look as a possible culprit
[16:58] <ogra_> i know cyphermox now will take a look (despite being overly busy with other stuff), we should know more in a while
[16:58] <davmor2> ogra_: there are no icons on 29 but Indicator-network showed if you dragged down from the top and swiped across
[16:59] <sil2100> ogra_: ^ so hm, it's strange, since duh the unity8 change related to connectivity-api seems really not regression-prone
[16:59] <ogra_> davmor2, right ... then 30 had no changes and 31 had the final bits for that indicator landing
[17:00] <davmor2> hmmm 30 isn't coming up
[17:01] <sil2100> davmor2: what do you mean?
[17:01] <sil2100> davmor2: no network or no nothing?
[17:01] <ogra_> patience
[17:01] <davmor2> ah there we go just taking it's time
[17:01] <ogra_> yeah
[17:02] <ogra_> confidence :)
[17:02] <xnox> autopilot-qt has a stray dependency.
[17:02] <ogra_> meow
[17:02] <ogra_> :)
[17:03] <davmor2> Okay so image 30 no indicator images, Swipe down from the top and I have network listed and it shows wifi, Settings → wifi shows available aps
[17:03] <davmor2> onto 31
[17:03] <ogra_> right, 30 was nearly identical to 29
[17:04] <ogra_> only hadd apport changes
[17:04] <sil2100> Right, wanted to make sure
[17:05] <ogra_> so if you revert unity8 on 31 ... that shoould theoretically get it working again
[17:07] <davmor2> ogra_: but then you have no icons right
[17:07] <ogra_> right
[17:07] <ogra_> but are also using the old connectivity-api
[17:07] <cyphermox> so after flashing, wifi is off, but that's expected
[17:07] <davmor2> ogra_: also the no network in setting app only seems to affect flo and manta so lets see if mako is the same before we go reverting things
[17:08] <ogra_> cyphermox, thats a regression
[17:08] <cyphermox> ogra_: well, no
[17:08] <cyphermox> I mean, it's disconnected
[17:08] <ogra_> cyphermox, well, yes :) it behaves differently to how it did before ... unannouced
[17:08] <cyphermox> the switch in the indicator in 32, on mako, is ON
[17:08] <ogra_> oh
[17:08] <ogra_> and you can connect ?
[17:08] <davmor2> in 32
[17:08] <xnox> py2 -> 2 failures, py3 -> 4 failures, in gallery-app latest.
[17:08] <cyphermox> I have scan results, but nothing is connected since I never entered anything
[17:09] <davmor2> we were on 31
[17:09] <xnox> *sigh* will debug this later tonight.
[17:09] <ogra_> cyphermox, wow, did you do a clean bootstrap install ?
[17:09] <xnox> ogra_: apart from gallery app nothing should be broken on image 32 after autopilot-legacy gets into the release pocket.
[17:09] <xnox> (thus if something deb based fails it would need a retry later)
[17:09] <cyphermox> ogra_: yes
[17:09] <ogra_> xnox, awesome, so i should not need to roll back ?
[17:09] <ogra_> cyphermox, that is strange
[17:10] <xnox> ogra_: no need to rollback.
[17:10] <cyphermox> ogra_: so far, it's the expected behavior
[17:10] <ogra_> yay
[17:10] <davmor2> ogra_: I haven't tested 32 only 31
[17:10] <ogra_> cyphermox, sounds like ... why do we see it broken on 31 then
[17:10] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/32.changes
[17:10] <davmor2> So maybe 32 fixed it
[17:10] <ogra_> how ?
[17:10] <xnox> ogra_: and well gallery-app is broken. but we are actively trying to land/update that at the moment.
[17:10] <davmor2> ogra_: magic
[17:10] <ogra_> via whoopsie ?
[17:10] <cyphermox> wait
[17:10] <xnox> ogra_: and it must to promote an image.
[17:10] <cyphermox> this is only first boot
[17:11] <cyphermox> so I successfully connected to wifi, so far so good. Now I'll reboot the phone
[17:11] <ogra_> xnox,  we wont promote anythign today anymore so we have tomorrow to fix it
[17:11] <ogra_> cyphermox, well, we had people without either wlan or 3G after fresh boot before ...
[17:11] <ogra_> on 31
[17:11] <ogra_> 32 has no related changes ... so it should be broken the same way
[17:12] <davmor2> cyphermox: manata and flo have no network at all
[17:12] <cyphermox> well, you can't possibly get connected on first boot with wifi unless you touch something
[17:12] <ogra_> also davmor2 sees no wifi settings at all in the system-settings app on flo and manta anymore
[17:12] <ogra_> while mako seems to have them
[17:12] <cyphermox> it's not going to magically choose a network to connect to
[17:12] <ogra_> yeah
[17:12] <cyphermox> I don't have a manta or flo, so I can't say about though
[17:12] <cyphermox> *those
[17:12] <ogra_> yeah, indeed
[17:13] <cyphermox> so on reboot, mako is properly connected to both gsm and wifi
[17:13]  * ogra_ doesnt get that ... 
[17:13] <ogra_> right
[17:13] <cyphermox> mako is good with networking, I can confirm this
[17:13] <davmor2> ogra_, cyphermox after tea I'll do fresh bootstraps on flo and manta
[17:13] <ogra_> davmor2, can yo also try 32 ?
[17:13] <cyphermox> should I try an earlier image?
[17:13] <kgunn> cyphermox: robru ...2 items when you get a chance, first reconfig on silo6 (i added qtubuntu rebuild), second can i get a "test only" silo for line 35 ?
[17:13] <ogra_> even though it is totalyl beyond me why 31 should be any different to 32
[17:13] <ogra_> cyphermox, well, davmor2 sees 31 broken
[17:13] <davmor2> ogra_: will do but again after tea need to eat now :)
[17:14] <cyphermox> ogra_:  on mako?
[17:14] <kgunn> greyback: ^ like so
[17:14] <ogra_> yeah
[17:14] <cyphermox> how do I go about specifying the image I want to install?
[17:14] <ogra_> --revision i think
[17:14] <cyphermox> ok
[17:14] <davmor2> cyphermox: give me one second and I will take a screenshot as soon as it comes up
[17:14] <davmor2> --revision=xx
[17:15] <cyphermox> flashing 31 now...
[17:15] <cyphermox> I really need to get my hands on one or both of the other devices
[17:16] <robru> kgunn, sorry we are totally out of silos, but I can reconfig silo 6 for you sure
[17:16] <kgunn> robru: thanks!
[17:16] <ogra_> asac, is there a chance we can get the networking guys more devices (flo/manta) ... awe and cyphermox both only have a mako
[17:16] <davmor2> cyphermox: http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-181553.png
[17:17] <ogra_> davmor2, 31, right ?
[17:17] <davmor2> ogra_: yeap
[17:17] <robru> kgunn, alright, silo 6 ready to build
[17:18] <davmor2> cyphermox, ogra_
[17:18] <ogra_> Wellark, see the screenshot above
[17:18] <davmor2> cyphermox, ogra_ : http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-181734.png this is what I get if I turn it on
[17:18] <cyphermox> davmor2: that's a mako on 31 correct?
[17:18] <ogra_> right
[17:18] <davmor2> cyphermox: yeap
[17:18] <cyphermox> good. then I should be able to see this as well shortly
[17:19] <cyphermox> not that it's especially useful since on 32, it works :P
[17:19] <ogra_> yeah
[17:19] <ogra_> :/
[17:19] <Wellark> davmor2: can you get it back to the initial satte?
[17:19] <Wellark> *state
[17:19] <cyphermox> but maybe with this I can get just enough information to know what's up on flo and manta
[17:19] <davmor2> Wellark: I think cyphermox will shortly hopefully
[17:19] <Wellark> well, I'm flashing also..
[17:20] <davmor2> right tea for me back in 30
[17:20] <ogra_> the weird bit is that 31 and 32 behave differently for no good reason
[17:20] <cyphermox> indeed
[17:20] <ogra_> unless NM secretly hooks into whoopsie now :P
[17:20] <Wellark> on 32 it works?
[17:20] <cyphermox> was it reported by more people than just davmor though? like, do we see the same issue in the lab?
[17:21] <ogra_> Wellark, for cyphermox it works on 32 ... http://people.canonical.com/~ogra/touch-image-stats/32.changes is the changeset between 31 and 32
[17:21] <ogra_> cyphermox, yes, it was reported by more people
[17:21] <Wellark> does that track all the android changes as well?
[17:21] <Wellark> ogra_: ^
[17:21] <ogra_> Wellark, no, but there werent any
[17:21] <Wellark> were there some?
[17:21] <ogra_> nope
[17:21] <Wellark> ok.
[17:22] <ogra_> last android change was from 29 to 30
[17:22] <Wellark> ok. flashed 32. works.
[17:22] <Wellark> let's see 31
[17:22] <ogra_> but there the indicator was only half landed aynway
[17:22] <ogra_> (before 31)
[17:22] <ogra_> so it doesnt give us any good datapoints
[17:23] <Wellark> ogra_: the unity8 side of the landing did not affect the functionality of the indicator at all
[17:23] <Wellark> it's only changed the way unity8 reads the icons from the indicator
[17:23] <ogra_> it affected the visuals ...
[17:23] <ogra_> no indicator at all vs indicator visible
[17:23] <Wellark> I mean the actual code paths run
[17:23] <ogra_> right
[17:23] <ogra_> but you cant interact ...
[17:24] <ogra_> and if it come up like http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-181553.png... but without indicator you are locked out of wlan
[17:24] <Wellark> well, you could if you go to the bluetooth indicator first and then switch from the panel :)
[17:24] <ogra_> *comes
[17:24] <Wellark> ogra_: you can get the indicator visible by going inside the bluetooth indicator first
[17:24] <Wellark> ogra_: but using system-settings is just the same
[17:25] <Wellark> from 29-30 you can simply open system-settings Wifi page
[17:25] <Wellark> and get he exact same toggle
[17:25] <ogra_> right, thats another issue ... on all non mako devices system-settings wlan settings are gone
[17:25] <cyphermox> ogra_: 31 appears to work just the same
[17:25] <ogra_> (they are fine on mako)
[17:25] <ogra_> cyphermox, bah
[17:26] <Wellark> ogra_: what.. I'm running 31 and 32 just fine and seeing the system settings
[17:26] <bfiller> sil2100, ogra_, robru: can someone review/ack these packaging changes for silo1 so we can get that released?
[17:26] <bfiller> https://ci-train.ubuntu.com/job/landing-001-2-publish/29/
[17:26] <ogra_> Wellark, on flo or manta ?
[17:26] <Wellark> wait.. ogra_ do they by any change use the tablet profile on the system settings?
[17:26] <sil2100> bfiller: right, so it seems ogra_ is busy, let me find someone else ;)
[17:26] <robru> bfiller, in the meeting sil2100 told me he was doing that one, but if he's not then I can take a look at it after I finish silo 6
[17:26] <ogra_> Wellark, not sure ... ask seb128 or Laney ... i dont think so though
[17:26]  * sil2100 still writing the e-mail
[17:26] <bfiller> thanks guys!
[17:27] <cyphermox> sil2100:  robru: i review
[17:27] <sil2100> But it's just getting someone to look at it
[17:27] <Wellark> ogra_: if they do then that would explain the settings dissapeaering
[17:27] <sil2100> cyphermox: thanks, it's a quick one - a new binary package and its usage
[17:27]  * Wellark makes a note to check the tablet profile
[17:27] <ogra_> i'm pretty sure we use the same on all devices currently ...
[17:28] <sil2100> cyphermox: it's safe from my POV
[17:28] <Wellark> well, then there is no reason.. unless indicator-network is not runnig
[17:28] <ogra_> but let them answer that ... i dont know the system-settings code
[17:28] <cyphermox> it looks fine, simple
[17:29] <Wellark> but again. is someone now running a device that has the wifi disabled right now?
[17:29] <ogra_> Wellark, davmor2 will shortly ...
[17:29] <ogra_> (he said)
[17:29] <ogra_> i'm upgrading a flo here
[17:29] <ogra_> so i can get you infos about that side
[17:30] <ogra_> (thought thats OTA ... might not be 100% the same)
[17:30] <Wellark> ogra_, davmor2: are you doing anything else than simply running ubuntu-device-flash ?
[17:30] <Wellark> or OTA
[17:30] <ogra_> Wellark, davmor2 only used u-d-f
[17:31] <Wellark> ok. so no scripts or any other dark magic involved.
[17:31] <ogra_> with --bootstrap even
[17:31] <ogra_> so it is 100% clean
[17:31] <Wellark> hmm.. could that be it?
[17:31] <Wellark> is it always with --bootstrap?
[17:31] <ogra_> yes
[17:31] <Wellark> what about plain --wipe?
[17:32] <ogra_> you need that on new installs since thats the only way to get the ubuntu kernel and recovery installed
[17:32] <ogra_> --wipe just formats /data
[17:32] <ogra_> ok
[17:32] <Wellark> umm.. new kernel and recovery..
[17:32] <ogra_> after OTA on flo i have wifi ...
[17:32] <ogra_> but no wifi page in settings
[17:33] <sergiusens> ogra_: flashing from a pre installed image does get you a new recovery and kernel
[17:33] <sergiusens> it just doesn't reboot into it during the install
[17:33] <ogra_> and no network indicator either
[17:33] <ogra_> sergiusens, using --bootstrap doesnt get you a new kernel ?
[17:33] <Wellark> ogra_: please, stand by
[17:33] <Wellark> don't touch it
[17:34] <Wellark> ogra_: please open
[17:34] <Wellark> /usr/share/unity/indicators/com.canonical.indicator.network
[17:35] <Wellark> ogra_: flo is a tablet right?
[17:35] <ogra_> yes
[17:35] <Wellark> so change the [tablet] [tablet_greeter] and [tablet_wifi_settings]
[17:35]  * ogra_ has the file open
[17:35] <ogra_> to what
[17:35] <Wellark> ogra_: ther ObjectPath=..../tablet*
[17:36] <ogra_> to be phone =
[17:36] <ogra_> ?
[17:36] <Wellark> change them to ObjectPath=..../phone
[17:36] <Wellark> yep
[17:36] <ogra_> k
[17:36] <sil2100> brb, jumping out to the store
[17:36] <Wellark> ogra_: then reboot
[17:37] <Wellark> or do restart unity8
[17:37] <Wellark> that should also do it
[17:37] <ogra_> rebooting
[17:37] <Wellark> btw, I installed 31 with --wipe to mako and wifi is on by default
[17:37] <Wellark> now trying with bootstrap
[17:38] <ogra_> nothing in wlan settings nor in the indicator menu with that change
[17:38] <Wellark> ogra "status indicator-network"
[17:38] <ogra_> its not in the processlist
[17:39] <ogra_> phablet@ubuntu-phablet:~$ status indicator-network
[17:39] <ogra_> indicator-network stop/waiting
[17:39] <Wellark> ogra_: start indicator-network
[17:39] <Wellark> as phablet user
[17:39] <ogra_> starts it seems
[17:40] <Wellark> ogra_: did you get indicator on the panel?
[17:40] <ogra_> nope
[17:40] <sergiusens> ogra_: --bootstrap boots recovery with the new kernel and then the system-image-upgrader also flashes that kernel
[17:40] <ogra_> and it prints "ModemManager::ModemManager()" in the log
[17:40] <ogra_> every time it starts it seems
[17:40] <Wellark> ogra_: yep. that's a "feature" ignore that for now
[17:40] <ogra_> sergiusens, ok, phew ... you scared me
[17:40] <sergiusens> ogra_: correction, we boot into recovery with the new kernel; and then recovery flashes the kernel
[17:41] <sergiusens> ogra_: in every case, recovery is the one that flashes the kernel (in the boot.img)
[17:41] <ogra_> Wellark, anyway, nothing is running ...
[17:41] <ogra_> and .cache/upstart/indicator-network.log has no errors
[17:41] <Wellark> ogra_: what about /var/crash?
[17:41] <ogra_> except the MM thing
[17:42] <ogra_> Wellark, indeed :)
[17:42] <ogra_> there is a .crash file
[17:42] <Wellark> hmm..
[17:43] <Wellark> ogra_: run the indicator manually on the shell
[17:43] <ogra_> "on the shell" ?
[17:43] <Wellark> /usr/lib/arm../indicator-network/indicator-network-service
[17:43] <Wellark> ogra_: console
[17:44] <ogra_> or-network-serviceblet:~$ /usr/lib/arm-linux-gnueabihf/indicator-network/indicat
[17:44] <ogra_> ModemManager::ModemManager()
[17:44] <ogra_> Segmentation fault (core dumped)
[17:44] <Wellark> I need that dump..
[17:45] <Wellark> better yet, I need a flo
[17:47] <Wellark> ogra_: is NetworkManager running?
[17:47] <Wellark> ogra_: is ofono running ?
[17:47] <ogra_> why would ofono run ?
[17:47] <ogra_> NM is running, i'm online
[17:47] <davmor2> Wellark: for that run is was as follows, adb reboot bootloader and then ubuntu-device-flash --channel=devel-proposed --revision=31 --bootstrap
[17:47] <ogra_> (and see it in ps)
[17:48] <davmor2> s/is/it
[17:48] <Wellark> davmor2: what about 32 ?
[17:49] <Wellark> somebody everything magically started to work properly on 32
[17:49] <ogra_> well, cyphermox didnt even have issues on 31
[17:49] <sergiusens> sil2100: any updates?
[17:49] <ogra_> which is ..... well .... irritating
[17:49] <Wellark> ogra_: did cyphermox use --bootstrap ?
[17:50] <ogra_> i would expect so
[17:50] <cyphermox> I *always* do
[17:50] <ogra_> right
[17:50] <Wellark> ok. good. just had to check
[17:50] <davmor2> Wellark: that was when I went for tea so trying 32 now
[17:50] <Wellark> davmor2: wait
[17:51] <Wellark> do you have that faulty system live now?
[17:51] <Wellark> "faulty"
[17:51] <davmor2> Wellark: no it's flashing as we speak, but I can re-flash 31 after
[17:52] <Wellark> well, as long as there is any system where the wifi is disabled initially
[17:52] <Wellark> except flo. it has some other issues
[17:53] <davmor2> Wellark: I have manta and flo with no networking at all.  I'm going to bootstrap those after, mako shouldn't be long before it is up on 32 and I can see what happens there
[17:53] <ogra_> davmor2, check /var/crash on manta
[17:54] <ogra_> and: ps ax|grep indicator-network
[17:54] <ogra_> see if it runs at all
[17:54]  * ogra_ suspects flo and manta have the same issue 
[17:54] <Wellark> what was manta?
[17:54] <ogra_> N10
[17:54] <Wellark> right.
[17:54] <ogra_> flo is N7
[17:54] <Wellark> 2013 ed.
[17:54] <Wellark> right?
[17:54] <ogra_> yeah
[17:55] <Wellark> ogra_, davmor2: you do have a mako, too, right?
[17:55] <ogra_> plars, so i guess you want to switch off tests on flo until this is fixed ...
[17:55] <davmor2> ogra_: mediascanner, system-settings, unity8, indicator-network-service, thumbnailer and upstart
[17:55] <ogra_> Wellark, i only have a personal mako that only runs promoted images
[17:56] <ogra_> davmor2, well yes, we look for indicator network indeed :)
[17:56] <davmor2> Wellark: I have mako, manta and flo
[17:56] <plars> ogra_: I'm happy to leave them on as long as it's not something killing devices
[17:56] <Wellark> well, who then reported that mako now boots with wifi disabled by default?
[17:56] <ogra_> plars, adb should still be fine ...
[17:56] <plars> ogra_: we may have incomplete results is all
[17:56] <plars> ogra_: yeah
[17:56] <plars> ogra_: that way when it does get fixed, we're not behind
[17:56] <ogra_> Wellark, davmor2 did ... and i think popey too earlier
[17:56] <ogra_> plars, ok, fine
[17:57] <Wellark> ogra_: could you get me the output of
[17:57] <Wellark> nmcli nm
[17:57] <Wellark> nmcli d
[17:57] <Wellark> from flo
[17:58] <ogra_> note that i did OTA and have working wifi ... just no way to manage it
[17:58] <plars> sil2100: ogra_: they clearly didn't run for this image though, so don't expect results on flo or manta for now is all
[17:58] <ogra_> root@ubuntu-phablet:~# nmcli nm
[17:58] <ogra_> RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN
[17:58] <ogra_> running         connected       enabled         enabled    enabled         disabled
[17:58] <ogra_> root@ubuntu-phablet:~# nmcli d
[17:58] <ogra_> DEVICE     TYPE              STATE
[17:58] <ogra_> wlan0      802-11-wireless   connected
[17:59] <ogra_> plars, right
[17:59] <ogra_> Wellark, the NM side is totally fine ...
[17:59] <Wellark> I just finished a fresh flash on mako with image 32 and --bootsrap an wifi is enabled.
[18:00] <davmor2> ogra_: flo has the same crash as manta stands a chance it;s the same issue which then begs the question as to why mako works when the others don't
[18:00] <ogra_> right
[18:00] <ogra_> well, mako is the only one that also has ofono
[18:00] <Wellark> well, I either need a flo, manta or a backtrace
[18:00] <greyback> robru: hey, silo6 didn't reconfig, qtubuntu is missing from it still. Could you kick it please? :)
[18:00] <Wellark> or being able to reproduce on mako
[18:01] <Wellark> which I am not
[18:01] <ogra_> Wellark, well, do you make any assumptions about ofono in your code ? the tablets both dont have 3G so there wont be any 3G connection
[18:01] <ogra_> nor will there be ofono running
[18:02] <robru> greyback, strange, ok
[18:02] <greyback> robru: thanks
[18:02] <davmor2> Wellark, ogra_, cyphermox: Right so on 32 this is what I see http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-190056.png  note no wifi indicator icon, however I have a list to choose from which is kinda what I expect
[18:02] <Wellark> ogra_: the code *should* be able to function without ofono
[18:02] <robru> greyback, you're welcome
[18:02] <ogra_> davmor2, right, i would call that fine
[18:02] <ogra_> (and we know about the icon issue)
[18:03] <Wellark> there is a MR for the 3G icon
[18:03] <ogra_> right
[18:03] <Wellark> waiting for a silo
[18:03] <Wellark> that's screenshot looks correct
[18:03] <ogra_> well, seems the WLAN icon is missing too
[18:03] <Wellark> nope
[18:03] <ogra_> judging by davmor2's screenshots
[18:03] <Wellark> there is no separate wlan icon
[18:03] <ogra_> ah
[18:03] <davmor2> ogra_: that's my point the wifi icon is missing
[18:03] <davmor2> Wellark: there was when did that change
[18:04] <ogra_> davmor2, right, but the issue we look at is "wlan disabled on first boot"
[18:04] <Wellark> only if 3G is not connected
[18:04] <ogra_> we know about the icon
[18:04]  * cyphermox lunch, bbl
[18:04] <ogra_> well, in any case it looks like a heisenbug ...
[18:05] <ogra_> since it seems to work fine for everyone on 32
[18:06] <davmor2> Wellark: let me get this straight if there is no 3g there is no wifi icon?  How do you tell if you are connected to wifi then,  or the signal strength or for that matter how would manta and flo that have no 3g ever display wifi :)
[18:06] <ogra_> if there is no 3G there should be a wifi icon ... is how i understood Wellark
[18:06] <Wellark> yes. if there is no wifi and no 3g
[18:07] <Wellark> then you will have an icon showing wifi with a X
[18:07] <ogra_> right
[18:07] <Wellark> but if there is no wifi and a 3g connection then you see a mobile broadband ion
[18:07] <Wellark> *icon
[18:07] <ogra_> davmor2, switch off 3G
[18:07] <ogra_> then you should see a wifi icon
[18:07] <Wellark> yep.
[18:08] <ogra_> and if you switch off both you should see the disabled wifi one
[18:08] <ogra_> if i understand that right
[18:08] <Wellark> yes
[18:08] <davmor2> Wellark: but normally I see a wifi icon with a x on it to say that there are wifi ap's available
[18:08] <ogra_> davmor2, even if 3G is up ?
[18:09] <davmor2> yeap
[18:09] <Wellark> well, the old indicator was a bit flaky on it's icons ;)
[18:09] <Wellark> this is the way the design wants it
[18:10] <ogra_> i found the old indicator quite logical ...
[18:10] <ogra_> but who am i to argue with design ... :P
[18:10] <davmor2> Wellark: in that case how do you know that there are wifi zones available if there is no indication for it?
[18:11] <ogra_> (i'll just grow a longer thumb to reach the new back button they "designed")
[18:11] <davmor2> do you just have to swipe down everywhere you go to see?
[18:11] <ogra_> (SCNR)
[18:11] <davmor2> ogra_: I'll buy you a thumb tip from the local magic shop :)
[18:11] <Wellark> davmor2: well there are plans to have a super annoying (my personal opinion!) dialog that tells you "Hey, there are access points available!"
[18:11] <ogra_> haha
[18:11] <ogra_> oh, like IOS
[18:12] <ogra_> davmor2, well, do you see the wlan icon after disableing 3G ?
[18:12] <Wellark> if it was up to me we would have separate icons for mobile data and wifi
[18:12] <ogra_> ++
[18:12] <ogra_> same here
[18:12] <davmor2> Wellark: I'm with you on that one :)
[18:12] <ogra_> but after the back button issue i gave up arguing with design
[18:12] <Wellark> I would actually put wifi icon per wifi adapter :)
[18:13] <davmor2> Yeap with 3g knocked off I now see the icon I was expecting to see
[18:13] <Wellark> I already had quite a fight convincing that we do need to show cellular strength per modem
[18:13] <davmor2> wifi with a x in it
[18:13] <Wellark> yep. so you don't have wifi nor you have 3g
[18:13] <Wellark> you are offline.
[18:13] <ogra_> Wellark, well, they answer your questions then ... i had a week long email thread on the ML where i only got "well, we decided that" in the end as answer
[18:14] <ogra_> davmor2, and swtiching on wifi will get you the normal wlan icon, right ?
[18:14] <Wellark> so.. now. is anyone able to reproduce the the "wifi initially disabled after --bootstrap" on mako anymore with image 32?
[18:14] <davmor2> Wellark: indeed but that is the icon I expect to see which says there are wifi aps available :)
[18:14] <ogra_> Wellark, doesnt look like
[18:14] <davmor2> image 32 is fine let me try image 31 againa
[18:15] <Wellark> I just flashed both 32 and 31 with bootstrap and everything looked fine
[18:15] <Wellark> ogra_, davmor2: regarding the tablets
[18:15] <ogra_> well, as long as it stays fine now i dont care about 31 ...
[18:15] <ogra_> :P
[18:16] <Wellark> would you be able to install ofono-phonesim-autostart package ?
[18:16] <Wellark> that would provide ofono
[18:16] <Wellark> just to see if indicator-network does not handle missing ofono as well as I thought
[18:16] <davmor2> Wellark: no there is no network to pull it in on :D
[18:16] <Wellark> ok :)
[18:16] <Wellark> davmor2: you can use nmcli to connect :)
[18:17] <davmor2> Wellark: let me finish flashing mako now it has started
[18:19] <Wellark> ogra_, davmor2: has there been a kernel change between 30 and 32 ?
[18:19] <davmor2> Wellark: no idea ogra_ ^
[18:19] <ogra_> no
[18:19] <ogra_> kernels are shipped with android
[18:19] <ogra_> and that didnt change as we know :)
[18:22] <ogra_> (our kernels didnt change since mid trusty actually)
[18:23] <ogra_> sil2100, hmm, 32 looks really good actually
[18:24] <ogra_> even shorts app has one failure less
[18:24] <ogra_> (uitk and system-settings didnt run yet though)
[18:27] <sil2100> Woot
[18:27] <davmor2> sil2100: and wifi is working there too :)
[18:27] <sil2100> Double-woot
[18:27] <sil2100> ;)
[18:29] <davmor2> ogra_, Wellark: meh okay so this is weird this time 31 has aps in the list and the wifi is turned on,  I hope this isn't going to be some random race condition
[18:30] <ogra_> stop wearing these aluminium gloves !
[18:30] <davmor2> ogra_: no one told me it was safe to take of the tin foil hat and gloves
[18:33] <ogra_> Wellark, well, i guess for mako we are fine then ... and i think we can let flo and manta be until tomorrow ...
[18:33] <sil2100> uh
[18:34]  * sil2100 goes back to tinkering then
[18:34] <ogra_> sil2100, well, we need that icon fix landed asap ...
[18:35] <ogra_> but given that we wont promote anything tonight anymore i guess thats also for tomorrow
[18:36] <davmor2> rsalveti: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1319119 I added the crash file but if I try and collect on it it crashes apport
[18:36] <robru> sil2100, oh are you still around? we're having more snakefruit rsync issues if you didn't notice. do you remember what the fix was yesterday? (or, uh, earlier today for you i guess)
[18:36] <rsalveti> davmor2: haha, thanks
[18:36] <Wellark> sil2100: ogra_: that iconfix is ready. just waiting for a silo.
[18:36] <ogra_> Wellark, right
[18:36] <Wellark> davmor2, ogra_ : if you happen to see the disabled wifi again
[18:36] <davmor2> rsalveti: I added it in the hope that you can deconstruct it and maybe get something useful from it :)
[18:37] <Wellark> then just stop everything
[18:37] <ogra_> we will hunt you down
[18:37] <sil2100> robru: hmmm... maybe Timo would know, no one informed me about those sadly ;/
[18:37] <Wellark> ogra_: ok :)
[18:37] <sil2100> robru: what issues are those?
[18:37] <rsalveti> davmor2: sure, thanks! :-)
[18:37] <robru> sil2100, http://people.canonical.com/~rbpark/citrain/ there are 8 packages spanning 4 silos that are in "no known space and time". we've lost the ability to publish anything basically
[18:37] <robru> sil2100, happned to me yesterday
[18:37] <Wellark> davmor2, ogra_: you could try to install ofono-phonesim-autopilot on manta and flo to see if missing ofono causes indicator-network to crash
[18:38] <Wellark> you can get network up with nmcli
[18:38] <ogra_> i will do that tomorrow ... i'm constantly working since over 12h now and need to go afk else my brain explodes ...
[18:39] <Wellark> ogra_: oh, you, too? ;)
[18:39] <Wellark> for how many weeks?
[18:39] <Wellark> I lost count at some point :P
[18:39] <davmor2> ogra_: but your brain can't explode until I press the button on this detonator
[18:39] <ogra_> Wellark, haha
[18:40] <ogra_> davmor2, stop that !! :P
[18:40] <ogra_> anyway ... off to take care of that headdache ...
[18:40] <davmor2> ogra_: have a good evening Sir
[18:41] <davmor2> Wellark: I'll have a play and see if I can't get it up and running
[18:41] <robru> sil2100, I pinged in #ubuntu-release already, no response yet, I'm off for lunch now... bbl
[18:42] <davmor2> Wellark: this is what I currently see on flo and manta though http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-194140.png
[18:42] <Wellark> davmor2, ogra_: could you guys make a comment to bug #1319906 saying that after exhaustive testing from several people we were not able to reproduce on mako with image 32
[18:43] <Wellark> and mark it as "Incomplete" just so it stays open if the problem comes back but also it will expire in 60 days if it doesn't come back
[18:43] <Wellark> davmor2: yeah, try installing ofono-phonesim-autostart
[18:43] <Wellark> and reboot
[18:43] <davmor2> Wellark: yeah that is just the before
[18:45] <Wellark> davmor2: could you file a bug, install gdb and try to get me a backtrace
[18:45] <Wellark> if you do, then please file a bug
[18:45] <Wellark> or if there is a crash file under /var/crash
[18:45] <davmor2> Wellark: I've just had a thought,  I wonder if the issue with 31 was that there was no 3g/phone signal on ofono so it tripped out wifi with it maybe?  Long shot I understand but just a thought
[18:46] <Wellark> would be great if that could be backtraced with LP backtracer evven
[18:46] <Wellark> davmor2: good theory, but.. :)
[18:46] <Wellark> the wifi disable/enable switch on totally separated code path
[18:47] <davmor2> Wellark: oh well
[18:58] <davmor2> Wellark: man ofono autosim pulls in some odd stuff
[18:58] <davmor2> xvfb x11 libs
[18:58] <Wellark> yep
[18:58] <Wellark> enjoy ;)
[19:00] <bfiller> xnox, sergiusens : we are good to upload 672 of gallery to store, the failures are all because of the one known bug
[19:00] <sergiusens> bfiller: ok ... I'll upload (xnox ack)
[19:01] <davmor2> Wellark: http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-200029.png  note indicator is there settings → wifi still blank
[19:02] <davmor2> Wellark: on a plus side I can at least try and report the indicator crash now :)
[19:02] <Wellark> davmor2: try to modify the /usr/share/unity/indicators/com.canonical.indicator.network
[19:03] <Wellark> on the same go
[19:03] <Wellark> so that I can fix the settings if it's just that
[19:03] <Wellark> davmor2: does the indicator contain the list of access points also?
[19:04] <Wellark> davmor2: so on that file
[19:04] <Wellark> all the ObjectPath= lines
[19:04] <Wellark> that contain "tablet"
[19:04] <Wellark> replace with "phone"
[19:04] <Wellark> then reboot and see if the wifi settings magically populate
[19:05] <davmor2> Wellark: http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-05-15-200456.png
[19:05] <davmor2> I'll reboot
[19:09] <davmor2> Wellark: so oddly both with tablet and phone in those settings it look like it briefly lists the network connections maybe 1 second and then reverts to empty
[19:11] <davmor2> Wellark: I'll do a fresh bootstrap tomorrow though and test it properly then
[19:14] <Wellark> davmor2: if the list goes empty then indicator-network probably has crashed
[19:14] <Wellark> though upstart should bring it up again straight away..
[19:14] <Wellark> I need to get myself a manta or flo somewhere
[19:15] <Wellark> or somebody needs to get me a backtrace
[19:15] <Wellark> there should be a crashfile under /var/crash
[19:15] <Wellark> although the one that is there right now is probably just the ofono missing crash
[19:15] <davmor2> Wellark: I just cleared it down I'll run a manual retrace on manta's but that is waiting till tomorrow to late tonight
[19:16] <davmor2> I'll see if flo has a new crash now though
[19:16] <Wellark> davmor2: if you have the stamina,could you nuke /var/crash and get a "clean" crashfile after ofono-phonesim-autostart has been installed
[19:16] <davmor2> Wellark: _usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash
[19:16] <Wellark> davmor2: ok, thanks!
[19:16] <davmor2> _usr_sbin_ofonod.0.crash
[19:16] <Wellark> oh.
[19:16] <Wellark> if ofono crashes
[19:17] <Wellark> then it will crash indicator-network now
[19:17] <Wellark> as I'm intentionally letting dbus problems raise exceptions that are not catched
[19:17] <Wellark> so ofono crash would explain why the indicator misbehaves
[19:18] <Wellark> (after I've fixed the crash when ofono is not available at all)
[19:18] <Wellark> although..
[19:18] <Wellark> is it really so that ofono is not seeded to manta or flo?
[19:18] <Wellark> davmor2: did ofono-phonesim-autostart also pull in ofono package?
[19:18] <davmor2> Wellark: I have no idea
[19:19] <Wellark> awe said that there is a known crasher on ofono
[19:19] <Wellark> that is waiting to be landed
[19:19] <Wellark> that might be affecting flo and manta
[19:19] <Wellark> awe_: ^
[19:22] <davmor2> Wellark: I need to go sorry,  I'll try and get manta's crash uploaded tomorrow after the landing meeting so about 10am bst  and we can pick it up again then
[19:22] <Wellark> davmor2: np. I need to eod too
[19:22] <Wellark> davmor2: thanks!
[19:31] <awe_> Wellark, there's a very specific crash that can happen during autopilot testing on flo and manta as they have no rild running
[19:32] <awe_> Wellark, AFAIK, nobody has hit this crash in a production scenario...
[19:32] <Wellark> sure, this was not a production scenario
[19:32] <Wellark> more close to an AP encironment
[19:33] <awe_> sergiusens, I thought you were going to update the status to "tested"
[19:33] <sergiusens> awe_: yes
[19:34] <awe_> it's not
[19:34] <awe_> ;)
[19:34] <Wellark> awe_: is ofono seeded on the tablet images?
[19:34] <sergiusens> awe_: no it is
[19:34] <sergiusens> Wellark: yes
[19:34] <awe_> as far as I know it is
[19:34] <sergiusens> the seed is common
[19:34] <awe_> thanks sergiusens
[19:34] <Wellark> so tablet images have ofono installed?
[19:34] <Wellark> is it running?
[19:34] <awe_> yes
[19:34] <awe_> yes
[19:34] <awe_> yes
[19:35] <Wellark> ok. good.
[19:35] <awe_> at least for the autopilot tests
[19:35] <sergiusens> installed, but probably not started as the rild upstart event never happens; haven't looked really
[19:35] <Wellark> I meant on "production"
[19:35] <awe_> I don't have a tablet, so I can't verify whether it's started on a table in the non-AP case
[19:35] <Wellark> oh, well. I will need to get myself a tablet as well
[19:35] <Wellark> what an interesting situation
[19:36] <awe_> probably not, as it won't get a rild-started event from the rild upstart job ( see /etc/init/rild.conf )
[19:36] <sergiusens> awe_: Wellark $ adb shell status ofono
[19:36] <sergiusens> ofono stop/waiting
[19:36] <Wellark> us not having HW :P
[19:36] <awe_> I have more phones than I know what to do with...
[19:36] <awe_> tablets are not important in my world
[19:36] <awe_> ;D
[19:36] <sergiusens> awe_: I'll trade a mako for a manta ;-)
[19:37] <awe_> sorry, I only have one mako
[19:37] <Wellark> oh, well.. until someone gives me a flo or mako I'm just going to mark all bugs coming from them as "Opinion" ;)
[19:39] <awe_> Wellark, you don't have a phone???
[19:40] <Wellark> sorry. was supposed to be manta
[19:40] <Wellark> :)
[19:40] <awe_> ah, ok
[19:40] <awe_> whew
[19:40] <Wellark> ok. eod
[19:40] <Wellark> bye.
[19:41] <awe_> Wellark, did the indicator icon fix land?
[20:07] <dobey> awe_: there's a network-indicator in the panel again on 32 for me
[20:13] <awe_> dobey, sweet, 3g?
[20:14] <dobey> awe_: i'm on wifi at the moment, and the wifi icon is there. cellular bars too.
[20:15] <awe_> ok, thanks...I'm re-flashing myself
[20:15] <dobey> awe_: and turning off wifi shows the [L] for LTE yes
[20:15] <awe_> ;)
[20:25] <awe_> dobey, still broken for me on mako
[20:25] <awe_> ;(
[20:31] <bfiller> robru: could you reconfigure silo 8 as I've added address-book there
[20:33] <robru> bfiller, can it wait until silo 1 finished publishing? will save you an extra rebuild that way
[20:34] <bfiller> robru: that's fine, any eta when that publish might finish?
[20:34] <robru> bfiller, should be soon. it was blocked all day by an infrastructure issue, but cjwatson fixed it just moments ago so everything should be working normally as of right now
[20:34] <bfiller> robru: cool
[20:35] <bfiller> robru: if I'm not around and you happen to notice the publish finish just go ahead and reconfig and rebuild if you don't mind
[20:35] <robru> bfiller, sure thing
[20:35] <bfiller> will be back later tonight to test
[20:37] <sergiusens> doanac: the time has come, can you do a full ci run on silo 3?
[20:38] <doanac> sergiusens: sure thing.
[20:38] <sergiusens> doanac: thanks
[20:41] <doanac> sergiusens: you have the new link to the spreadsheet handy?
[20:41] <sergiusens> doanac: I use the meta sheet from robru
[20:41] <sergiusens> doanac: http://people.canonical.com/~rbpark/citrain/
[20:42] <robru> doanac, and that page links to the spreadsheet in the top bar
[20:44] <doanac> robru: i love this: http://people.canonical.com/~rbpark/citrain/train.gif
[20:44] <robru> doanac, lol! I was wondering how long until somebody noticed that! ;-)
[20:45] <dobey> awe_: weird. my mako has the wifi icon too (i have all on my hammerhead)
[20:45] <dobey> awe_: are you flashing devel, or devel-proposed?
[20:48] <awe_> dobey, the bug was that the wrong 3g icon was used, so that's why it's working for you
[20:48] <awe_> https://code.launchpad.net/~unity-api-team/indicator-network/fix-3g-icon/+merge/219726
[20:49] <awe_> unfortunately, there's no silo for this fix yet
[20:49] <awe_> ;(
[20:49] <robru> bfiller, ok, silo 1 merged and silo 8 reconfigged and building: https://ci-train.ubuntu.com/job/landing-008-1-build/67/console
[20:49] <bfiller> robru: awesome, thanks
[20:50] <robru> bfiller, you're welcome!
[20:52] <doanac> sergiusens: kicked off a job: http://q-jenkins.ubuntu-ci:8080/job/andy-smoke-daily-test/14/console
[20:52] <doanac> i'll check back with the results later tonight
[20:52] <sergiusens> thanks
[21:02] <robru> alright, I'm going to run some errands, does anybody need anything before i go?
[21:06] <robru> bbiab
[21:09] <dobey> awe_: oh! i thought you were talking about the indicator not showing up at all :)
[21:10] <awe_> I was...  if the icon can't be found, it doesn't show up at all!
[21:10] <awe_> all I see are signal bars
[21:10] <awe_> when the phone is actually on 3g
[21:11] <dobey> awe_: i mean, the bug about the indicator not showing up at all
[21:11] <dobey> not the 3g icon only :)
[21:12] <awe_> I wasn't aware there was another bug
[21:16] <dobey> awe_: there was a big change to the network indicator that landed in i think image 29, so 29 and 30 didn't have an indicator at all. don't know about 31, but with 32 and a new unity8, it came back
[21:17] <awe_> right
[21:17] <awe_> in my opinion it's still broken for mako
[21:18] <ToyKeeper> Hmm, I wonder if I'll be able to see that issue...  my 3G doesn't work most of the time.
[21:19] <awe_> well, if it does work you won't know it.  ;)-
[21:19] <ToyKeeper> No idea why.  Another phone here uses the same provider and works fine.
[21:19] <awe_> ToyKeeper, have you filed a bug?
[21:20] <awe_> 3g not working properly is the kinda thing that keeps me up at night
[21:20] <ToyKeeper> Until recently, I didn't even know if it *could* work...  and then it just suddenly worked one day.
[21:20] <ToyKeeper> I had been meaning to flash android on it to test, but never seemed to find time.
[21:21]  * ToyKeeper tries image 32
[21:25] <dobey> awe_: know how to disable LTE so i'm forced down to 3G?
[21:27] <awe_> yea, I believe /usr/share/ofono/scripts/set-tech-preference umts will do the trick
[21:28] <awe_> and conversely, just use "lte" to switch back
[21:29] <dobey> either "lte" doesn't work for that, or once the icon's broken it stays broken
[21:29] <dobey> but setting it to umts does result in the brokenness you describe
[21:31] <dobey> ok, got lte icon back after a reboot
[23:15] <thomi> plars: doanac fginther: any idea where I can find a list of tests that are run on the dashboard, and their corrosponding bzr branches? That must be stored somewhere, right?
[23:16] <doanac> thomi: i don't know about their corresponding branches, but the tests we run come from: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/jenkins/testconfig.py#L51
[23:17] <robru> kgunn, building in silo 1: https://ci-train.ubuntu.com/job/landing-001-1-build/49/console
[23:17] <thomi> doanac: yeah, I relly need the bzr branches. Maybe in phablet-tools
[23:17] <robru> boiko, building in silo 14: https://ci-train.ubuntu.com/job/landing-014-1-build/44/console
[23:17] <robru> greyback, building in silo 17: https://ci-train.ubuntu.com/job/landing-017-1-build/56/console
[23:17] <doanac> thomi: cupstream2distro-config? i don't think phablet-tools is going to have anything like that
[23:18] <doanac> well - phablet-click-test-setup might.
[23:18] <thomi> that's what I was thinking
[23:18]  * thomi reads the source
[23:19] <doanac> thomi: i've got to grab dinner. good luck
[23:19] <thomi> cheers