/srv/irclogs.ubuntu.com/2014/08/05/#ubuntu-ci-eng.txt

ToyKeeperSo, this was cool: http://toykeeper.net/tmp/phablet/2014-08-04/wifi-settings-layout-broken.png04:36
bzoltanGuys, i am executing the UITK test plan right now.. pretty much doing the same test set as the CI dash.  I see that the CI dash shows scary amount of failures...04:40
MirvKaleo: jhodapp: line 27 for qtubuntu-camera (ensure directory exists) conflicts with silo-003 (audio recording), do you want to land the line 27 first or wait until 003 has been landed?04:47
bzoltanMirv:  do you know what the hack is happening with the autopilot tests? The CI dash shows tons of failures.04:56
ToyKeeperbzoltan: I'm not sure, but I heard mumblings earlier today about being unable to make a new image until something in the process was fixed...  so image 171 didn't happen.  I haven't checked on the details though.  Perhaps related?05:10
bzoltanToyKeeper: I do not know.. I just woke up and watched my own nightly tests for the ongoing UITK landing. Horror...05:17
Mirvsome devices are apparently failing which cause havoc to the numbers05:42
Mirvor that was the general idea yesterday at least05:42
Mirvbzoltan: you were offline, but there is some problems with some of the devices. the 169 mako results for example were repeated for more times and show "truer" results: http://ci.ubuntu.com/smokeng/utopic/touch/mako/169:20140804:20140728.1/9466/06:00
sergiusensMirv: hey, can you check silo 2 for me?06:25
Mirvsergiusens: I can't do the packaging ack unfortunately :(06:30
Mirvsince I'm not coredev06:30
sergiusensMirv: can rsalveti do the ack?06:30
rsalvetipackaging ack is fine06:30
sergiusensMirv: it's a preNew thing06:30
Mirvyes he can, it's a new package though06:31
rsalvetiThis source is a new package, if the destination is ubuntu, please ensure it has been preNEWed by an archive admin before publishing that stack.06:31
rsalvetiright06:31
rsalvetithat's the message06:31
Mirvprenew acks used to be only doable by https://launchpad.net/~ubuntu-archive/+members06:31
rsalvetiyeah, not by me06:31
Mirvseb might be awake since he's in China tz06:31
rsalvetiyeah, seb128_, able to help with that?06:31
Mirv( = pre-new acking https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-002/+packages 's ciborium package)06:32
seb128_rsalveti, Mirv: in a meeting, which one?06:34
seb128_can look in a bit06:34
=== seb128_ is now known as seb128
rsalvetiseb128: ciborium, from silo 0206:34
seb128rsalveti, k06:35
Mirvrsalveti: while you're there, packaging pre-check for qtdeclarative-gles https://launchpadlibrarian.net/181499705/qtdeclarative-opensource-src-gles_5.3.0-0ubuntu3_5.3.0-0ubuntu4.diff.gz would be welcome, in case I get testing done at some point06:36
Mirvrsalveti: changelog for the respective qtdeclarative: http://pastebin.ubuntu.com/7958613/06:37
rsalvetiMirv: change looks fine, just need testing though06:38
slangaseksil2100: FYI, I didn't quite get autopilot-qt4 off the image yesterday; I'm building a new one now that autopilot 1.5.0+14.10.20140716-0ubuntu2 is in06:38
Mirvrsalveti: thanks. I'm battling my way through autopilots and manual testing.06:39
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
bzoltan1Mirv: about the UITK landing... I have run multiple times all the tests... the shorts, music, calendar and address book apps have same ugly test results with the release candidate UITK, all other tests are OK07:18
bzoltan1Mirv:  should we land the UITK?07:18
jibelnetwork list in the indicator and system-settings is broken on #17107:19
seb128jibel, settings tests started failing as well, we think it might be the ofono landings07:20
seb128I pinged rsalveti about it07:20
jibelseb128, is there is bug # ?07:20
ToyKeeperjibel: I filed a bug for that for 170...07:20
seb128but not sure anyone is looking at it07:20
jibelToyKeeper, ok07:20
rsalvetilet me ping abeato07:20
seb128rsalveti, thanks07:20
ToyKeeperjibel: Bug 1352684.07:20
ubot5Error: Launchpad bug 1352684 could not be found07:20
Mirvbzoltan1: music, calendar and address book have known failures, so please compare if you get the same individual test failures as shown at http://ci.ubuntu.com/smokeng/utopic/touch/mako/169:20140804:20140728.1/9466/ - shorts should pass, though07:21
Mirvalthough #171 does show a shorts failure too: http://ci.ubuntu.com/smokeng/utopic/touch/mako/171:20140805:20140728.1/9484/shorts_app/ is yours the same there too?07:22
ogra_ugh ... 13 of the 15 crashes in the 171 tests are indicator-network ... wow, that's bad07:22
bzoltan1Mirv: shorts did not pass here http://ci.ubuntu.com/smokeng/utopic/touch/mako/168:20140803:20140728.1/9448/?sort=pass_rate07:22
jibelogra_, indicator-network is not visible on #17107:23
jibelthat may explain test failures07:23
ogra_bzoltan1, don't trust the infrastructure to much, there are currently some issues07:23
Mirvbzoltan1: please do a comparison if you can "match" all your failures to those of #169, and also note which test is failing for shorts07:23
ogra_jibel, heh, definitely07:23
bzoltan1ogra_:  I figured... :(07:23
sil2100o/07:23
ogra_sil2100, 13 of the 15 crashes in the 171 tests are indicator-network ... and according to jibel it doesnt start in dogfooding07:24
Mirvbzoltan1: so you should probably have 4 calendar, 8 music-app, 9 address-book failures07:24
ogra_(just to sweeten your morning :) )07:24
sil210015 crashes?07:24
ogra_yeah, 171 has 15 crashes07:24
ogra_one dialer-app, one telepathy-ofono and 13 indicator-network ones07:25
sil2100It just can't get any better ;)07:25
seb128sil2100, hey07:25
sil2100seb128: hi07:25
seb128sil2100, the settings change you approved yesterday is incomplete, it should have an updated depends on the schemas since it uses keys that only got added to the new version07:25
seb128sil2100, can you get it fixed?07:26
sil2100seb128: I only top-approved it because mardy top-approved it, and the lander said it was all tested and fine07:26
sil2100I mean, mardy approved it07:26
seb128sil2100, well, you top approved and it's buggy, so you are responsible, sorry...07:26
seb128don't top approve if otherwise07:26
seb128if -> it07:27
bzoltan1Mirv: i have this for shorts http://paste.ubuntu.com/7958905/07:27
sil2100Chipaca: ping07:27
Chipacasil2100: pong07:28
sil2100Chipaca: so it seems your landing wasn't completely +107:28
Chipacawha?07:28
sil2100Chipaca: check what seb128 mentioned above, the ubuntu-system-settings change that I was asking about seems to be missing something, something that mardy probably didn't see during his review07:29
slangaseksil2100: FYI, I didn't quite get autopilot-qt4 off the image yesterday; I've built a new one now that autopilot 1.5.0+14.10.20140716-0ubuntu2 is in07:29
jibelsil2100, ogra_ seb128 I filed bug 135274407:29
ubot5bug 1352744 in ofono (Ubuntu) "List of WiFi access point is empty" [Critical,Confirmed] https://launchpad.net/bugs/135274407:29
jibelseb128, do you think the missing network-indicator is the same bug or should I submit another one?07:29
seb128jibel, likely the same bug07:29
jibelk07:29
seb128same as the segfaults07:29
seb128I wonder how that ofono could land it if creates those issues07:30
seb128it made things not work and tests from rdepends fail07:30
ToyKeeperDoes this mean traincon 0?07:30
sil2100slangasek: ok, so you uploaded a new autopilot directly to the archive?07:31
Mirvbzoltan1: I built watch_only on your silo since the status was wrong in the sheet. the shorts app failure has happened on #161 (and random 1 failure every now and then otherwise) so probably not you to blame. please compare the 3 other packages with failures to the #169 results.07:31
jibelToyKeeper, I guess it does, last promotion was 157 on July 29th07:31
slangaseksil2100: yes, with packaging-only changes and an MP raised on the 1.5 branch07:31
Chipacasil2100: drat. I'll fix.07:31
ToyKeeper:(07:31
sil2100jibel, ToyKeeper: no, no traincon-0 yet, traincon is after 7 business days, now it's only 5... but we can decide on a traincon if things are very bad07:31
bzoltan1Mirv:  I am re-running the  calendar_app  music_app  address_book_app tests right now... takes damn long time07:32
jibelsil2100, k if it's business days07:32
Chipacaseb128: so do I bump the gsettings revno?07:32
Mirvbzoltan1: you don't need to rerun, you need to compare if you got the same failures as the #169 shows.07:32
ogra_slangasek, not sure you noted, but autopilot-qt4 is still on the image (was that wanted ?)07:32
slangasekogra_: that's exactly the thing that I'm rebuilding for right now07:33
bzoltan1Mirv:  I have to, because the first run gave me more failures than the CO dash.. but then I started to run those tests individually and few of them turned to be OK. We have more flaky tests than the CI dash shows.07:33
Chipacaseb128: or do i use the autogenerated revno like the previous depends?07:33
sil2100Chipaca: thanks, would be grateful since I have many other things right now07:33
Chipacasil2100: yeah, no worries07:34
Mirvbzoltan1: right, ok let's see to get slightly more certainty :( calendar and address book app tests are indeed quite slow07:34
Chipacaseb128: I mean, i can make it depend on the autogenerated07:35
Chipacaseb128: but i was told to land these things all together07:35
bzoltan1Mirv:  luckily I got the UITK silo build ready just before I went to sleep.. so the night test dropped out most of the time consuming tests with OK.. like unity8, uitk, browser, etc... so by the morning the list was down to the CI dash list.07:35
Chipacaseb128: which makes me wonder exactly how i was supposed to manage to do this dependency07:36
sil2100ogra_: I see that 170 also has many indicator-network crashes07:37
sil2100ogra_: I suppose it will be really hard to pin-down what caused those to happen so much07:39
* sil2100 upgrades his phone07:40
abeatojibel, ping07:45
jibelabeato, pong07:46
abeatojibel, hi, so why do you think it is an ofono issue?07:46
jibelabeato, http://people.canonical.com/~ogra/touch-image-stats/170.changes the most probable change in this list is ofono07:47
tvosssil2100, likely an issue with ofono not exposing a certain type of interface early enough07:48
ogra_jibel, what is broken in 170 ?07:48
ogra_looks pretty good on my device here07:48
abeatojibel, ok, I am going to re-flash mako, I do not see the issue for #171 in krillin07:49
jibelogra_, bug 135274407:49
ubot5bug 1352744 in ofono (Ubuntu) "List of WiFi access point is empty" [Critical,Confirmed] https://launchpad.net/bugs/135274407:49
ogra_hmm, i dont see that in 17007:50
jibelogra_, ah, I'm lost in build numbers :) let me reflash 170 then 17107:51
ogra_in smoketesting the indicator crashes in 170 ... but thats in its normal range (5 crashes ... not 13)07:52
ogra_"normal" :P07:52
sil2100Yeah07:53
sil2100ogra_: but it would be best if we had someone see if 170 doesn't have it completely broken as well, just in case07:53
bzoltan1Mirv:  for the calendar app I got +1 failure... after re-running that +1 it failed again (could not even start the app), I rebooted and then that test passed. So the calendar is as good with the UITK as on the CI dash. I proceed with the next one...07:54
ogra_sil2100, i'm running 170 here ... (on some other device)07:54
ogra_there it is fine07:54
sil2100ogra_: yeah, but it seems to be mako specific - flo and manta do not have so many crashes on 17107:55
sil2100So I wonder07:55
ogra_weird07:55
ogra_android didnt change07:55
sil2100Let's see what jibel finds out :)07:55
ogra_(it will change with the next build)07:56
jibelogra_, if I want to backup a mako before wiping it (it is my main phone) is saving /home enough? or should I backup all the rw partitions? (I don't care about keeping logs and this type of data)07:58
ogra_jibel, phew, not sure, i usually just pull my data off via mtp and do a fresh flash later ...07:59
ogra_i never tried to backup the rw partitions ... if you dont miss anything that might work though08:00
jibeli'll try and see what I lose08:00
* ogra_ wishes gallery app would start :(08:01
ogra_i reflashed yesterady and cant set my lockscreen wallaper now :(08:01
sil2100ogra_: gallery app does not work at all?08:01
sil2100Or doesn't work only when during content picker?08:02
ogra_sil2100, not sure ... it doesnt start at all for me08:02
slangaseksil2100, ogra_: ok, Qt4 off the image now; 11MB savings in tar.gz size, dunno how much savings on the install footprint08:02
slangasekand hopefully, removed without any test regressions08:03
ogra_lets take bets :)08:03
* ogra_ says 60MB08:03
slangasek:)08:03
sil2100hah ;)08:03
sil2100slangasek: thanks!08:03
ogra_yeah !!08:03
sil2100hm, we'll have to poke veebers or thomi to rebuild the autopilot silo though08:05
=== oSoMoN_ is now known as oSoMoN
sil2100I might do it for them if they're not around though08:05
thomihmmm?08:05
Chipacasil2100: https://code.launchpad.net/~chipaca/ubuntu-system-settings/gsettings-schema-depends-fix/+merge/22956708:05
pete-woodssil2100: you're a legend! thanks for fixing up the changelog for release:)08:06
sil2100pete-woods: nooo ;p No problem, good thing that I had access to that team and could commit to staging08:07
slangaseksil2100: ah, time-of-day suggests thomi is probably not around, I guess we should take care of this for tem08:07
slangasekthem08:07
thomi...08:07
sil2100Yeah, will do that in a moment :)08:07
thomiI'm around08:07
sil2100thomi: no worries! No re-testing needed, it's just a packaging change08:07
bzoltan1Mirv:  the music app is cleared too. The CI dash shows 8 failures and the UITK gave 9. The +1 was the music_app.tests.test_music.TestMainWindow.test_add_song_to_queue_from_albums_page what was OK after I run only that one again.08:13
Chipacaseb128: https://code.launchpad.net/~chipaca/ubuntu-system-settings/gsettings-schema-depends-fix/+merge/22956708:13
sil2100Chipaca: could you fix the issue I mentioned? i.e. 0.0.2+14.10.20140802.1 instead of 0.0.2+14.10.20140802 as the version08:15
sil2100Chipaca: it's a nit-pick, but since we fix it up now anyway, let's have the correct thing08:15
Chipacasil2100: i didn't see you mention that, yes sure08:15
sil2100Chipaca: I just noticed it and mentioned ;)08:15
sil2100(you might have needed to refresh the page)08:16
jibelogra_, sil2100 abeato I confirm that 135274408:16
jibelis a regression in #17008:16
sil2100Uh08:16
abeatojibel, I have just commented in https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/135274408:16
* sil2100 looks at the commitlog08:16
ubot5Launchpad bug 1352744 in ofono (Ubuntu) "List of WiFi access point is empty" [Critical,Confirmed]08:16
Chipacasil2100: done08:16
sil2100jibel: ok, thanks, then it might be the ofono upload then indeed08:17
abeatojibel, sil2100 the crash happens when indicator-network tries to access a non-existing interface08:17
abeatoSimManager, when there is no SIM08:17
sil2100abeato: oh08:17
abeatojibel, can you confirm that you have no SIM inserted=08:17
abeato?08:17
jibelabeato, confirmed08:17
abeatohm, weird thing, ofono has not changed its behaviour with regard to when the interfaces appear08:18
bzoltan1Mirv:  the address book app has exactly the same failures on CI dash as with the UITK silo tests08:18
sil2100abeato, jibel: makes sense, the indicator works fine here on my mako with a sim inserted08:19
abeatobut imho this should be sorted out in indicator-network08:19
zbenjaminogra_: is there any problem with the 174 emulator image? http://pastebin.ubuntu.com/7959173/08:20
sil2100abeato, jibel, ogra_: in any case, I informed mandel who was the lander for the ofono landing about the regression08:21
bzoltan1sil2100:  Mirv: I have flipped the UITK landing to be tested. I did see shitload of failures but nothing what is not failing on the CI dash already. The shorts have the shorts_app.tests.test_rssreader.TestMainWindow.test_open_listmode_feed_item failing08:21
sil2100bzoltan1: ACK, we'll try landing this today then, thanks for your hard work in testing it throughly :)08:22
bzoltan1sil2100:  I am just doing my job :)08:23
bzoltan1sil2100: I am checking that shorts failure just to be super sure...08:23
jibel172 already, did we switch to 1 build per hour :)08:24
ogra_heh08:26
abeatojibel, sil2100, ogra_ the only thing that could have triggered this bug is that now there are a couple of interfaces that were not there previously when there was no SIM, which maybe confuses indicator-network08:28
Mirvbzoltan1: it seems good to me, then, as good as can be testable under the circumstances.08:28
bzoltan1Mirv:  yes, the shorts app failure we are investigating with kalikiana, to be hypersure. But i think this UITK is good to go.08:29
Mirvbzoltan1: https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_08-04/+merge/229487 not approved08:29
abeatoWellark, ping08:30
bzoltan1Mirv:  ohh.. again I forget ... sorry, approved08:30
Mirvbzoltan1: ^ -gles missing08:35
Mirvbzoltan1: are you on it, or do you want to me to try it?08:37
bzoltan1Mirv:  no need, I captured it. There is a bug in the shorts tests...we are on it08:38
Mirvaha, ok08:39
Mirvrsalveti: can you ack https://ci-train.ubuntu.com/job/landing-015-2-publish/40/artifact/packaging_changes_messaging-app_0.1+14.10.20140804-0ubuntu1.diff (you tried to publish it before but didn't ack the changes)?08:41
Chipacaanybody around here know what a GhostRevisionsHaveNoRevno error from bzr means? or more pointedly, how to fix it?09:00
oSoMoNsil2100, good morning! can I have a silo for line 42, please?09:04
sil2100oSoMoN: hello! Let me take a look at that :)09:05
Mirvbzoltan1: I put the testing status back to No until you're ready09:36
bzoltan1Mirv:  OK09:36
Mirvmaybe ogra_ could ack this? https://ci-train.ubuntu.com/job/landing-015-2-publish/40/artifact/packaging_changes_messaging-app_0.1+14.10.20140804-0ubuntu1.diff09:37
Mirvsince ricardo seems away09:37
Mirvdoes not seem rocket science level of pkging changes09:37
jibelpsivaa, can you remind me the bug # for precise alternate installation failure ?09:44
psivaajibel: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/135126209:45
ubot5Launchpad bug 1351262 in xorg-lts-transitional (Ubuntu) "precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (>= 0~)'" [Undecided,New]09:45
jibelpsivaa, thanks09:46
LaneyMirv: that is like the worst changelog09:47
Laneyit's impossible to assess these changes in isolation09:48
=== psivaa is now known as psivaa-reboot
mandelsil2100, you might be able to give me a hand, I'm getting the following when executing debuild -uc -uc09:55
mandelsil2100, dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at09:55
mandelsil2100, but I've never had that issue, any idea?09:55
Mirvindeed the changelog does not explain the additional dep (or cmake changes)09:57
sil2100mandel: hi! For what project does that happen? If you're doing it for some of our upstream projects then you need to make sure the tarball is  there, as it's being generated by bzr09:59
mandelsil2100, I'm doing it for the location-service, AFAIK nothing has changed we only bumped the version09:59
sil2100mandel: try running bzr bd first to generate the tarball10:00
popeyooh! screen wakes on alarms10:00
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): psivaa | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
seb128Mirv, that diff has a buggy indentation, using a tab in the build-depends which is space indented10:03
mandelsil2100, strange bzr bd works10:06
sil2100mandel: bzr bd will always work as how our ubuntu projects work is:10:06
sil2100mandel: the tarball is generated from the bzr tree by using the split option, so bzr bd actually generates the upstream tarball from the source on every build10:07
tvossmandel, we changed the source format10:08
sil2100mandel: without bzr bd, debuild has no knowledge about how to generate the tarball, so it will fail if it doesn't find it already generated10:08
mandeltvoss, ah, I missed that10:08
mandelsil2100, ok, thx10:08
Mirvrenatu: see seb's and laney's comments regarding landing-01510:11
Mirvif renatu is renato, that is :) bill and boiko not around10:12
popeypsivaa: can you please trigger https://code.launchpad.net/~bzoltan/ubuntu-rssreader-app/select_many/+merge/229590 to do the jenkins dance?10:16
psivaapopey: let me take a look10:19
popeythanks psivaa10:20
bzoltan1Mirv:  We got the shorts app failure. the Shorts app needs a single line change to make it OK -> https://code.launchpad.net/~bzoltan/ubuntu-rssreader-app/select_many/+merge/229590 popey promised to take care of it.10:21
davmor2popey: do you have the youtube scope enabled?10:21
davmor2installed even10:21
popeyyes10:22
davmor2popey: if you select anything does it play ever?10:22
popeyoh, i thought i did, but i dont10:22
popeywhere'd that go10:23
* popey installs10:23
davmor2popey: also if you try swiping the resulting youtube video window from right to left to close it does it jolt back and then not be able to swipe away10:23
popeydavmor2: youtube playback appears to be broken in the browser10:25
sil2100Ok, for a moment I thought dogfood was down10:27
davmor2popey: works fine from your app though10:27
Mirvbzoltan1: excellent!10:27
sil2100But then I noticed that the internet is down10:27
sil2100duh10:27
popeydavmor2: yeah, you're right10:28
popeyodd10:28
davmor2popey: so I don't think it is the playback that is broken I think it is the direct link format it is using10:29
popeywell the video playbox box appears10:29
davmor2popey: yeah but no fullscreen button and the sound is muted and it doesn't play, so I'm wondering if it is linking to the flash version instead of the html5 versions maybe as a huge guess10:31
popeyunlikely as the video render box appears10:31
popeyhmm, going to m.youtube.com in the browser works10:32
popeyi wonder if its adverts that aren't playing10:32
davmor2popey: could be10:32
davmor2popey: it is definitely something specific to the video url that is produced from the scope10:33
bzoltan1Mirv:  may I get a silo for the QtC plugin?10:34
popeydavmor2: shelling in to get the url it launched with...10:34
popeywebbrowser-app https://www.youtube.com/watch?v=7-7knsP2n5w  for me10:35
popeythat video clearly works on desktop10:35
popeyhas no adverts for me here (no adblock)10:35
bzoltan1Mirv:  line 4310:35
Mirvbzoltan1: done10:42
bzoltan1Mirv:  thanks10:43
davmor2popey: I just dropped that line into my utopic desktop and I got The Adobe Flash Player is required for video playback, get the latest flash player10:45
davmor2popey: as in the whole of webbrowser-app https://www.youtube.com/watch?v=7-7knsP2n5w that line10:46
popeyso maybe a video that's not available in html5?10:46
bzoltan1Mirv:  So, what is the plan with the UITK landing?10:46
davmor2popey: works fine via your app10:48
=== oSoMoN_ is now known as oSoMoN
davmor2popey: so I think the issue is that the link is to the desktop flash version,  I wonder if there is a way to find the url from your app and compare it10:50
popeywell, the test would be to try and play the same video in the app10:51
popeyok, tested that, found that video in my app and it plays fine10:52
davmor2popey: there is no m. at the start of the link, I bet the scope is basically presenting itself as though it were a desktop app not a mobile one10:54
popeywell its the browser really10:54
popeynot the scope10:54
popeyi dunno ☻10:55
Mirvbzoltan1: step 1 is someone setting it back to tested :)10:55
davmor2popey: well I'm assuming that the scope is say open to this link10:55
davmor2popey: meh no it does show as m.youtube.com so that blew that theory out of the window10:56
bzoltan1Mirv:  Ohh... i can be that someone :)10:57
popeypsivaa: any luck with https://code.launchpad.net/~bzoltan/ubuntu-rssreader-app/select_many/+merge/229590 ?10:57
psivaapopey: i added bzoltan in the the jenkins instance as allowed user. that should trigger the job. it hasn't triggered yet. digging  more on this10:58
popeythanks10:58
Mirvnot really, just the automated gles watch thing11:01
psivaapopey: sorry about that. i had a typo earlier. the job has triggered11:02
psivaapopey: as you might have seen.. that MP needs some fixing11:04
brendandsil2100, is the messaging-app failure not a known issue?11:11
brendandsil2100, it's been reproducible for a while11:11
sil2100brendand: not sure - is it reproducible locally?11:11
brendandsil2100, yes11:11
brendandsil2100, been failing consistently since 165 on friday11:11
brendandno wait, that was last monday actually11:12
davmor2brendand: is this the issue for the icon missing or something?11:12
brendanddavmor2, yeah11:12
=== MacSlow is now known as MacSlow|lunch
brendanddavmor2, is there a bug for it? is someone looking at it?11:17
davmor2brendand: pass sil2100 ^  is there a bug for that?11:17
Chipacasil2100: don't forget https://code.launchpad.net/~chipaca/ubuntu-system-settings/gsettings-schema-depends-fix/+merge/229567 when you have a gap (hah)11:21
sil2100brendand: davmor2: uh, we might have 'missed' it in all this commotion, let me poke boiko as soon as he's up - but it might be fixed by the landing they prepared as well11:22
sil2100As he mentioned some things in other apps as well11:23
sil2100Chipaca: sure :)11:23
brendandsil2100, which silo is that? i can try it out11:24
sil2100brendand: let me see11:25
sil2100brendand: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-01511:25
brendandsil2100, cool11:25
sil2100brendand: this is ready for landing actually, so I'll publish this in a moment anyway :)11:25
brendandsil2100, it's also meant to fix address book?11:25
sil2100Yes11:25
sil2100At least from what boiko said ;)11:25
Mirvsil2100: seb + lane_y had comments about the packaging changes11:32
Mirvon that one11:32
sil2100Ok, didn't look at those yet as I still didn't finish something else11:32
MirvI added the comments to the sheet11:34
bzoltan1ogra_: I have a new API for the seeds -> https://code.launchpad.net/~bzoltan/ubuntu-seeds/add_settings/+merge/22960211:43
sil2100grrrr11:44
renatuMirv, the only problem on silo15 is the indention? or there is any other problem?11:45
renatuMirv, fix pushed11:46
Mirvrenatu: the changelog (=commit message) also doesn't explain the cmake file changes or the additional new build dependency11:47
renatuMirv, how I can fix that? can I edit the changelog manually?11:48
Mirvrenatu: you change the merge request's commit message11:49
renatuok11:49
Mirvrenatu: for example https://code.launchpad.net/~renatofilho/address-book-app/release-2014-08-04/+merge/229528 now only has "Visual update"11:49
renatuMirv, I have updated the messaging mr commit message11:55
renatuMirv, the address-book-app only contains visual updates, more details about the changes can be found in each commit message11:56
ogra_sil2100, looks like android is in the archive, if you dont have anything pending i'll start a build now11:59
sil2100hmm11:59
sil2100ogra_: one moment11:59
=== tvoss is now known as tvoss|test
ogra_ok11:59
=== tvoss|test is now known as tvoss
sil2100Mirv: so, what were the comments from seb regarding the address-book etc. landing?12:00
Saviqsil2100, recon on silo 7 please, added qtmir-gles12:00
sil2100Saviq: ACK12:01
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cihelp | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
Mirvsil2100: see sheet, renato is now fixing them. cosmetic+reviewability12:06
=== alan_g is now known as alan_g|lunch
sil2100_Saviq: sorry, internet problems... did anyone reconfigure in the meantime?12:12
popeypete-woods: youtube scope approved to store..12:13
pete-woodspopey: thanks!12:13
tvosssil2100_, any plans to spin an image with the language pack updates in? dist-upgrading the device is taking ages right now12:14
=== MacSlow|lunch is now known as MacSlow
sil2100_ogra_: ok, could you kick a new image ;)?12:14
sil2100_ogra_: I guess it's the right time now12:15
Saviqsil2100_, nope12:15
jhodappMirv, land line 27 first12:15
sil2100_Saviq: ok, reconfiguring then12:15
ogra_sil2100_, you mean to make the peopple using unsupported upgrade methods happy ?12:15
* ogra_ bets when tvoss just waits for dist-upgrade to finish he will still be twice as fast as the image builder :) 12:16
tvossogra_, exactly, those developers trying to move as fast as possible12:16
tvossogra_, sure, not questioning that12:16
tvossogra_, it's not only me waiting for language pack installations finishing righ tnow12:17
ogra_sil2100_, ugh, i cant !12:17
ogra_stgraber, iso tracker is not offering me a build button ...12:17
cjwatsonbet you aren't logged in12:17
ogra_i am12:18
ogra_(guessing by the "log out" button next to my name in the top right)12:18
ogra_;)12:18
cjwatsonI get the usual checkboxes and "Request a rebuild"12:18
cjwatsonSo I can kick it for you if you like12:18
ogra_yes please ... though i would like to be able to do it myself without having to use nusakan12:18
ogra_:/12:18
cjwatsondone12:19
ogra_thx12:19
ogra_aha !12:20
ogra_SSO was nice enough to uncheck the ubuntu-touch-imagebuilders membership for me :P12:20
ogra_that was checked last week ! silly thing12:21
slangaseksil2100_: so, any sign of new issues with the qt4 removal?  Or is it hard to tell because of masking by the general networking problems?12:22
Mirvjhodapp: ok, you have silo now for that12:23
jhodappMirv: thanks12:24
imgbot=== trainguard: IMAGE 173 building (started: 20140805 12:25) ===12:25
brendandsil2100_, yeah silo15 fixes it :)12:25
renatusil2100_, Mirv , do you need any other fix?12:26
popeybzoltan1: approved your branch, when it lands we'll ship a new shorts to the store12:26
renatusil2100_, Mirv can we land this in the next image?12:26
ogra_slangasek, heh, well, hard to tell since the results are currently so broken that we essentially are flying blind12:26
ogra_slangasek, the apparmor denials make the world explode12:26
bzoltan1popey: Thank you very much12:26
popeynp12:26
slangasekogra_: ack12:26
bzoltan1popey: and by the way. We will have a permanent solution from the UITK to avoid similar problems in the future.12:27
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): cprov | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
Mirvrenatu: did you fix the LP pages' "commit message" fields for all MPsbto be more descriptive? (explaining packaging / makefile changes to make them reviewable in the packaging diff)12:36
popeybzoltan1: great!12:40
renatuMirv, done12:42
sergiusensjibel: ogra_ for what it's worth, I had indicator-network crashing ever since I was on the road last Wednesday; failed to start12:44
ogra_sergiusens, ouw !12:44
=== alan_g|lunch is now known as alan_g
Saviqdavmor2, hey, would you have time to do QA sign off on silo 7?12:45
sergiusensogra_: my process was; open terminal and: "start indicator-network"12:45
ogra_heh12:46
sil2100_psivaa: hey, were you able to re-run those tests in 171?12:47
=== sil2100_ is now known as sil2100
sil2100slangasek: so, from what I see things seem to be a bit brokenish...12:48
ogra_lol12:48
sil2100ogra_: did you see test results for 172 :/ ?12:48
ogra_diplomat !12:48
ogra_sil2100, "totally screwed" would be my expression :)12:48
sil2100;)12:48
sil2100I personally don't feel like looking at the dashboard right now12:49
Mirvrenatu: thanks, looks very good now! I'm doing a quick rebuild, after that a smoke test should be done (no code changes) and someone of you landers should set the silo back to "Testing pass?" "Yes" for publishing.12:50
renatuoSoMoN, could you do that ^^12:51
renatuMirv, thanks12:51
psivaasil2100: hmm, weird. by the time the tests kicked off, 172 must have been available. the job picked up 172 :/12:52
psivaasil2100: if you'd like the same ones with 171 i could rerun them again. sorry dint notice this 172 being on the way12:52
sil2100cjwatson: hi! Could you by any chance branch lp:~sil2100/cupstream2distro/cu2d-rtm again on snakefruit? I added a ton of other workarounds to enable it working for both DF and LP simultaneously12:53
sil2100psivaa: yeah, if you could do it for 171 it would be awesome, as 172 is b0rken badly12:53
psivaasil2100: will do12:54
sil2100psivaa: thanks :)12:54
cjwatsonsil2100: done12:55
davmor2Saviq: I'm just back from Lunch.  Give me a few minutes to just look and see if anyone has got back to me with anything and then I'll happily have a look for you12:58
Saviqdavmor2, great, thanks12:58
sil2100cjwatson: thanks!13:01
=== pete-woods is now known as pete-woods|lunch
sil2100Mirv: if you publish anything, remember to lookout for issues with package uploads to the archive ;)13:06
sil2100Mirv: the copy2distro I made is a big hack right now, as I didn't want to modify the other code-paths13:06
Mirvsil2100: seems to have worked so far13:10
ogra_hacks ... the glue that holds the world together13:12
ogra_:)13:12
oSoMoNrenatu, sorry, I’m lacking context, what do you need?13:13
psivaaslangasek: we're having whoopsie test in default set for some images now: http://ci.ubuntu.com/smokeng/utopic/touch/mako/172:20140805.1:20140728.1/9490/default/1486871/13:13
renatuoSoMoN, I need you to mark silo 15 as Yes for testing pass13:14
psivaaslangasek: curious if you'd know what caused it?13:14
oSoMoNrenatu, have you actually tested it according to the test plan?13:14
renatuoSoMoN, yes13:17
psivaaslangasek: ok, I think you could ignore me: i see https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1351137 is the reason for it from the comments13:17
oSoMoNrenatu, ok, will do in a moment13:17
renatuoSoMoN, Thanks13:17
ubot5Launchpad bug 1351137 in ubuntu-system-settings (Ubuntu) "ubuntu-system-settings-wizard does not create /var/lib/apport/autoreport on first boot" [Critical,Confirmed]13:17
slangasekpsivaa: ah, I would have expected that test to be working.  Do the devices get reflashed for each test?13:20
slangasekpsivaa: or are they upgraded?13:20
slangasekpsivaa: I do want the test to actually be passing ;)13:20
psivaaslangasek: they are flashed every time at least before the default tests13:21
slangasekok, good13:21
slangasekgood that you're doing this; bad that whoopsie_upload_all is apparently still not running13:21
bzoltan1Mirv: sil2100: the silo8 is good to go13:28
sil2100bzoltan1: publishing :)13:29
Mirvpublish.. not13:29
Mirvsil was too fast, again :)13:29
psivaaslangasek: looks like it's running but not within 20 seconds13:29
slangasekpsivaa: this is highly improbable13:29
slangasekpsivaa: it's inotify-driven, and creating the .upload files is a quick operation13:30
slangasekI tested the script locally in an environment here on a device that did have /var/lib/apport/autoreport, and it was near instantaneous13:30
psivaaslangasek: ok, not sure why the delay was.. but it took more than 20 seconds for me to see whoopsie-upload-all to run after i sent the -SEGV kill signal13:31
slangasekpsivaa: yes, but the delay is between sending the signal and the creation of the .crash file, not between creation of the .crash file and creation of the .upload file13:32
slangasekpsivaa: it should never take more than a second to create the .upload file for the .crash file13:32
slangasekand here, even the .crash file was created within 2 seconds13:33
psivaaslangasek: it's taken more than 20 sec again here. would it be different if the crash is on unity8?13:37
psivaaand i saw the .crash appearing instantaneously13:37
slangasekpsivaa: whoopsie_upload_all should still be quick13:37
slangasekpsivaa: oh13:37
boikosil2100: sorry, I tested everything yesterday, but forgot to mark the silo as tested, just did it13:38
slangasekpsivaa: that implies that the .crash is not being created atomically13:38
slangasekpsivaa: let me dig13:38
brendandsil2100, psivaa - what's happening with the ci results? did the rerun not have any effect?13:38
psivaaslangasek: let me paste the ls -lart details13:38
sil2100brendand: what do you mean?13:38
sil2100brendand: it's still re-running 171, but 172 is completely b0rken13:38
brendandsil2100, oh right. because of the network?13:39
sil2100brendand: no, 172 might be b0rken becasue of qt4 being gone I suppose...13:39
sil2100hah!13:40
boikosil2100: oh, wait, I think I I marked the silo as tested, renatu just told me he fixed some more things, so I'll be testing again13:41
psivaasil2100: brendand with 171 rerun the results are still running: http://ci.ubuntu.com/smokeng/utopic/touch/mako/171:20140805:20140728.1/9484/ improvement i guess13:42
sil2100boiko: I think some core-devs had some packaging issues13:42
stgraberogra_: yeah, sso is a bit weird, never quite got how it decided what to keep selected13:43
ogra_stgraber, yeah, i thought if i had it selected it once it keeps it13:43
ogra_seems not :P13:43
davmor2Saviq: right installing now I'll get back to you in an hour or so13:44
brendandsil2100, because of qt4 being gone?13:46
ogra_unlikely13:46
ogra_the 100s of apparmor denials and non-working network are more likely i think13:47
sil2100brendand: 172 dropped qt4 packages, that was the biggest change... but not sure about that - what we know for sure is that it's horrible ;p13:47
Saviqdavmor2, awesome, thanks13:47
jdstrandogra_: what is causing the 100s of apparmor denials?13:48
brendandsil2100, there appear to be a whole load of dbus errors13:48
ogra_jdstrand, same issues still13:48
jdstrandautopilot?13:48
ogra_jdstrand, yeah, dbus introspection errors from autopilot13:48
jdstrandI wonder if plars got his changes pushed out in those tests13:49
ogra_i hope plars was able to collect some info with your changes from yesterday13:49
jdstrandogra_: can you point me at a log?13:49
ogra_jdstrand, https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/657/consoleFull13:49
ogra_after all the syslog or console log of most of the red ones on http://ci.ubuntu.com/smokeng/utopic/touch/mako/172:20140805.1:20140728.1/9490/13:50
jdstrandI see the output from aa-clickhook. it didn't crash and exited properly and the rules are applied based on adb-shell /home/phablet/bin/check-clickhook-rules13:52
jdstrandADB_RC=013:52
bzoltansil2100: thank you13:54
plarsjdstrand: I pushed the changes into our scripts,  but the phablet-config one hasn't landed yet13:54
plarsjdstrand: did it happen again?13:55
jdstrandso I'm told13:55
jdstrandI'm looking now13:55
plarsjdstrand, ogra_: if you grep the log for check-clickhook-rules, you'll see where the checks run13:56
plarsjdstrand: the log ogra_ posted doesn't seem to have any failures on it though13:56
jdstrandI don't see autopilot denials13:56
jdstrandhttps://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/657/ has failures, but they aren't autopilot13:57
jdstrandso, there is the known gallery and notes denials13:57
psivaahttps://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/653/artifact/clientlogs/camera_app/syslog/*view*/ has the denials13:57
jdstrandthe media-hub denials13:58
jdstrandthen13:58
jdstrandbut those should be fixed in the latest mediahub13:58
jdstrandlet me check that13:58
jdstrandthat build doesn't seem to have media-hub 1.0.0+14.10.20140731-0ubuntu113:59
jdstrandthat ^ may be the cause of the music-app failures14:01
psivaajdstrand: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/658/consoleText also has denials corresponding to camera and clock app tests on 17214:02
psivaajdstrand: hang on pls. wrong link14:02
psivaajdstrand: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/656/artifact/clientlogs/ubuntu_terminal_app/syslog/*view*/14:03
psivaais the right one sorry14:03
* jdstrand wonders why the log goes back to Jan 714:04
imgbot=== trainguard: IMAGE 173 DONE (finished: 20140805 14:05) ===14:05
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/173.changes ===14:05
davmor2popey: hmmm In calendar app I see something weird.  In month view I see Dots for appointments in July, I also see them for September but August is blank14:05
jdstrandplars: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/656/artifact/clientlogs/ubuntu_terminal_app/syslog/ has autopilot denials14:05
brendandsil2100, want me to check out the autopilot/dbus issues?14:06
sil2100brendand: if you could help out with that it would be excellent!14:06
plarsjdstrand: I don't see any check-clickhook-rules failures there though14:07
brendandsil2100, ok i'll have a look and see what i can find14:07
jdstrandno, me either14:07
brendandsil2100, it's new in 172 right?14:07
MirvLaney: ack request renewed, https://ci-train.ubuntu.com/job/landing-015-2-publish/lastSuccessfulBuild/artifact/packaging_changes_messaging-app_0.1+14.10.20140805-0ubuntu1.diff14:09
jdstrandplars: if I look in https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/656/consoleFull, and search for 'testing ubuntu_clock_app'14:10
jdstrandplars: where is the check-clickhook-rules check before it?14:11
brendandsil2100, it seems to be only click packages affected14:12
davmor2Saviq: with silo 007 in place why would the videos scope carousel stop displaying video snapshots?  They are just blank grey tiles with a title now14:12
brendandsil2100, maybe something broke in the --enable-dbus-probe tool14:13
jdstrandplars: it seems like it goes from dropping letters to clock-app, but we don't verify the click rules are in effect when the clock app starts14:13
Saviqdavmor2, anything relevant in .cache/upstart/unity8-dash.log ?14:13
Saviqdavmor2, sounds like the thumbnail generation failed14:13
sil2100brendand: then it might most possibly be the same issue we've been seeing already - I see jdstrand and plars are looking into it all the time14:13
jdstrandoh14:14
jdstrandplars: under 'testing ubuntu_clock_app' there is a 'reboot'14:14
davmor2Saviq: the thumbnails are then in the video view where they are nolonger in carousel14:14
jdstrandplars: oh no, I see after the reboot there is a /home/phablet/bin/check-clickhook-rules14:16
plarsjdstrand: yeah, sorry I'm in a meeting right now. It reboots before each new testsuite14:16
plarsjdstrand: which reruns the setup steps like phablet-config14:17
jdstrandplars: yeah, disregard that14:17
jdstrandseems like somewhere between adb-shell /home/phablet/bin/check-clickhook-rules and 10:19:58.379 ERROR proxies:410 - Introspect error on :1.74:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender=":1.72" (uid=32011 pid=3746 comm="/usr/bin/python3 -m autopilot14:19
davmor2Saviq: http://paste.ubuntu.com/7961520/14:19
jdstrandplars: I have to step into a meeting, but can you give me a link to check-clickhook-rules?14:19
Wellarksil2100: did you have something for me?14:20
Saviqdavmor2, there's only one 'D-Bus error:  "Could not get thumbnail"'14:20
plarsjdstrand: here's the mp from yesterday that shows pretty clearly the change I made yesterday: https://code.launchpad.net/~pwlars/ubuntu-test-cases/touch-add-aa-clickhook-check/+merge/22951314:20
Saviqah but that's for albums anyway14:20
Saviqdavmor2, I'll need to have a look14:20
sil2100Wellark: hello! Most probably, yes, as indicator-network is having issues in our current images14:20
sil2100Wellark: I suppose you are the right person to poke about this? :)14:21
Wellarkthis one? https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/135274414:21
ubot5Launchpad bug 1352744 in indicator-network (Ubuntu) "List of WiFi access point is empty" [Critical,In progress]14:21
sil2100Wellark: it seems that after the last ofono update bug LP: #1352744 appeared14:21
Wellarkyeah. ok. I will investigate14:21
sil2100Wellark: yes, it seems to segfault whenever the simcard is not inserted :)14:21
sil2100Wellark: thanks!14:21
Wellarkactually there might be two bugs in that one14:22
Wellarkanyway.14:22
WellarkI'll start triaging14:22
davmor2Saviq: http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-152139.png  vs  http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-152222.png14:23
popeythe contacts ui seems to have broken recently14:28
sil2100Wellark: it might, we also saw many indicator-network crashes during smoketesting, which is using the ofono-phonesim-autostart14:28
sil2100Wellark: just so you know14:28
davmor2popey: how so?14:28
sil2100People! Stop breaking things!14:29
popeyoh jees, this image is bad14:29
sil2100popey: 173?14:29
popeyyes14:29
ogra_blame tvoss14:29
davmor2popey: other than the image being slightly bigger and closer to the first letter14:29
ogra_he asked for ti14:29
ogra_*it14:29
popeyhttp://imgur.com/EnFvIP814:30
sil2100Well, it also has a new UITK14:30
popeytext alignment is all wrong14:30
Wellarksil2100: ack14:30
sil2100popey: I think we need to blame bzoltan for that!14:30
sil2100bzoltan: confess!14:30
popeythe clicks store has white arrow in the title14:30
popeyhttp://imgur.com/9C5elck14:30
popeyand white search icon14:31
sil2100bzoltan, t1mp: could you take a look at the issues that popey is mentioning above ^ ?14:31
brendandsil2100, hmm - so i don't have a problem after i run 'phablet-config autopilot --dbus-probe enable'14:33
brendandsil2100, are psivaa/plars sure that somehow didn't fail to run?14:33
brendandsil2100, because it certainly looks like it14:33
sil2100I think there was some lead once that something could have getting in the way with that14:33
ogra_brendand, well, the consolelog should have the full info14:34
ogra_(just hard to read there)14:34
brendandogra_, it does say it runs that14:35
brendandogra_, multiple times for some reason (maybe once per suite)14:35
brendandalthough that's unneccesary14:36
ogra_yep14:36
ogra_one per suite14:36
ogra_it should also show the return value iirc14:36
ogra_or at least spill an error if it fails14:36
mandelsil2100, do you have the rights to trigger a rebuild ps job, one of the tests failed because the machine had a lot of load (http://s-jenkins.ubuntu-ci:8080/job/ubuntu-download-manager-ci/712/rebuild)14:36
mandelsil2100, this MR - https://code.launchpad.net/~mandel/ubuntu-download-manager/content-disposition/+merge/22880414:37
davmor2popey: it's black here but I have Saviq silo installed14:37
popeyi dont have any silos, vanila 17314:37
sil2100mandel: yes, let me try that14:37
mandelsil2100, awesome, thx14:37
davmor2Saviq: okay so other than the carousel I don't see anything else that looks broken so far14:37
Saviqdavmor2, ok, I'll find out what's going on there, thanks14:38
sil2100mandel: ok, retriggered14:38
mandelsil2100, thx, really appreciate it14:38
davmor2popey: on flo it looks fine14:40
sil2100yw :)14:40
plarsbrendand: that what failed to run?14:41
Saviqdavmor2, hmm showed up fine here...14:42
Saviqdavmor2, can you try searching for something and clearing the search then?14:42
brendandplars,  'phablet-config autopilot --dbus-probe enable'. i can see in the console log it did run14:42
plarsbrendand: phablet-config autopilot --dbus-probe does run as a setup step for each testsuite, yes14:42
davmor2Saviq: sure14:42
brendandplars, but it clearly wasn't succesful, somehow14:42
brendandplars, i don't have any problem when running locally14:42
bzoltansil2100:  I admit everything .. i am a good person to blame for whatever reason :)14:42
plarsbrendand: there is a problem with phablet-config that I have an MP for that fixes the fact that it will eat the errors if it fails14:42
plarsbrendand: the very next thing we run after phablet-config autopilot runs a script from jdstrand to check that the aa-clickhook stuff was run properly. So if it phablet-config does fail, we should see the effects of it from that14:43
plarsbrendand: all the logs I've looked at so far today indicate that it passed though. Are you finding one for certain that failed?14:44
brendandplars, well the ci failures in 172 are all the same dbus error14:44
brendandplars, which are identical to the ones you get if you didn't run phablet-config autopilot14:44
plarsbrendand: but that's clearly not the problem in this case...14:46
bzoltansil2100: popey: let me check if the UITK is the source of that14:46
brendandplars, well i can't reproduce it locally, so i've nothing else to suspect14:46
plarsbrendand: so something else is going on14:46
plarssergiusens: did you happen to look at my mp for phablet-config?14:47
jdstrandplars: looking at https://code.launchpad.net/~pwlars/ubuntu-test-cases/touch-add-aa-clickhook-check/+merge/229513, check-clickhook-rules is fine. is the adb-shell command perhaps ignoring an error or not displaying output (like the other issue we saw?)14:49
plarsjdstrand: adb-shell is just a wrapper for adb that lets us actually get the return code from a shell script that runs, and it does not eat output14:50
jdstrandok14:50
plarsjdstrand: if we ran adb directly, we wouldn't get the exit code14:50
jdstrandplars: so, looking at https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/656/consoleText, grep for 'testing ubuntu_clock_app'. you'll see the tests failing due to autopilot down below14:51
plarsjdstrand: right, that's the one I'm looking at right now14:51
sil2100ogra_: hm, I won't make it for the evening meeting today - could you lead it in my stead? :)14:52
jdstrandplars: is it possible somewhere between check-clickhook-rules and the first failure that a click is getting installed?14:52
ogra_sil2100, lol, because its a tricky one ?14:52
ogra_:)14:53
jdstrandplars: (the first check-clickhook-rules under 'testing ubuntu_clock_app' that is14:53
jdstrand)14:53
plarsjdstrand: no, we don't install any clicks, unless the test case itself is doing it14:53
jdstrandplars: would we see in this output if it is?14:53
plarsjdstrand: I don't know what clock app tests are doing internally, but I seriously doubt they have it installing a click app14:55
sil2100ogra_: of course!14:55
jdstrandI'm starting to suspect that while the profiles have the autopilot rule, the cache file may not14:56
jdstrandplars: I have to step into a meeting, but I'm going to need some more output. I'll give you a script after my meeting. will I be able to run it as root?14:57
plarsjdstrand: certainly. I'm still trying to reproduce this here too14:58
davmor2popey: your bug about twitter in the indicator, did you notice that the osd notification actually has the avatars in :)14:58
jdstrandplars: I'm not super confident in the timestamps at this point due to: Aug  5 09:30:46 ubuntu-phablet ntpdate[2552]: step time server 91.189.89.199 offset 1406642012.683614 sec14:59
=== pete-woods|lunch is now known as pete-woods
jdstrandplars: (timestamps are used when compiling policy so we can use cache files)14:59
jdstrandplars: my script will attempt to see if that is the issue15:00
* jdstrand -> meeting15:00
boikosil2100: is there any thing I need to do on silo 15 now, or is it just a matter of having a core dev to ack the packaging changes now?15:00
t1mppopey: about the color of the back button, did you notice issues with that in apps as well? or dash only?15:01
popeyt1mp: its fine in dialer, messaging15:02
t1mppopey: ok, thanks15:02
popeynp15:02
oSoMoNsil2100, hey, can silo 6 be published, please?15:04
MirvoSoMoN: did that for sil15:05
Mirvwhile publishing qt declarative as well15:05
oSoMoNMirv, awesome, thanks!15:05
oSoMoNMirv, sil2100: can I have a silo for line 47, please?15:09
MirvoSoMoN: done, but be sure to clean the previous webbrowser app silo as soon as it has migrated15:19
oSoMoNMirv, of course, thanks!15:19
popeysil2100: it's not possible to uninstall apps on 17315:21
popeydavmor2: ^15:21
ogra_popey, are you sure that wasnt there on 172 ?15:22
ogra_i mean ... the changeset is three packages for 173 ... (plus language updates)15:22
popeyi dont know15:22
popeyso entirely possible15:23
davmor2popey, ogra_: I need to reflash to clear out the silos so I'll do 172 and see what happens there15:24
ogra_davmor2, thanks ... i dont think it can be 173 specific15:24
tvossdavmor2, ping15:27
davmor2tvoss: hello15:29
davmor2ogra_: actually can you give me write access to the silo spreadsheet so I can mark QA approved please or mark line 25 as done thanks :)15:32
ogra_davi dont know if i can :/ or how i would15:32
ogra_*davmor2 ^^15:33
davmor2ogra_: haha no worries definitely a job for sil2100 then15:33
ogra_i think you need robru for that15:33
ogra_or sil2100 yeah15:33
* sil2100 does that15:35
sil2100davmor2: I'll give ya access15:35
sil2100davmor2: now switch it yourself ;)15:35
davmor2sil2100: ta15:36
davmor2oh get you with your fancy granted :)15:37
davmor2sil2100, Saviq: Done granted :)15:37
Mirvsil2100: hey MOTU :) could you ack this universe pkg? https://ci-train.ubuntu.com/job/landing-015-2-publish/lastSuccessfulBuild/artifact/packaging_changes_messaging-app_0.1+14.10.20140805-0ubuntu1.diff15:39
Saviqdavmor2, thanks!15:40
Saviqlet's land this!15:40
Saviqwho wants to push the button on silo 7? ;)15:41
MirvI can, but it'll need packaging acks15:41
SaviqMirv, I can strong-arm mterry to get you those :)15:41
MirvSaviq: give him https://ci-train.ubuntu.com/job/landing-007-2-publish/34/artifact/packaging_changes_unity8_8.00+14.10.20140805-0ubuntu1.diff15:42
Saviqmterry, have a look please ↑?15:42
* mterry looks15:42
sergiusensslangasek: can you help me out with http://people.canonical.com/~platform/citrain_dashboard/#?q=sergiusens ? preNewing15:43
Mirvsergiusens: seb promised to try to do that but didn't get to that15:46
mterrySaviq, Mirv: from a debian-packaging POV, seems fine15:46
sergiusensMirv: yeah, that's why I started to roll; not sure who preNew queues work or if archive admins get to notice them15:47
* Mirv should not start straight after vac with days this long15:47
Mirvmterry: thanks. if you don't mind, there'd be a smaller https://ci-train.ubuntu.com/job/landing-015-2-publish/lastSuccessfulBuild/artifact/packaging_changes_messaging-app_0.1+14.10.20140805-0ubuntu1.diff too15:47
sergiusenss/who/how/15:47
Mirvsergiusens: they're completely manual, the admin needs to check the packaging and eg. copyright headers (seemed fine to me)15:47
sergiusensMirv: yeah, well rsalveti did review the packaging; but the message says to explicitly wait for an archive admin15:48
sergiusens:-)15:48
cjwatsonthe preNEW thing is kind of unnecessary nonsense for source uploads anyway15:48
cjwatsonthey're going to land in actual NEW15:48
cjwatsonit's only new binaries that need prior care because the copy buggily bypasses NEW right now15:49
cjwatsonI think we should stop bothering with preNEW for new sources, and only keep it for new binaries15:49
sergiusensI'll leave yo your discretion then15:50
sergiusensor a core devs if it's fine15:50
Mirvtaking a note of what colin says and pushing publish15:51
Mirvsince ricardo reviewed it anyway15:51
=== gatox is now known as gatox_lunch
mterryMirv, for messaging-app...  (A) the new build-dep should be sorted into the list and (B) "cd obj-$(DEB_HOST_GNU_TYPE); ctest -V" should be "cd obj-$(DEB_HOST_GNU_TYPE) && ctest -V" so that we notice when obj-* isn't created where we expect it.  I'm not sure they are stop-the-line problems at this point in the silo process, but I would normally needs-fixing an MP for them15:53
Mirvmterry: I think sil2100 wants the messaging AP fix in sooner rather than later, but let's get renato___ / boiko to promise they care of those points A and B in the next merge request15:55
camakokgunn, plz ignore the failure above... It didn't fail.15:55
mterryMirv, sure; they aren't showstoppers15:55
kgunnack15:55
Mirvthanks. I'll file a bug against messaging-app15:56
Mirvrenato___ / boiko: filed bug #1352976 for that15:56
ubot5bug 1352976 in messaging-app "Fix small packaging issues as reported in review" [Undecided,New] https://launchpad.net/bugs/135297615:56
elopioMirv: I've top-approved the autopilot branch.16:08
Mirvelopio: thanks. now it'll need a packaging ack still but I'll let someone else handle it or alternatively I'll look pinging some core dev about it in the morning.16:09
elopioMirv: I'll ask for a review there. I am eager to get this branch released :)16:10
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: trainguards | Vanguard (general help): Ursinha | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
popeydavmor2: ogra_ uninstalling is broken in 170 too16:34
* popey goes afk for evening merriment16:35
davmor2popey: can you quickly check if you install an app if it shows in the click store as available still too, that would then confirm my theory of they broke the updater on the scope16:35
popeyok16:35
* popey installs riddling16:36
popeyshows as installed16:36
popeyin both store and click scope16:36
davmor2let me try that again then16:37
camakokgunn, ignore failure msg.. It succeeded. Now starting unity-mir, papi, qtmir...16:39
=== robru_ changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: robru, trainguards | Vanguard (general help): Ursinha | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
popeyreally afk now16:44
oSoMoNsil2100, hey, can I have a silo for line 32 please? it’s an oxide landing, no MR associated, need to copy the source package from the phablet-team PPA to the silo, once assigned16:45
oSoMoNsil2100, I also need silo 8 to be published, when you have a moment. Thanks!16:47
=== robru_ is now known as robru
davmor2popey: from click list net.launchpad.click-webapps.googleplus6 ,  and in the store http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-174829.png16:50
davmor2if I go out of the store and then back in it shows as installed though16:50
=== gatox_lunch is now known as gatox
robruoSoMoN, published16:56
oSoMoNrobru, thanks!16:56
robruoSoMoN, you're welcome!16:56
oSoMoNrobru, have you seen my request a few lines above to get a silo for line 32 for the oxide landing?16:57
robruoSoMoN, no sorry, just waking up ;-)16:57
oSoMoNrobru, « sil2100, hey, can I have a silo for line 32 please? it’s an oxide landing, no MR associated, need to copy the source package from the phablet-team PPA to the silo, once assigned »16:58
robruoSoMoN, ok you got silo 616:58
robruoSoMoN, oh, did you need *me* to copy the source package?16:59
oSoMoNrobru, yeah, I guess I don’t have permissions to copy to a silo PPA16:59
robruoSoMoN, you want this package from this ppa? https://launchpad.net/~phablet-team/+archive/ubuntu/ppa17:00
oSoMoNrobru, yep, from this PPA, only the oxide-qt package, not the webbrowser-app one17:00
robruoSoMoN, ok, submitted the copy, should show up soon17:01
oSoMoNrobru, excellent, thanks!17:01
robruoSoMoN, you're welcome17:01
pmcgowankenvandine, silo 17 has the reset stuff?17:02
oSoMoNrobru, did you do a binary copy? I was told it has to be a source copy, because the phablet-team PPA doesn’t build against utopic-proposed17:03
=== alan_g is now known as alan_g|EOD
robruoh crap17:04
robruoSoMoN, ugh, ok I need to assign a new silo, 6 is shot17:07
oSoMoN:/17:07
Wellarkhey, guys. do we need to land this separately or could we just have it as part of silo 1 ?17:10
Wellarkhttps://code.launchpad.net/~unity-api-team/indicator-network/lp1352744/+merge/22966517:10
Wellarkwhich is ready to land as soon as people can test it (that bug is causing also the current stuff in silo 1 to fail to start)17:10
robruWellark, you're welcome to add that to silo 1, but it looks like somebody tried to publish silo 1 already, so adding that means you have to retest everything else that's already in silo 117:13
kenvandinepmcgowan, looks like it... i wasn't quite ready to prepare that, wanted to figure out the CI failures17:14
kenvandinewhich are clearly all unrelated to those branches :/17:15
robruoSoMoN, ok, did a source copy into silo 1517:15
oSoMoNrobru, thanks!17:15
robruoSoMoN, you're welcome17:15
robruoSoMoN, dunno, the build job is being weird, anyway you can watch the real builds here: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+packages17:16
oSoMoNrobru, yeah, that’s what I usually do17:17
jdstrandplars: ok, can you insert this after the aa-clickhook run: http://paste.ubuntu.com/7962896/17:28
boikoMirv: thanks for the bug report, I'll fix that one17:28
jdstrandplars: or something similar to it. that is going to be very chatty-- maybe redirect to a file per app? I'll let you decide how to report it17:28
jdstrandplars: (that needs to be run as root)17:29
Wellarkrobru: we now have the fix separately in silo 617:30
plarsjdstrand: sure, one min17:30
jdstrandplars: that is only going to be useful on a test run that has the problem unfortunately17:31
=== psivaa is now known as psivaa-holiday
jdstrandplars: you could make the output conditional on if the tests fail. but again, up to you17:32
tvossdavmor2, ping17:39
davmor2tvoss: yeap sorry tea got in the way it's installed I just need to get an app on and test it17:57
tvossdavmor2, browser for the win17:58
davmor2tvoss: indeed but if it doesn't work with the apps it's pointless ;)17:59
davmor2tvoss: still having the same issue with location indicator so I don't know if that is going to knock the gps off or not18:01
davmor2tvoss I have a fix \o/18:04
plarsjdstrand: btw, you've probably already looked at it, but what do you make of the errors in https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/661/artifact/clientlogs/ubuntu_clock_app/application-click-com.ubuntu.clock_clock_1.0.474.log/*view*/18:05
davmor2tvoss: now the wierd news.  So here maps app, asked twice for location,  Once black and white the old webbrowser request and once in colour with a green comfirm button which I assume is the location service.  However when I opened mpas.google.com I didn't get the second request18:06
plarsex:18:06
plarsprocess 3467: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2777.18:06
plarsThis is normally a bug in some application using the D-Bus library.18:06
davmor2tvoss: I'm assuming that is because the browser already had permission from here mapps app?18:06
tvossdavmor2, yup18:13
davmor2tvoss: I rebooted and tried maps.google.com from the browser again and it again only asked once for permission, trying here maps app again now18:15
tvossdavmor2, that's actually great, your answer is cached :)18:17
tvossdavmor2, or better: your previous answer is cached18:17
tvossdavmor2, so with that: rm -rf ~./local/share/UbuntuLocationService to remove the trust db18:17
tvossdavmor2, ideally, the first prompt (within the browser) wouldn't look so much like the actual trust prompt18:20
jdstrandplars: you mean the dconf errors? confined apps aren't allowed to use gsettings18:20
jdstrandplars: the shm stuff is normal and expected18:20
davmor2tvoss: I get them in this order http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-192152.png  and then http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-192837.png  none of the mapping apps or browser show the second one after it has been selected once.  I'm not sure if that is desired behaviour though, once per app at least I would of assumed18:30
jibelToyKeeper, davmor2 could one of you test silo 618:31
jibel?18:31
tvossdavmor2, can you retry please, with prior removing ~/.local/share/UbuntuLocationService and rebooting?18:32
davmor2tvoss: that was18:32
tvossdavmor2, so expected behavior is one actual trust prompt *per* app. So if you open the nokia here app from the store, you should see a trust prompt (colored buttons). If you then go to the browser and open google maps, you should see the trust prompt again18:33
plarsjdstrand: oh, I actually just managed to reproduce this at home!18:34
davmor2tvoss: I see the http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-192152.png every time I open anything that needs location as before.  http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-08-05-192837.png  I only saw this once opening here maps from the store18:35
tvossdavmor2, so the first one comes from the webengine, and thus is the same for webapps and the browser18:35
tvossdavmor2, the second is issued by the location service18:36
ToyKeeperjibel: Trying silo 006 now...18:36
davmor2tvoss: the first is the one I see on every app and browser the second I've only seen once18:36
plarsjdstrand: http://paste.ubuntu.com/7963444/18:36
jibelToyKeeper, thank you18:36
jibelWellark, ^18:36
tvossdavmor2, let me quickly retry here18:37
davmor2ToyKeeper: thanks, I'm looking at 7 currently18:37
tvossdavmor2, could you make sure that your local nokia here app isn't running unconfined?18:37
davmor2tvoss: sure how?18:38
WellarkToyKeeper: please, ping if you encounter any problems18:41
ToyKeeperWellark: So far it looks great...  appears to fix the network indicator issues completely.18:41
WellarkToyKeeper: it should :)18:41
WellarkToyKeeper: there was an unfortunate non-discovered bug in indicator-network which just happened to surface it self after the last ofono landing18:42
Wellarkwe are now updating the test plans to make sure this kind of stuff does not happen in the future18:42
WellarkSaviq: did you land that dash-as-app silo?18:43
sil2100o/18:43
Wellarkonce silo6 is landed we should try to land silo 118:43
sil2100robru, ogra_: so, what's the status? Did you fix everything magically while I was away?18:43
sil2100robru, ogra_: I don't accept 'no' as an answer18:43
robrusil2100, oh yep, totally, next image will be 100% green18:43
davmor2hey sil2100 is that you saying hello or goodbye these waves all look the same to me ;)18:43
ogra_sil2100, yup, even retroactiverly ... we decided t declare 170 as not broken :P18:44
robruogra_, yeah, we promoted that one, didn't we?18:44
sil2100ogra_: oh, 170 was not b0rken? :O18:44
ogra_robru, indeed18:44
jdstrandplars: which app failed?18:44
* sil2100 smells lies18:44
sil2100;)18:44
ogra_haha18:44
Wellarksil2100, robru, ogra_: silo 1 also fixes the RootState::updateNetworkingIcon() crash in indicator-network that has been bugging us during smoke testing18:45
sil2100Wellark: \o/18:45
tvossdavmor2, so working flawlessly here18:45
sil2100davmor2: hah ;)18:45
ogra_sil2100, well, nothing new came up in the meeting ... we have to wait for apparmor and the indicator fix .... and then judge the qt4 dropping18:45
tvossdavmor2, should we jump on a hangout real quick and I show you what I'm doing?18:45
robruWellark, right but it needs to be rebuilt after the other conflicting silo lands18:45
plarsjdstrand: I was running clock_app and camera_app tests only after a fresh install18:45
ogra_the above looks good at least :)18:45
ogra_one down18:45
plarsjdstrand: they both failed18:45
Wellarkrobru: true.18:46
davmor2tvoss: sure give me 5 minutes18:46
tvossdavmor2, ack18:46
sil2100robru: so, anyway, we seem to be 'almost ready' for RTM in CI-Train, I'll just make a few more tests but it's good in overall18:46
robrusil2100, how is it looking? what changes will I need to make in the dashboard / queuebot?18:47
ogra_sil2100, so unless apparmor magically fixes itself and qt4 dropping has no side effects at all it smells like traincon-018:47
sil2100ogra_: ;/ but did you guys hear any updates on this apparmor situation? Is there at least any lead on what can be the cause?18:47
ogra_no, but plars and jdstrand are actively working on it18:48
ogra_(see backlog)18:48
jdstrandplars: you ran aa-clickhook -f --include=...? and your check-click-hook script returned 0?18:48
sil2100robru: mostly only cosmetic changes, there will be one additional column needed but in overall most things stay the same18:49
jdstrandplars: basically, what I am seeing here is that the cache files have a newer timestamp by 44.5 years than the policy files18:49
sil2100robru: there is some risk involved that when I remove the bazillion workarounds that I had to implement to test this on dogfood it will stop working, but we'll deal with it fast ;)18:50
robrusil2100, k, when you get a chance can you email me some of the details? I need to know things like a) where will the json files live, b) what's the PPA link, c) jenkins job links, etc, that way I can hook up all the frontend bits18:50
jdstrandactually, I think I need one more debugging item18:51
sil2100robru: sure18:51
ToyKeeperWellark: The only odd bit I see is that, on one device, the signal bar icon stays visible in flight mode, and on another device that disappears in flight mode.18:51
ogra_ToyKeeper, did you wait long enough ? the UI updates for that are often really slow18:52
WellarkToyKeeper: the panel icons will get a lot of love in silo 118:52
Wellarkhopefully I get it landed today18:53
ToyKeeperogra_: Yes, on one it was almost immediate; the other still hasn't hidden the icon after ~5 minutes.18:53
Wellarksilo 6 just fixes the crash and all of the problems that come with it18:53
jdstrandplars: I'm really uncomfortable with these timestamps. why is the time so off?18:53
ToyKeeperYeah, silo 6 looks awesome.18:53
ogra_wow, 5 mins is surely not normal18:53
plarsjdstrand: no idea, that's just how it came up18:54
WellarkToyKeeper: just wait when you see silo 6 on a dual sim device ;)18:54
ogra_i have seen the "dripping coffe filter icon" show up for ~1min befor the mobile bars went away18:54
ogra_but never 5min18:54
ToyKeeperWellark: Hmm, will try moving my other sim over to take a look.18:54
Wellarkjust need to land silo 6 first18:54
Wellarkotherwise silo 1 keeps crashing just the same18:55
WellarkToyKeeper: teaser http://imgur.com/XK0fEWt18:55
ToyKeeperI got a little distracted by a regression in 173...  looks like the task switcher no longer handles the only-one-app-running case correctly (again).  It doesn't 3D-ify things, so it looks a little confusing.18:55
jdstrandplars: did you comment on if aa-clickhook --include=... was run successfully and if your check passed?18:55
plarsjdstrand: seems like maybe ntpdateis running at some point after boot18:55
plarsjdstrand: yes, the checks passed fine18:55
plarsjdstrand: but what I'm wondering is if that ran before the ntpdate ran and corrected the time18:56
plarsjdstrand: so what if we came up after install with a *really* old time on the device18:56
jdstrandplars: if you ran the test again now, does it still fail?18:56
plarsjdstrand: I don't know, probably hit or miss like all the others. I still have the device in the state where the tests left it though in case we need to get anything else off it18:57
plarsjdstrand: so it seems like sometimes right after install, the phone has a datestamp of Jan 12, 197018:58
jdstrandplars: right. I have a feeling that is related, since we do all kinds of timestamp checks when loading cache files18:58
nik90sil2100: we got a bug in image #173 due to the latest ui-toolkit, bug 135304818:58
ubot5bug 1353048 in Ubuntu UI Toolkit "Header icon colors are white and barely visible in the Unity8 Dash" [Undecided,New] https://launchpad.net/bugs/135304818:58
WellarkToyKeeper: please leave a comment to the MP and state which device you used for testing and what is the test result18:58
WellarkToyKeeper: https://code.launchpad.net/~unity-api-team/indicator-network/lp1352744/+merge/22966518:58
ToyKeeperWellark: Looks nice, but the SIM card names don't seem to be used in apps other than the settings app.19:02
WellarkToyKeeper: that's being worked on19:02
sil2100nik90: yes, we noticed it earlier, bzoltan1 is aware of it... let me read the backlog19:03
WellarkToyKeeper: actually indicator-network won't show up the sim names on devices with silo6 yet19:03
Wellarkthat's the next one19:03
Wellarkwe just need to get the items in now19:03
Wellarkand then add labels throughout the system19:03
nik90sil2100: ok19:04
jdstrandplars: there seems to be data missing from the syslog19:05
jdstrandplars: ie, I can't see that the clock apparmor profile is loaded into the kernel19:06
jdstrandplars: can you adjust the infrastructure to run this as early as you can: sysctl -w kernel.printk_ratelimit=019:07
jdstrandplars: that will disable kernel rate limiting19:07
jdstrandplars: that is something we will permanently want in the test infrastructure19:08
jdstrandsil2100, ogra_: can you point me at the last known good test run?19:08
plarsjdstrand: sure, but couldn't that have a negative effect if we get something spamming?19:09
plarsjdstrand: and which syslog are you looking at? I don't think I sent you one from this run19:09
ogra_jdstrand, 162 or 165, not sure without looking deeper19:10
jdstrandplars: I was looking at 656, which was the failed one from ealier19:12
plarsjdstrand: from one of the recent successful runs, I see a bunch of failed ntpdate calls (also seen here) and then: Aug  5 15:00:57 ubuntu-phablet ntpdate[2836]: step time server 91.189.89.199 offset 8.587277 sec19:13
jdstrandplars: it might have a negative side-effect if something spams, but it is known that we can lose valuable information without it. I think it is an appropriate default so disable rate limiting in a testing environment so we don't lose anything19:13
plarswhich is way more reasonable19:13
plarsso something is resetting the clock inconsistently19:14
jdstrandplars: ah yes, that was what I was wondering- if successful ones had good clocks and unsuccessful ones had bad19:15
plarsjdstrand: yep19:15
plarsjdstrand: what's really funny, is that during these two tests I tried locally, they both failed, and I have two entries for: Aug  5 18:35:08 ubuntu-phablet ntpdate[2716]: step time server 91.189.89.199 offset 1406238958.132842 sec19:15
plarsjdstrand: so either the hwclock never got set and it lost it across the reboot before the next test, or something reset it again19:16
jdstrandplars: I see /etc/init/hwclock-save.conf19:18
tvosssil2100, still around?19:18
sil2100tvoss: yeah, more or less19:18
jdstrandplars: it should run in runlevel 0 and 6, so a reboot shoud trigger it, if the machine goes down cleanly19:19
plarsroot@ubuntu-phablet:~# hwclock19:19
plarsMon 12 Jan 1970 09:22:57 PM UTC  -1.029365 seconds19:19
tvosssil2100, I have to remerge qtmir and qtmir-gles in silo1019:19
tvosscould use some help with the twins stuff19:19
plarsjdstrand: I think perhaps the reboot bit is calling adb reboot, rather than trying to rely on the OS to reboot19:20
sil2100tvoss: ok, let me take a look at that silo19:20
jdstrandplars: I can keep digging to autoritatively determine the series of events that are causing the problem. I feel like we are going to want to have the clock fixed regardless and doing that will resolve this19:20
davmor2sil2100: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1352930  jibel did an updated version of the gps indicator19:20
ubot5Launchpad bug 1352930 in indicator-location (Ubuntu) "GPS checkbox doesn't stay checked" [High,Confirmed]19:20
tvosssil2100, just pushed the updated gles branch19:21
jdstrandplars: oh, that would make some sense. you could prior to adb reboot do 'start hwclock-save' and see if that helps19:21
davmor2sil2100: that's incase it isn't the same issues as it was before19:21
plarsjdstrand: indeed, I think the clock issues have to be the root cause, but why on earth would we need to jump through all these extra hoops for CI? This is something that it seems could potentially hit others19:21
plarswhat made us get into this situation where the date is coming up bad19:21
sil2100tvoss: ok, does the silo need reconfiguration? Or did you only push to already existing branches?19:21
tvosssil2100, only to already existing branches19:21
sil2100davmor2: oh, let me add that to the list, but not a blocker right?19:22
tvosssil2100, so we should just need a rebuild for qtmir and qtmir-gles19:22
sil2100tvoss: ok, doing then :)19:22
jdstrandplars: yeah, I don't have answers to those questions, except to say that people don't usually adb reboot their device, and if they do, it isn't often, so if this is an intermittent failure that doesn't happen for regular people, maybe they just reboot?19:23
davmor2sil2100: no just a known issue, that should be monitored closely as currently it might be knocking gps off until tvoss's location service lands fingers crossed for latter tonight or tomorrow am19:23
jdstrands/happen/happen often/19:23
plarsjdstrand: no, more likely they don't reboot it at all unless they hard-power it off19:23
plarsogra_: any ideas on the clock?^19:24
jdstrandright, I would think that would still not save the hwclock19:24
jdstrandbut maybe we run some stuff on power button press19:24
plarsjdstrand: I'm not opposed to working around this if we really have to, but I think we should understand how we got here and ensure we're not just hiding the bug from ourselves in the future.19:24
jdstrandplars: yes, I agree19:25
jdstrandthat is a good point19:25
plarswe've been asked to do things like that before, and resisted, and learned that it was a real bug after all :)19:25
jdstrandsure, that makes sense19:27
plarsjdstrand: but I wouldn't think it's apparmor's fault either here. But it makes me wonder if my thinking is backwards.... if we push those aa-clickhook changes when the date is set to 1970, and then the date gets updated, wouldn't apparmor have even more urgency to update what it has cached?19:27
jdstrandplars: well, that is the thing-- I don't have enough data to say what is exactly happening19:31
jdstrandplars: I need the sysctl in place to do that19:31
jdstrandI can say that the cache files are newer than the policy files by 44 years19:31
Wellarkcan we now land silo 6 as ToyKeeper has tested on relevant devices?19:31
WellarkI will try to get tedg to set the silo as "Testing done"19:32
ToyKeeperWellark: That happened about 23 minutes ago.19:32
plarsjdstrand: where can I find the cache files? I still have that system booted at my desk right now19:32
WellarkToyKeeper: I didn't get the memo..19:32
Wellark;)19:32
Wellarkok. great19:32
Wellarkthanks!19:32
jdstrandplars: /var/cache/apparmor19:32
ToyKeeperWellark: Do you get notices from queuebot?19:33
jdstrandplars: I think I see the issue19:33
jdstrandelif os.lstat(hook_full).st_mtime > os.stat(profile).st_mtime:19:33
jdstrand# If the profile exists, but the hook symlink is newer, we need to19:33
jdstrand# regenerate it. Click may update the symlink from time to time, so19:33
jdstrand# we need to handle this (LP: #1291549)19:33
jdstrand...19:33
ubot5Launchpad bug 1291549 in click-apparmor (Ubuntu) "Apps don't start if click packages update without version number bump" [High,Fix released] https://launchpad.net/bugs/129154919:33
ToyKeeperWellark: The last silo 6 notice I saw was: -queuebot/#ubuntu-ci-eng- Silos: landing-006 (pete-woods, Wellark) Migration: One package at least is not available at the destination. indicator-network (0.5.1+14.10.20140805-0ubuntu1) is in the proposed pocket.  (indicator-network)19:33
jdstrandmeh bug bot19:33
jdstrandplars: notice, that check is '>'19:33
nik90hey guys what's up with all the clock app tests failing in the dashboard?19:33
jdstrandplars: the timestamps are all the same19:33
nik90I haven't made any change to the AP tests for sometime now19:34
jdstrand(1970)19:34
jdstrandwell, but the profile has the code, so that isn't it19:34
Wellarkrobru: plz help to debug silo 619:34
jdstrandyeah, I need more data19:34
robruWellark, what's wrong with silo 6?19:34
Wellarkrobru: the status is weird19:35
WellarkIn silo landing-006. Migration: One package at least is not available at the destination. indicator-network (0.5.1+14.10.20140805-0ubuntu1) is in the proposed pocket.19:35
jdstrandplars: I need to know when the clock app profile was loaded so I can compare it to the timestamps in the paste you gave me19:35
robruWellark, yes... that is completely unremarkable.19:35
tvossdavmor2, found the issue19:35
davmor2tvoss: \o/19:36
tvosssil2100, so once the packages are built, we have to adjust the changelog entry in the gles-branch, correct?19:37
Wellarkrobru: ok. silo 1 needs a rebuild.19:37
Wellarkrobru: oh, wait.. I need to update the unity8 dependency version19:37
robruWellark, don't rebuild silo 1 until after 6 is merged.19:37
* Wellark wonders what is the latest version of unity819:38
Wellarkqueuebot: where unity819:38
Wellark;(19:38
jdstrandplars: ok, I think I have it. we precompile apparmor policy for clicks shipped on the device. those have a timestamp of today. with aa-clickhook is run, the policy is regenerated, but the clock is still at 1970. when the parser goes to load the policy, it sees the cache files from 2014 and the policy with a timestamp of 1970 and so it skips them19:39
plarsjdstrand: ah, that makes some sense19:40
plarsjdstrand: so we are actually pushing what it believes to be an older policy19:40
plarsjdstrand: that sounds plausible19:40
jdstrandok, I've definitely convinced myself that we need to fix the clock :)19:40
plars:)19:40
plarsogra_, sil2100: any ideas how we are timetraveling?19:40
plarsogra_, sil2100: it looks like we've created a paradox in the universe, and apparmor is trying to prevent a temporal rift from killing us all. Thanks to jdstrand and his excellent code that prevents the universe from being torn asunder19:41
jdstrandheh19:42
sil2100:O19:43
kgunnrobru: hey there, is there a way you could move the mir stuff to a new silo, we've been dorking around with symbol stuff...we're thinking 2 of the rdeps we're trying to build are getting hung up on some residue19:43
sil2100wow19:43
plarswith all the systemd related problems, I blame that. And it got update in 164 right before we started hitting this :)19:44
robrukgunn, you mean silo 9? yeah I can do that19:44
sil2100plars, jdstrand: ok guys, this sounds like a really crazy bug19:44
plarssil2100: nah, I just made it sound much more serious in hopes someone would fix it :)19:45
jdstrandits actually probably a simple bug, it was just hard to triage19:45
jdstrandwell, triage to the point were someone can really now dig in19:45
robrucjwatson, infinity, stgraber: anybody around to ack a new binary package? https://ci-train.ubuntu.com/job/landing-014-2-publish/lastSuccessfulBuild/artifact/packaging_changes_address-book-service_0.1.1+14.10.20140804-0ubuntu1.diff19:45
sil2100Indeed, as no one would suspect the timing of the clickhook to being a bit unfortunate19:45
plarsbut apparmor is doing the right thing - it's not updating to the "new" profile from 197019:46
SaviqWellark, fwiw, your unity8 branch in silo 1 isn't reviewed yet19:46
jdstrandit would've been ok if we didn't precompile policy19:46
SaviqWellark, so it will only land tomorrow at the earliest19:46
jdstrandfor some definition of 'ok'19:46
jdstrandthe clock would still be off and who knows what other issues that might cause19:46
jdstrandsil2100: yeah, as plars said, it isn't click-apparmor or apparmor's fault. we need to have a clock that is not 44 years off :P19:47
jdstrandfor today, we needed it to be less than a few hours off19:48
davmor2sil2100: did you answer tvoss?19:48
jdstrand(since each new image recompiles the cache files for pre-caching)19:48
jdstrands/new image/new image generation/19:48
WellarkSaviq: i thought dednick reviewed it already, but OK.19:49
SaviqWellark, I asked him today and he said he didn't test it yet, will make sure this happens tomorrow19:49
robrukgunn, you're in 7 now19:50
sil2100tvoss: ah, yes, sorry, missed that - we need to make sure the versions are the same19:51
davmor2plars: that or jdstrand is actually the Doctor19:51
plarsdavmor2: no, then the clock would be off by the *other* direction19:51
plarswhich would actually be ok for this19:52
davmor2plars: no he can go anywhere in time, it's a big squirmy wormy, timey whimy thing it's hard to explain ;)19:53
tvosssil2100, do we have a version, yet?19:55
sil2100tvoss: yeah, let me get it (still building though)19:55
sil2100tvoss: 0.4.0+14.10.20140805.1-0ubuntu119:56
tvosssil2100, pushed19:59
sil2100tvoss: excellent19:59
plarsjdstrand, sil2100: interesting, here's a line from syslog during boot in a good run. vs a bad run respectively:20:04
plarsJul 31 23:50:51 ubuntu-phablet kernel: [    2.315092] rtc-pm8xxx rtc-pm8xxx: setting system clock to 2014-07-31 23:50:47 UTC (1406850647)20:04
plars[    2.191240] rtc-pm8xxx rtc-pm8xxx: setting system clock to 1970-01-12 20:38:34 UTC (1024714)20:04
plarsnm, I guess that's just confirming what we already suspected, that the hwclock is wrong on boot in some cases20:05
Saviqrobru, hey, we're down to 1 utopic&&amd64 vm on s-jenkins, do you know if anything can be done about that?20:09
Saviqthis one seems to be stuck launching http://s-jenkins.ubuntu-ci:8080/computer/ps-utopic-server-amd64-1/? :|20:10
Saviqcamako, FYI, unity-mir is deprecated, probably doesn't make sense to update it any more20:11
Saviqwe should be cleaning it up from distro20:11
robruSaviq, nope, try Ursinha for that one20:16
Ursinhamoi?20:16
Saviqoui20:16
Ursinha:)20:16
robruUrsinha, vanguard ;-)20:16
Saviq we're down to 1 utopic&&amd64 vm on s-jenkins, do you know if anything can be done about that?20:16
Saviq this one seems to be stuck launching http://s-jenkins.ubuntu-ci:8080/computer/ps-utopic-server-amd64-1/? :|20:16
SaviqUrsinha, ↑20:16
Ursinhaah, I'm not vanguard anymore, but I can have a look :)20:16
UrsinhaSaviq: let me see20:17
SaviqUrsinha, /topic says you are ;)20:17
Saviqrobru, ah, sorry, misread the "Train" in /topic20:17
UrsinhaSaviq: yeah, I forgot changing that :) it's my fault, I'll reply the request :P20:17
robruSaviq, no worries. I'm vanguard sometimes, but I don't actually know about this request ;-)20:18
robruWellark, ok, merged 6 and rebuilding 1.20:19
Wellarkrobru: thanks!20:22
robruWellark, you're welcome!20:23
rsalvetirobru: mind reconfiguring silo 3?20:24
robrursalveti, can do20:25
robrursalveti, well there's a build job running by jhodapp, is that on purpose?20:25
jhodappyes20:25
jhodappif it needs a reconfigure you can kill the build20:26
rsalvetijhodapp: robru: sorry, we can reconfigure after the build20:28
rsalvetino worries20:28
rsalvetijust added 2 extra src packages to the silo20:29
jhodappok cool20:29
robrursalveti, ah ok, yeah if there's no changes toe xisting source packages, lets let those build then reconfigure after. just ping me when the build is done20:29
rsalvetisure, thanks20:29
tedgrobru, Can I get a silo for Line 30 please?20:33
robrutedg, ok you gto #620:34
tedgrobru, Great, thanks!20:34
robrutedg, you're welcome!20:34
jhodapprobru, we need a reconfigure on silo 3 after all20:45
robruah, manual upload. ok20:46
rsalvetigreat, just missing android now20:48
rsalvetitesting on every device now20:48
rsalvetiogra_mobile: on krillin? :-)20:50
rsalvetijhodapp: for some reason my videos didn't pick my recorded video20:54
rsalvetithe scopes20:54
jhodapprsalveti, yeah I think it might be the scopes...because gallery app pics up the video20:55
jhodapprsalveti, but not entirely sure...if you close the camera-app the scopes pick up the new video20:55
davmor2rsalveti: check the permissions and then on the video scope do a search20:55
nik90rsalveti, jhodapp: I saw my recorded video in the video scope. however on clicking it to play open the mediaplayer app, but the apps shows an error dialog that no video was selected to play it20:56
rsalvetiyeah, worked fine from file manager20:56
davmor2it might just be that the scope needs to be triggered to search again20:56
jhodappnik90, I've seen that too20:56
rsalvetipermission is fine20:56
rsalvetilol, yeah20:56
rsalvetiit works as soon I hit search20:56
jhodappscope bug then I guess20:56
davmor2rsalveti, jhodapp: Media scanner scope bug it does a search initially on boot I don't know when it is triggered to look for videos after that20:57
rsalvetiright20:57
jhodappdavmor2, it should be triggered to monitor the directory for filesystem event changes20:58
davmor2jhodapp: but then when does the scope know to update, does media scanner say I have a new file show it?20:59
jhodappdavmor2, that I don't know how it works20:59
jhodappdavmor2, there should be some trigger because when you copy videos over with MTP, the scopes update21:00
davmor2jhodapp: but only when there are no videos on the device I think I could be wrong though21:00
jhodappdavmor2, I'm pretty sure all of the time21:00
davmor2jhodapp: ah fair enough21:01
jhodappdavmor2, unless that's changed recently21:01
jhodappdavmor2, only one way to find out :)21:01
davmor2anyway way passed my EOD night all21:01
jhodapplater davmor221:01
rsalvetiwe should probably kick an image soon21:03
rsalvetiquite many changes21:03
rsalvetirobru: is that planned?21:03
ogra_mobilersalveti, shhhh !21:04
rsalvetiogra_mobile: what, talking about dragon ball21:05
ogra_mobilelol21:05
rsalvetirobru: ogra_mobile: will trigger a new build in ~23 min if that is fine21:07
ogra_mobilesure, go ahead21:10
rsalvetigreat21:11
jhodapprsalveti, building qtubuntu-camera for silo 321:21
veebersrobru, thomi: when you have a moment I have a query re: changes in archive vs what's in trunk and release21:24
tvossdavmor2, in case you are *still* around: silo 10 is good to go21:28
slangaseksergiusens: sorry, I was just EOD here at the sprint when you pinged me - does http://people.canonical.com/~platform/citrain_dashboard/#?q=sergiusens still need a look?21:29
Saviqrobru, can we have a reconf on silo 7 please? added qtmir-gles there21:31
robruveebers, Saviq: sorry in meeting, one sec21:31
Saviqnw21:31
veebersrobru: nw, I knew that :-)21:31
veebersrobru: I'm not sure what to do with this changeset as it seems to be applied against the lp:autopilot/1.5 release branch but not lp:trunk (http://launchpadlibrarian.net/181532211/autopilot_1.5.0%2B14.10.20140716-0ubuntu1_1.5.0%2B14.10.20140716-0ubuntu2.diff.gz)21:32
robruslangasek, you here?? ;-) ^^21:32
veebersrobru: so, I can merge it into 1.5 ok, but then it won't exist in the trunk codebase, will that cause an issue?21:32
slangasekveebers: merge it both places, please :)21:33
slangasekI can raise an MP if needed21:33
robruveebers, well, it's not really applied against 'trunk' or 'the 1.5 branch', it's applied against what's in distro.21:33
robruveebers, yeah, so syncing it everywhere is ideal21:34
UrsinhaSaviq: other two utopic amd64 nodes might be corrupted, we're looking into it21:34
SaviqUrsinha, ok thanks21:34
veebersrobru: ack, that makes sense thanks. I hope I can do it it in a way that doesn't cause conflicts :-)21:34
slangasekveebers: it would be awfully lovely from my POV if there were not two branches to merge to in the first place21:34
Saviqslangasek, as you're around, can you tell me what the process is for dropping a package from archives (unity-mir)?21:34
slangasekveebers: and certainly I do not expect you to have any difficulty with merge conflicts21:34
slangasekSaviq: source package?21:34
robruSaviq, reconfiguring 721:35
Saviqslangasek, unity-mir, yup21:35
Saviqrobru, yes please21:35
Saviqslangasek, got replaced by qtmir already21:35
robrursalveti, oops, was in meeting. image build fine by me21:35
robrursalveti, want me to do it?21:35
rsalvetirobru: great, that would be awesome21:35
robruSaviq, i meant, it's happening ;-)21:35
robrursalveti, ok. right now?21:35
slangasekSaviq: file a bug against the package; subscribe ~ubuntu-archiev21:36
rsalvetirobru: yeah21:36
slangasekSaviq: file a bug against the package; subscribe ~ubuntu-archive21:36
robrursalveti, ok, on it21:36
veebersslangasek: ack21:36
Saviqrobru, ah, 7 looked like ? ;)21:36
Saviqslangasek, will do, thanks21:37
robruSaviq, hehe21:37
robruslangasek, oh, can you ack a new binary package? I know you are just relaxing with tons of free time right now ;-) https://ci-train.ubuntu.com/job/landing-014-2-publish/62/artifact/packaging_changes_address-book-service_0.1.1+14.10.20140804-0ubuntu1.diff21:38
slangasekrobru: currently reviewing ciborium21:38
slangasekloving the naming schemes, btw :)21:38
rsalvetirobru: thanks21:39
robrursalveti, you're welcome21:40
slangaseksergiusens: oh, but I am reminded that new source packages don't need to be pre-reviewed21:40
slangaseksergiusens: so please feel free to publish this in the normal way and I'll pick it up from there21:40
cjwatsonI thought somebody already had21:41
sergiusensslangasek: it's been published by Mirv; just sitting in the queue now21:41
slangaseksergiusens: ok, so not pre-review at all21:41
sergiusensI'm just waiting for that to happen eventually21:41
cjwatsonright, it's simply review :)21:41
sergiusenswas just asking about preNew since there isn't much info around that21:42
sergiusensthat I found at least21:42
slangaseksergiusens: you set DEB_HOST_ARCH but don't use it; and I think you could quite reasonably leave this in /usr/bin instead of moving it into a private dir21:44
slangasekand accepted21:44
imgbot=== trainguard: IMAGE 174 building (started: 20140805 21:45) ===21:45
sergiusensslangasek: I can change that; was just applying the trend I was seeing recently in some packages21:45
veebersslangasek: to clarify, how come these changes (packaging changes to autopilot) weren't done through an MP + silo etc. ?21:45
* sergiusens takes note of adjustments21:45
slangaseksergiusens: there's no reason you *need* to hide this in /usr/lib, and doing so seems to make debian/rules a lot more complicated than it should be21:45
sergiusensthat is true21:46
slangasekom26er, robru: address-book-service - what's the reason of adding the test as a new binary package?21:48
robruslangasek, dunno. renato___ boiko ^^ ?21:49
om26erslangasek, we install a python fixture with that, that can be used by external applications like messaging-app dialer and address-book for testing21:50
om26erwell the new fixture is part of the address-book-service testcode now.21:51
slangasekhmm, I have no idea what a "fixture" is21:51
slangasekbut at least "it's used by other packages" explains21:52
om26erslangasek, its a reusable helper class, that in this case, helps add fake contact in the service for testing purpose.21:53
slangasekrobru, om26er: ok, approved21:55
davmor3tvoss, sil2100, robru: silo10 is good to go be nice to get that in for the morning image21:57
pmcgowanslangasek, where do I find the crash reports for say system settings?21:57
slangasekpmcgowan: https://errors.ubuntu.com/?package=ubuntu-system-settings&period=day21:58
pmcgowanslangasek, thank you21:58
robrudavmor8, ok, can publish once it's done building21:59
davmor3robru: Thanks dude :)22:00
davmor3Right back to bed22:00
Saviqrobru, reconf on silo 1 please, added unity-scopes-shell (and a slew of unity8 MPs, basically took over thostr's silo :P)22:04
robruSaviq, ok going... did you say you merged a silo? is there another silo I can clear because of this?22:05
Saviqrobru, no, I took it over22:05
robruSaviq, oh ok22:05
Saviqthere were just 2 MPs before, more like 20 now ;)22:06
Saviqand there's plenty more when those came from...22:06
pmcgowanslangasek, once I trigger a crash it should automatically get uploaded now yes?22:08
pmcgowanah I see the magic hapen22:08
slangasekpmcgowan: this is true for a newly-installed device.  If you've been upgrading continuously, you need to manually toggle a setting in system-settings22:09
pmcgowanslangasek, ok, now any way to identify the crash I just triggered on errors page?22:10
slangasekpmcgowan: hum - in theory yes but I don't know how to extract this from the phone22:11
slangasekjibel: you had a way to get the whoopsie identifier off of a device, right?  (Even though it doesn't work reliably)22:12
ogra_mobileyou need the whoopsie id22:12
pmcgowanogra_mobile, wheres that22:13
ogra_mobileshould be in the url that opens when you click "previous error reports"22:14
ogra_mobileon the privacy settings22:14
pmcgowanogra_mobile, nothing there22:17
pmcgowanI didnt see any new reports either22:18
veebersrobru: any idea why the build job was unable to create a changelog from the unmerged revisions in the MP for the silo? (https://ci-train.ubuntu.com/job/landing-004-1-build/158/console)22:19
robruveebers, oh, yeah, that's because you merged steve's change which touched debian/changelog and then didn't actually add a new debian/changelog entry with your new changes.22:20
robruveebers, generally the best way to avoid this is to just merge those kinds of changes directly in trunk, not into the silo build22:20
robruveebers, but since we're in this situation now, you have to add a new entry in debian/changelog22:21
veebersrobru: right, so I'm just going through now cerating one based on the unmerged22:21
veebersrobru: ack, so I shouldn't have merged into lp:ap/1.5 just lp:ap. I'll keep that in mind, cheers22:21
ogra_pmcgowan, no, it is broken, but your whoopsie ID is your user ID in the URL in the browser now22:21
veebersrobru. slangasek: how come those packaging changes were pushed directly and not through a MP + silo?22:22
robruveebers, because core devs just do that sometimes? I dunno, that was the official way of doing things since long before citrain ever existed.22:22
pmcgowanogra_, that enormous guid string?22:23
ogra_yep22:23
ogra_pmcgowan, there is also a dbus way i think ... ask ev22:23
veebersrobru: hmm, ok cheers.22:24
robruveebers, so just add a new stanza at the top of debian/changelog that says 'UNRELEASED' where the other stanzas say 'utopic' and it should work.22:24
slangasekveebers: because when I asked thomi earlier same day about a silo for autopilot-qt, I was told that this was currently untestable through a silo so I should feel free to push my packaging-only changes direct22:25
evogra_, pmcgowan, slangasek: sudo gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.GetIdentifier22:25
veebersrobru: ok, do I need to increase the version number? or use dch to do so?22:25
robruveebers, yeah, sorry, earlier when you asked about this I didn't realize that you were merging 1.5 into trunk, I thought they were two diverged branches. if I'd realized, I would have just said "yeah push steve's thing to trunk only"22:25
veebersslangasek: ack, thanks makes sense :-)22:25
veebersrobru: no worries, I had a couple of people give me options on how to proceed and picked that one. It's good practice for next time :-)22:26
pmcgowanev, thanks now how do I use that to find the report on errors.u.c :22:27
pmcgowan?22:27
evpmcgowan: tack that on the end of https://errors.ubuntu.com/user/22:27
veebersrobru: can you confirm my Q about version number?22:28
* ev -> bed22:28
robruveebers, yeah you need to bump it, I'm just checking dch options for you because dch never really does what I expect it to22:28
veebersrobru: heh, sweet I think -i or -a. I'll have a go at it22:28
pmcgowanev, ok but nothing there, is there a delay after an upload?22:29
evpmcgowan: check to make sure you have a .uploaded file in /var/crash22:29
UrsinhaSaviq: your nodes should be back online22:29
robruveebers, yeah, neither -i nor -a did it, you need to make a whole new entry, not just adding a bullet point at the end of the current entry.22:29
pmcgowanev, I do indeed22:29
SaviqUrsinha, thank you plenty22:29
veebersrobru: oh *blush*22:29
evpmcgowan: quite perplexing. Does syslog give you any output from whoopsie? Could you pastebin it?22:30
veebersrobru: -i seems to do that for me (new line with *-ubuntu3 UNRELEASED etc)22:30
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | CI Train support: robru, trainguards | Vanguard (general help): cihelp | CI Train Status: #157 promoted | CI Train Dashboard: http://bit.ly/1mDv1FS | Known issues: -
pmcgowanev, anything I can grep on?22:30
evwhoopsie :)22:31
pmcgowanyeah nothin22:31
evand `sudo status whoopsie` shows it running?22:31
pmcgowanev yes22:31
robruveebers, yeah I dunno, when I try 'dch -i' here locally it just clobbers over the existing most recent entry in debian/changelog. Yeah it gives a new version, but it just clobbers the existing most recent version22:31
pmcgowanev it made an uploaded file right after I triggered the crash22:32
evpmcgowan: is there a /var/log/upstart/whoopsie.log?22:32
robruveebers, alternately you could just revert the debian/changelog changes in the 1.5 branch and then citrain can generate the changelog for you as it always does22:33
pmcgowanev, yep, looks good http://pastebin.ubuntu.com/7965105/22:33
pmcgowanand I can get the whoops id there so I could find my report with that I suppose22:33
evpmcgowan: does your /var/crash/*.crash file have a SystemIdentifier field?22:34
evoh wait, it wouldn't22:34
evhmmm22:35
pmcgowanev, nope22:35
evpmcgowan: can you PM me the output of that dbus command?22:35
veebersrobru: fyi this is what I came up with: https://code.launchpad.net/~veebers/autopilot/release-changelog/+merge/22970422:39
evpmcgowan: did you reboot since this crash occurred?22:39
pmcgowanev, no22:39
pmcgowanev, maybe I ran the gdbus thing wrong, I did adb shell which may not be root anymore22:40
pmcgowanno same22:41
evyeah, that is very strange22:42
evis it changing on subsequent runs?22:42
evthe gdbus command, that is22:42
ev(whatever you do, don't paste the system identifier in public)22:42
robruveebers, that'll work, but version number 20140805-0ubuntu1 would be better. 0ubuntu3 implies that it's a tiny patch, not a major upstream release.22:43
veebersrobru: oh ok, good catch. I just used dch :-)22:43
veebersI can change the the version number manually now22:44
robruveebers, yeah, dch, never works ;-)22:44
veebersrobru: how pedantic are we, over in NZ it's actually 20140806 :-)22:45
robruveebers, that's fine22:45
robrucrazy time travellers22:45
robru;-)22:45
veebersrobru: ^_^ Thanks again for all the help this morn22:45
robruveebers, no worries22:46
veebersrobru: I've updated the version number as per your comment22:49
robruveebers, thanks22:50
slangasekpsivaa: are you able to log in to the system exhibiting http://ci.ubuntu.com/smokeng/utopic/touch/mako/172:20140805.1:20140728.1/9490/default/1486871/ ? Would like to know if /var/lib/apport/autoreport exists22:56
plarsslangasek: since we use phablet-config to skip the wizard, I had to make our scripts create /var/lib/apport/autoreport. You can see where the command ran at http://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/658/consoleFull23:15
plarsslangasek: that phone has run other jobs since then, but I'm certain the autoreport file is there23:15
slangasekplars: the file is not created by the wizard; it's present in any fresh install23:19
imgbot=== trainguard: IMAGE 174 DONE (finished: 20140805 23:20) ===23:20
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/174.changes ===23:20
plarsslangasek: oh is that new? not too long ago I discovered it isn't created if you skip the wizard23:20
slangasekplars: creating the file from your scripts would explicitly undermine the purpose of this test, which is to ensure that autosubmission works without modification :)23:20
plarsslangasek: apparently the wizard is supposed to ask if you want the reports sent23:20
slangasekplars: the wizard doesn't ask - it's not created even if you do go through the wizard23:21
slangasekthe wizard lets you know it will be autosubmitted (which was a lie until a couple of days ago)23:21
plarsslangasek: from talking to bdmurray, my understanding was that if that file doesn't exist, we don't get submissions.  We can have it *not* create that file if you prefer though23:21
slangasekplars: yes, your scripts should not be modifying the environment to create that file23:22
slangasekit was a critical bug that the file wasn't being created23:22
plarsslangasek: well, at one point we were told they should be23:22
plarsso I'll change it back then23:22
slangasekok - at this point, you definitely shouldnt23:22
plarsslangasek: Just pushed the change, but I missed the cut for 174 to start testing by 1 or 2 minutes23:26
slangasekok23:26
plarsso the results for 174 will have still created it23:26
slangasekplars: at any rate, you creating the file manually should have let the test *pass* even if the install was broken, so I still don't know what's going on to cause the failure23:27
slangasekI thought I was all clever in instrumenting the different phases of the process with debugging output, but I still manage to get it into a state with confusing failures23:27
plarsslangasek: well, we are getting some strangeness that jdstrand and I were investigating earlier. For some reason the phones sometimes come up thinking it's January 12, 1970, and it takes a bit for ntpdate to sync up23:29
plarsslangasek: possible that's confusing whoopsie too? It's doing bad things when we try to setup the apparmor profiles23:29
slangasekI don't see how that would confuse whoopsie_upload_all, but I don't know23:31
robrukgunn, you got silo 2 but just note it conflicts with 723:34

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