/srv/irclogs.ubuntu.com/2014/09/11/#ubuntu-ci-eng.txt

imgbot=== trainguards: IMAGE 236 building (started: 20140911 02:05) ===02:04
=== fginther changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings.
AlbertA2cihelp: were are hitting an issue with the mir autolander02:44
AlbertA2cihelp: /runscript: line 10: mk-build-deps: command not found02:44
AlbertA2cihelp: https://jenkins.qa.ubuntu.com/job/mir-clang-utopic-amd64-build/1717/console02:45
fgintherAlbertA2, looking02:45
AlbertA2fginther: ack02:45
fgintherAlbertA2, I've made a change to fix this and am retesting. I enabled some new build slaves today and it appears they aren't properly setup for these jobs yet. I've reconfigured them to run only on the old hardware until I can fix the missing dependencies02:49
fgintherAlbertA2, This applies to the mir-android-utopic-i386-build job as well02:50
AlbertA2fginther: ok thanks!02:50
fgintherAlbertA2, sorry for the inconvenience, I'll add these jobs to my test set for the next round of slave updates02:50
AlbertA2fginther: np02:51
imgbot=== trainguards: RTM IMAGE 30 building (started: 20140911 03:05) ===03:04
Mirvmornings03:45
imgbot=== trainguards: IMAGE 236 DONE (finished: 20140911 03:50) ===03:49
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/236.changes ===03:49
bzoltanToyKeeper: I git might nightly tests with the RTM image -> http://people.canonical.com/~bzoltan/ap-2014_09_10-19_29_44/ Check the ap-2014_09_10-19_29_44.MAIN-LOGS.tests for the summary. I think it has the same failures as th stock image without the release candidat UITK.03:50
bzoltanToyKeeper:  it was on RTM image #3203:51
bzoltanMirv:  I have two RTM silos waiting for QA signature... the first one I tested on #22 and the second on #3204:07
Mirvbzoltan: ok. it'd be useful to get the utopic release published first.04:10
bzoltanMirv:  that one is a clear case after I have now top approved the MRs04:11
Mirvbzoltan: ok, thanks. I'll try publishing it then.04:11
Mirvnot that QA would look at the second rtm landing anyhow before the first one is done, of course..04:12
bzoltanMirv:  thank you. I will bug the QA folks to take the RTM UITK in queue.04:12
bzoltanMirv:  I do not see any point of releasing the first one to be honest. Or of course it is OK to releas it and in 5 seconds later release the second one. The first one can even cause killer regression because the second will fix it :D One think would be total waste of that ... re-validatinng both04:13
bzoltanMirv:  I think the UITK is the only project what does this level of pre-release testing -> http://people.canonical.com/~bzoltan/ap-2014_09_10-19_29_44/04:14
Mirvbzoltan: that's indeed probable..04:35
Mirvcyphermox_: just so you know, your upstart publishing did not publish anything, another "new normal" for CI Train. you need to watch that there's that rsync generated, otherwise you'll need to go to build watch_only and possibly reconfigure dance.04:52
Mirvrobru: ^ so that's another example of how rtm landings don't land.04:53
MirvI know to watch for it, but not necessarily all people doing publishing04:54
ToyKeeperbzoltan: Do you have the camera app tests enabled?  Everything looked good except for a new failure on the camera app.05:24
bzoltanToyKeeper:  the camera app tests have not even started05:28
ToyKeeperbzoltan: Okay, just wondering because it looked like it didn't run.05:30
bzoltanToyKeeper: I hav attempted to run the camera app tests 50+ times this week. It hangs or does not even start. So I removed it from the test lists. It should not block the UITK05:30
Mirvlooks like ToyKeeper has conquered the mountain of validating UITK release05:31
bzoltanToyKeeper: http://people.canonical.com/~bzoltan/ap-2014_09_10-19_29_44/ap-2014_09_10-19_29_44-camera_app-1.tests as you see05:31
ToyKeeperbzoltan: I haven't had issues getting the camera tests to run, but it was 1/12 failed pre-silo and 2/12 post-silo.05:31
Mirvand mtp too, and I get to do the so-called "train dance" again it seems05:32
bzoltanToyKeeper: Mirv: But I am still on the opinion that the QA validation should not repeat what I do .05:32
ToyKeeperI then tested that part of the camera's functions manually and it seems fine so I passed it anyway.05:32
Mirvit's a secretive ritual where packages get published with a ceremony of jobs05:32
Mirvwhich vary from case to case05:32
ToyKeeperbzoltan: The reason UITK was delayed was because the test results didn't match, so I investigated why.  I found out that what you were running was very different than the test plan given to QA, which makes it an automatic fail.  But instead of failing it, I tried to resolve the issue.  Still working on that, actually.05:33
bzoltanToyKeeper:  keep in mind that I am testing 20+ apps ... 800+ test cases. Flakiness and instability of apps causes surprises all the time. If any random app's random test would bock the UITK then we stil would be on the 0.000011 version :)05:34
bzoltanToyKeeper:  No, I have run exactly the test plan.05:35
ToyKeeperI found some pretty significant differences, big enough to invalidate the results.  Like installing bits from the wrong package feed.05:35
bzoltanToyKeeper:  the test plan was to run the AP tests for a list of apps ... the test plan does not define for any test plan how the tests are run05:36
bzoltanToyKeeper: what bits and what package feed?05:36
Mirvplease ignore the train comments. mtp was ~easy, the uitk needs bigger weapons05:37
ToyKeeperThe click setup was pulling files from the non-rtm feed, then testing them on a rtm image, producing meaningless results.05:37
bzoltanMirv: :) OK05:37
bzoltanToyKeeper: that is a phablet-click-test-setup bug ...05:38
bzoltanToyKeeper:  this is not the first time that a phable tool bites the SDK05:38
bzoltanToyKeeper:  I wish to have a test plan and QA validation for the phablet tools ... I cook from what is given to me.05:39
ToyKeeperbzoltan: You might want to talk with jfunk or perhaps asac about the intended role for QA in the landing process.  The idea isn't for developers to test some parts and QA to test the other parts.05:40
bzoltanToyKeeper: But I got your point. The 05.09 landing I have validated with the right click setup.05:40
ToyKeeperThe reason for traincon 0 (and the similar rtm landing process) was because people weren't even running the tests, or didn't understand what needed to happen, so QA got involved to fix the process issues and help get everyone on the same page.05:41
bzoltanToyKeeper: You do awesome job to secure the quality.05:41
bzoltanToyKeeper:  fixing the problems I would start releasing proper tools what the devs should use to validate their MRs05:41
ToyKeeperbzoltan: I hear there is an effort in progress to run the CI tools against every MP so it'll have those results before landing.05:42
ToyKeeperNot quite the "make CI work for individual use on local devices" I had in mind, but still good.05:42
bzoltanToyKeeper:  I am running the tests 24/7. In the last 24 hours I have 5 tims the ful UITK test plan. But unreliable test tools and flaky AP tests can indeed show strange results.05:42
bzoltanToyKeeper:  But devs are expected to run tests locally05:43
ToyKeeperI'm hoping the tools will also be made robust for personal use.05:45
bzoltanToyKeeper: We had talked about it with the QA team on the last sprint. I have proposed to require the same quality standards from the phablet tools as we require from the apps and other  components.05:47
ToyKeeperQA has had a lot less time for tooling lately though, due to the need to check each silo.  :(05:47
bzoltanToyKeeper:  for example I did not know that phablet-click-test-setup does not work on the RTM image with the default parameters as it works on the ubuntu image.05:48
ToyKeeperA lot of rtm infrastructure was put together in a hurry, I'm not surprised the auto-detection didn't get implemented.05:49
robruMirv: can you elaborate on this "new normal"? I thought the issue was that it reports successful migration immediately, and then you unsuspectingly free the silo before it is really copied. I'm not aware of any issues where it fails to publish even if you just give it time before freeing.06:19
robruAren't we expecting sil back today? Shouldn't he be on by now?06:19
robruMirv: Ooooooooooh, just saw your email, thanks for that06:27
Mirvrobru: you're welcome :)06:29
Mirvthose are the usual cases06:29
Mirvsil2100 should be around today, but he usually is around in about 30min - 1h from now06:30
robruAh OK06:46
sil2100o/06:49
robrusil2100: Heyo06:51
robrusil2100: welcome back, i hope you had a restful week ;-)06:52
Mirvsil2100: welcome back!07:13
Mirvdbarth: shall we get the testing done for rtm silo 017 today? since it's blocking that already (upstream) tested unity8 landing from going to QA signoff phase07:14
dbarthMirv: hi07:33
dbarthMirv: i need to ask someone else with an rtm installed; hold on07:34
sil2100robru: hey! You feeling better now?07:34
robrusil2100: yeah but just barely, thanks07:36
robrusil2100: I didn't get as much done with the train as I'd wanted, but I fixed some stuff and I got some tests in. Please skim over my recent commits when you get a break from the landing craziness07:39
sil2100robru: thanks, will do! Did you manage to do the big args-to-env change?07:39
robrusil2100: that was the first thing I accomplished ;-) so happy to see that code gone!07:40
Mirvdbarth: thanks07:40
ogra_hmm07:42
ogra_something got seriously out of sync ...07:42
ogra_rtm images failed07:42
robrusil2100: you won't recognize the deploy script ;-) just wish I had been healthy enough to make those kinds of changes everywhere07:42
ogra_seems ubuntu-touch is uninstallable in rtm07:44
robrusil2100: OK, bedtime for me, good luck today!07:44
sil2100robru: no worries, let me take a look - we'll have time to do that next week still07:44
sil2100robru: goodnight! :)07:44
sil2100ogra_: oh, does it say why?07:45
ogra_well, apt is as informative as ever  :P07:45
ogra_http://paste.ubuntu.com/8316717/07:45
brendandbzoltan, i see you have another silo ready - i would *really* appreciate those logs for the tests you ran - please07:46
bzoltanbrendand:  as we agreed yesterday: http://people.canonical.com/~bzoltan/ap-2014_09_10-19_29_44/07:46
Spads5.8G    ./var/lib/jenkins/silos/ubuntu-rtm/landing-01707:46
SpadsThat's a lot for this system07:46
brendandbzoltan, great! keep doing that :)07:47
brendandbzoltan, as a reward i will test your silo :)07:48
bzoltanbrendand:  I will do that from now. Thanks for testing the silo. if you need any help please shoot.07:49
ToyKeeperbzoltan: Quick question...  silo rtm/landing-009 says it was tested on rtm image 32, but image 30 is still building.  How did that happen?07:50
brendandToyKeeper, mako probably07:50
brendandbzoltan, we really do prefer you test on krillin if possible, but if not mako is acceptable07:50
bzoltanbrendand:  I would happily test on krilling if I would have one. It is coming as I have heard.07:51
MirvSpads: it's Oxide in there at the moment..07:51
brendandbzoltan, you could add a reference to that location on the test plan07:51
SpadsMirv: is it going to go out any time soon?07:51
brendandbzoltan, fair enough then - no problem07:51
Spadsand yeah: 3.6G    ./var/lib/jenkins/silos/ubuntu-rtm/landing-017/build/oxide-qt07:52
MirvSpads: as soon as possible we hope, but upstream tests it today and then QA needs to test and sign it off07:52
SpadsI only ask because it makes the backups unusually large as well, and that builds up over a week07:52
Spadsbut if this is the normal operating size of things for ci-train, maybe the backup policy needs to be revisited07:52
ToyKeeperbrendand: If you prefer, I could start the UITK tests running before I go to bed.  I still have everything open and set up from last time.07:53
ToyKeeperbrendand: If not, you might want to look at this for some possibly-helpful changes: lp:~toykeeper/ubuntu-ui-toolkit/test-plan-qa-changes07:53
brendandToyKeeper, if you're confident there won't be any hiccups, sure07:53
ToyKeeperbrendand: No, not really confident.  There are a *lot* of test failures each time, and many of them change with each test run.  It's difficult to get silo-vs-baseimage results which can be compared.07:54
brendandToyKeeper, i may as well do it then07:55
brendandToyKeeper, should that script just run unattended?07:55
Mirvogra_: it looks like rsyslog from last night's landing is stuck in rtm proposed07:55
ogra_Mirv, gah07:55
ogra_thanks for spotting that07:56
brendandToyKeeper, where does it install the silo?07:56
ogra_did we have a new UITK ?07:56
ToyKeeperbrendand: Bottom section of this: https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit07:56
ogra_seems that dropped 200 tests07:56
Mirvogra_: in rtm, only after the image build07:57
ogra_Mirv, right, i'm looking at 23507:57
ogra_which had it before07:57
ogra_bzoltan, http://ci.ubuntu.com/smokeng/utopic/touch/mako/235:20140910:20140903.1/10335/ubuntuuitoolkit/07:58
ogra_Total tests:2707:58
ogra_i assume that should be one or the other test more07:58
ToyKeeperbrendand: The provisioning for UITK tests is a little more complicated than other projects, and some things need to happen in a different order.07:58
bzoltanogra_:  yeah, a few more ... like 270+ more07:59
ogra_heh, thought so07:59
bzoltanToyKeeper: brendand: for the UITK testing I would recommend the script in the UITK project.07:59
ToyKeeperbzoltan: Indeed.  Just not necessarily the provisioning / commissioning parts.08:00
bzoltanToyKeeper:  I would say that especially that one08:00
bzoltanToyKeeper:  the most important is to remove the UITK tests from the ~phablet/autopilot/08:01
bzoltanToyKeeper:  so that you actually test with the release candidate and not with the archive AP tests08:02
bzoltanToyKeeper:  also, the gallery-app bug can still cause surprises .. so removing the cache could save a day08:02
brendandToyKeeper, see ogra_ 's comment - did you notice that?08:04
bzoltanbrendand: ToyKeeper: but the killer of all automatic provisioning is this one -> https://bugs.launchpad.net/ubuntu-rtm/+source/base-files/+bug/136121308:04
ubot5`Ubuntu bug 1361213 in software-properties (Ubuntu RTM) "add-apt-repository doesn't work" [High,New]08:04
brendandbzoltan, you don't need to tell me - look at the reporter :/08:04
bzoltanbrendand:  I know :)08:04
ToyKeeperbzoltan: That add-repo bug is trivial to work around.08:04
bzoltanToyKeeper:  Good to know :)08:05
brendandToyKeeper, yeah it's not difficult but still annoying08:05
bzoltanToyKeeper:  would you please share :)08:05
ToyKeeperecho URL > /etc/apt/sources.list.d/foo.list ; apt-get update08:05
sil2100ogra_: no UITK release in #235, I wonder why we only got 27 tests there08:05
ogra_Mirv, so i wonder if we could just sync dbconfig-common from utopic, that should release rsyslog08:06
bzoltanToyKeeper:  ehh.. I though there is a real one :) That one I know08:07
ToyKeeperecho "deb http://ppa.launchpad.net/ci-train-ppa-service/landing-$silo_number/ubuntu-rtm 14.09 main" > /etc/apt/sources.list.d/rtm-"$silo_number".list08:07
ogra_brendand, davmor2, seen bug 1367916 ?08:11
ubot5`bug 1367916 in messaging-app "Phone freezes when trying to active the dialer app from the messaging menu" [Undecided,New] https://launchpad.net/bugs/136791608:11
psivaaogra_: brendand : Mirv: sorry dint read all the backlogs, but do you see  issues seen in flashing devices with utopic-proposed both krillin and mako (rtm -29 and utopic-236?08:12
ogra_psivaa, i did an OTA ... whats your issue ?08:13
brendandogra_, can't say i have, but i'll check08:13
brendandogra_, what i did see though is that something broke trust-store location prompts08:13
ogra_again ?!?08:13
ogra_geez08:13
ToyKeeperOkay, updated the wiki page for UITK test plan, fixed two things I missed while writing it.08:13
brendandogra_, this time on krillin08:13
brendandogra_, before it was only mako08:13
ogra_oh, i thought it was there on krillin too08:14
ogra_at least during the tests08:14
brendandogra_, depends on the issue we're talking about08:14
psivaaogra_: this was fresh flashing with --wipe, we have 6 devices out during flashing08:14
psivaaogra_: 3 krillins and 3 makos08:14
brendandogra_, i'm talking about the one we found when we promoted the last mako image08:15
ogra_psivaa, damn08:15
psivaaogra_: yea, curious if someone try locally and send out an email if it's confirmed?08:15
vilapsivaa: only 6 ? nagios seems to report far more than 6 no ? Including flo08:15
brendandpsivaa, flashing utopic?08:16
ogra_brendand, yeah08:16
sil2100Are there problems with flashing utopic?08:16
psivaavila: i haven't crawled my way upto flo yet08:16
brendandhaven't tried that recently08:16
psivaabrendand: yes08:16
brendandpsivaa, mako too?08:17
psivaabrendand: yes08:17
psivaabrendand: both krillin (with image-29) and mako (with image 236)08:17
sil2100psivaa: flo and manta are ok?08:18
psivaasil2100: i haven't yet checked them, but vila reports they are down too08:18
psivaasil2100: and welcome back08:18
sil2100psivaa: thanks :)08:19
sil2100The UITK run for #235 looks strange08:19
brendandsil2100, there was a landing08:22
brendandToyKeeper, still here?08:22
ToyKeeperbrendand: Yes, briefly.08:22
sil2100brendand: I checked the changelog and commitlog for #235 and there was nothing08:22
sil2100brendand: at least not directly touching UITK08:22
brendandsil2100, oh so it didn't land there?08:24
brendandToyKeeper, when did you pass uitk?08:24
sil2100brendand: we're talking about utopic here08:24
sil2100Not RTM08:24
ToyKeeperbrendand: After the image started building.  But I didn't see that there was another UITK silo until afterward.08:25
ogra_psivaa, bah, doesnt boot08:25
brendandsil2100, oh i see08:25
ogra_psivaa, sitting at the google logo08:26
brendandsil2100, well i wipe my hands of your utopic :)08:26
psivaaogra_: right, i think that's the issue that we are seeing. 14 devices with upstream merger jobs too08:26
ogra_damn08:26
Mirvogra_: dbconfig-common? utopic has a version of it from 201108:26
davmor2ogra_: yes I can reproduce that bug, The number is being added to the emergency dialer which is why it looks like it is frozen, if you exit the emergency dialer and log in the number is in the dialer in the real session and works as expected08:26
ogra_Mirv, well, rmadison doesnt think it is in rtm ... and rsyslog-mysql|-psql depends on it08:27
Mirvogra_: right, it doesn't exist _at all_ in rtm08:27
ogra_davmor2, sound like i heard that before, is that an old bug ?08:27
Mirvso hmm I guess that'd be it08:27
ogra_right08:28
ogra_just pull it in and we should be good08:28
davmor2ogra_: not that I'm aware of08:28
ogra_k08:28
* ToyKeeper -> sleep08:29
ogra_psivaa, it booted now ... butu it took very very long08:30
ogra_psivaa, hmpf, i fear thats my fault ... the emulator fix seems to turn off adb on boot08:32
psivaaogra_: ack, that means we have a fix on the way :)08:33
bzoltanogra_:  how to turn the developer mode on with the #236?08:34
ogra_bzoltan, see above ... there is a bug08:34
ogra_bzoltan, test with 23508:35
brendandMirv is the first outsider to comment on our trello board!08:35
brendanddavmor2, we need to give him a prize08:36
Mirva prize \o/08:37
evsil2100: do you see any problems in excluding the silos/ directory from backups of the train? We can easily re-create their contents, correct?08:38
evtrying to get out of this disk space hole08:38
davmor2brendand: he gets to keep his cat we stop sil2100 steeling it08:38
bzoltanogra_: I just flashed 236 :(08:38
bzoltanogra_:  is there a way to enable adbd in the treminal app?08:42
ogra_brendand, sure08:42
Mirvdavmor2: thanks for the protection :)08:42
ogra_andr<doubletap> enable adb08:42
ogra_;)08:42
bzoltananything simpler? :)08:43
ogra_you could try a hammer ... but i wont promise success :)08:44
bzoltanogra_:  ohhh... I just tried. It broke my device. :D08:46
asacubuntu-device-flash doesnt work for us anymore :)08:48
asacubuntu-device-flash --channel=devel-proposed with a mako connected08:48
asacbut guess tvoss asked elsewhere already08:49
asacso /me will wait for his answer08:49
brendandogra_, i can't repro that bug in RTM08:49
brendandasac, yes it's broken08:49
ogra_brendand, which bug ?08:49
asacbrendand: broken?08:50
asachow come?08:50
brendandogra_, the messaging app one08:50
asacwho broke?08:50
ogra_brendand, ah08:50
brendandasac, i'll let them confess :)08:50
asachehe08:50
asacwell. how ?08:50
asacupload of ubuntu-device-flash?08:50
asacor server busted?08:50
brendandasac, adb not being started08:50
brendandadbd08:50
asacdev mode?08:50
ogra_asac, looks like a system-image server issue if you ask me08:50
ogra_brendand, unrelated08:50
brendandogra_, really?08:50
ogra_yes08:50
ogra_oh, wait, probably not08:51
asacare you on it?08:51
brendandogra_, i didn't see all the details of asacs issue08:51
ogra_brendand, i got tvoss' details08:51
asacsudo ubuntu-device-flash --channel=ubuntu-touch/devel-proposed08:51
asac2014/09/11 10:47:11 Expecting the device to expose an adb interface...08:51
asac2014/09/11 10:47:11 Device is |/bin/bash: /root/.bash_profile: Permission denied08:51
asacmako|08:51
asac2014/09/11 10:47:11 Device /bin/bash: /root/.bash_profile: Permission denied08:51
asacmako not found on server https://system-image.ubuntu.com channel ubuntu-touch/devel-proposed08:51
asacthast what i see08:51
bzoltanI see the same08:52
ogra_right, the last message confused me08:52
asacsurely a follow up from the stuff before08:52
asacor at least very likely08:52
ogra_then its the last lxc-android-config landing08:52
ogra_i see whats wrong and have a fix,08:52
asacthx08:52
asacdoes this affect ability to upgrade?08:52
asacfor thos taht have something installed?08:52
ogra_not OTA, no08:52
asacok08:53
asacso just newcomers cannot flash08:53
asacand infrastructure08:53
ogra_and u-d-f will work from reciovery08:53
ogra_asac, right, i'm aware since 30min08:53
vilaogra_: so this explains all (almost, 14 at least and counting ;) the devices in the infra being busted ?08:54
vilaogra_: with image #236 that is08:55
ogra_vila, yes, see the backlog and my conversation with psivaa08:55
bzoltanogra_: I could boot to recovery and now i am fahsing 235 with bootstrap08:57
ogra_bzoltan, yeah, that will work fine08:57
ogra_(as well as just enabling adb with the above command in the terminal)08:57
bzoltanogra_:  ... and the hummer08:58
ogra_lol08:58
bzoltanthat works always ... I was told today by my 5yo08:58
Mirvtvoss: non-approved https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-int64-signature/+merge/23251109:02
tvossMirv, done, and sorry09:03
Mirvthostr_: note line 32 is not marked as Ready?, should it be? (rtm fix apparmor settings)09:04
Mirvtvoss: why does libmedia-hub-common2.symbols only have one symbol while the common1 had many? https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/12/artifact/packaging_changes_media-hub_2.0.0+14.10.20140910.2-0ubuntu1.diff09:05
tvossMirv, I added a symbols.map to prevent weak stl symbols bleeding into the exposed set of symbols09:06
tvossMirv, we are doing that for almost all projects now, media-hub is one of the remaining ones09:06
Mirvtvoss: oh, stopping bleeding is good indeed09:07
Mirvsil2100: there's a need for MOTU here https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/09:07
Mirvmy motu meeting is in 1.5 weeks ;)09:07
sil2100Mirv: looking :)09:08
sil2100Mirv: well, there's no way you won't become a MOTU ;) So it's just a matter of time09:09
brendandsil2100, can you help me out with a couple of silos?09:09
Mirvsil2100: hehe09:11
sil2100Mirv: looks good, although it's really fishy that the symbols-count for the -common library fell down so much ;) But I guess since it builds, then it has to mean everything is OK09:11
sil2100Mirv: so a +109:11
sil2100brendand: what's up?09:11
brendandsil2100, i tested silo 14 earlier this week and found an issue09:12
brendandsil2100, the lander prepared a fix which they already landed in utopic09:12
brendandsil2100, that fix is in silo 15 now09:13
brendandsil2100, but it fixes a bug that only exists in silo 1409:13
brendandsil2100, is that ok, or is it going to cause issues?09:13
brendandmaybe i need to test and land them together?09:15
thostr_Mirv: line 32 is ready... seems I overlooked it09:16
sil2100cjwatson: hey! If I would like a new package in ubuntu-rtm which is available in ubuntu, can I simply publish it to ubuntu-rtm?09:17
sil2100cjwatson: or do we need something else to make sure ubuntu-rtm recognizes it?09:17
sil2100brendand: let me read up, one moment :)09:18
sil2100brendand: so, in other words... there are two rtm silos with the same component, right? 14 and 15?09:19
Mirvsil2100: thanks! yes I checked the symbols with thomas09:21
Mirvthostr_: ok, thanks!09:22
sil2100brendand: since because you say that the packages that are in silo 15 are already in utopic, what we can do is simply rebuild unity-scope-mediascanner in silo 1409:24
sil2100brendand: then silo 14 will have everything that you need09:25
sil2100brendand: since it will have the 2 other packages for itself + the latest of the latest from silo 1509:25
brendandsil2100, yeah i would rather have everything in one place09:26
brendandpete-woods, ^09:26
sil2100brendand: oh, I see it's no longer a sync silo09:27
sil2100brendand: ok, let me get everything you need into one silo anyway :)09:27
pete-woodsbrendand: okay, so what do you need me to do?09:28
pete-woodsam I rebuilding the mediascanner silo?09:28
brendandpete-woods, i don't *think* you need to do anything09:28
brendandpete-woods, just waiting for those test results09:29
sil2100pete-woods: no worries, I'm handling everything :)09:30
sil2100pete-woods: I'm making sure that everything is in silo 14 that's needed09:30
dbarthMirv: for silo 17 testing, either i need to wait for alex-abreu later today, or maybe i can stand by during the qa signoff to speed that up?09:30
sil2100ev: hmm, from first thought it might be ok, but let me double check something in a moment09:32
pete-woods:)09:33
evokay09:34
popeyMirv: could you please upload http://s-jenkins.ubuntu-ci:8080/job/sudoku-app-click/lastSuccessfulBuild/artifact/com.ubuntu.sudoku_1.1.282_all.click to the store?09:35
sil2100cjwatson: for now I'll try using a silo to sync it up09:36
popeyMirv: http://s-jenkins.ubuntu-ci:8080/job/weather-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.weather_1.1.365_all.click also please09:36
Mirvdbarth: what do you mean by stand by? maybe you could negotiate whether QA would be ready to start testing the silo without your approval, or that you would mark it as "tested" (the utopic equivlent was) to get it progressing?09:38
Mirvpopey: noted. my click-toolbelt just decided python doesn't have datetime module, so might need some time09:41
popeyoof09:41
dbarthMirv: have QA start testing to confim the silo; quicker easier, it's a set of bug fixes09:44
Mirvdbarth: right. please talk to brendand davmor2 about that (this is about silo 017)09:45
dbarthlet me know who gets started on that and i can just help drive the test in a hangout09:45
Mirvdbarth: they have currently it and silo 010 on hold until 017 would be marked as ready for signoff testing09:45
dbarthok clear09:45
seb128dbarth, could you look at https://bugs.launchpad.net/ubuntu-facebook-app/+bug/1367704 to check if it's assigned to the right component (it's a bug from jane)09:49
ubot5`Ubuntu bug 1367704 in Ubuntu Facebook App "Facebook account not recognised by Facebook webapp" [Undecided,New]09:49
dbarthseb128: it's not; but ok, taking care of it09:51
seb128dbarth, thanks09:51
cjwatsonsil2100: you can just copy it, sure09:57
cjwatsonsil2100: context?09:58
cjwatsonsil2100: is this rsyslog?09:58
=== psivaa changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: psivaa | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings.
ogra_cjwatson, yeah10:02
ogra_it broke image builds today10:02
davmor2dbarth: we can't touch silos till they are listed for QA sign off10:04
cjwatsonsil2100: using a silo for this is pointless - we should either force it, or else just do a direct binary copy into 14.09-proposed10:04
* ogra_ would do the latter 10:04
brendandpete-woods, i think silo 14 should be retested10:04
cjwatsonsil2100: why did you rebuild this package?10:05
cjwatsonsil2100: seriously, let's stop doing pointless source-only copies when we just want to get the dependencies satisfied10:05
dbarthdavmor2: i marked it test pass but left the #, does that help?10:06
dbarthapparently the queuebot noticed ;)10:06
davmor2dbarth: we'll find out in a second thanks10:07
dbarthok, let me know if you want to open a hg; it's a quick test (apart from your own test round)10:08
brendand17 is ready now10:08
jameshdavmor2, brendand: I posted an update on https://bugs.launchpad.net/unity8/+bug/1367400 about the bug in launching music-app for music on the SD card: in short, the fix to switch to music:/// has not made it to ubuntu-rtm yet10:11
ubot5`Ubuntu bug 1340952 in url-dispatcher (Ubuntu) "duplicate for #1367400 Video and Music scopes should provide non-file:/// based URIs" [High,In progress]10:11
brendandjamesh, is it in silo 14?10:11
sil2100cjwatson: can you just do a direct binary copy then?10:12
jameshbrendand: doesn't look like it.10:12
brendandjamesh, oh ok10:12
sil2100cjwatson: it's a package from main so I have no power over it besides through a silo10:13
jameshbrendand: was blocked waiting for QA approval for a landing to utopic, which looks like it has completed now10:13
brendandpete-woods, jamesh - so can we agree that you'll rerun the localmediascopes test plan for silo 14 and record the results somewhere?10:13
sil2100cjwatson: I can do a binary copy to the silo and then release, but yeah...10:13
cjwatsonsil2100: done10:13
cjwatson$ copy-package --from=ubuntu --from-suite=utopic --to=ubuntu-rtm --to-suite=14.09-proposed -b dbconfig-common10:13
sil2100cjwatson: thanks!10:13
sil2100cjwatson: well, in theory I can't do that for a main package, right?10:14
cjwatsonindeed10:14
sil2100cjwatson: or can I?10:14
cjwatsonI don't believe you'll be able to10:14
cjwatsonbug: sil2100 is not core-dev :)10:14
sil2100;p10:14
cjwatsoneven if you need to use a silo, though, please just binary-copy from ubuntu for this kind of thing10:15
cjwatsonthe reversioning and rebuilding gains us nothing, and potentially even introduces issues (e.g. if somebody has a >= dependency on the latest version of the thing we're copying)10:16
cjwatsonthe source of this issue was a bug in the original ubuntu-rtm copying script10:16
cjwatsonI followed through dependencies on everything we actually needed, of course; but I didn't follow dependencies of other binaries built by the same source as binaries we actually needed10:17
sil2100ACK o/10:18
cjwatsonI think at this point it is probably too hard to safely fix in bulk for 14.09, and we should just deal with it as it comes up10:18
sil2100Right10:18
sil2100Yeah, I'll do binary-copies in such cases, I'll also inform other people from the landing team to do the same thing in cases of missing deps10:18
cjwatsonbad morning for me to be late in, I guess :-/10:18
cjwatsonI've previously forced proposed-migration to ignore a few things like this10:19
cjwatsonbut it's probably better to chase the copies, now that I've thought about it a bit10:19
brendandpete-woods, i've set 'Testing pass' back to No. please do retest silo 14 and provide the results, then set it back to Yes10:20
cjwatsonwell, except that chasing the copies for ubuntu-desktop-next/ubuntu-sdk would take ages; for that one it's probably still better to force, as a matter of pragmatism10:21
pete-woodsbrendand: okay, will have james re-run the tests..10:21
Mirvpopey: ok... sudoku and weather uploaded. yesterday's python2.7 update broke it, I had to downgrade.10:24
popeyMirv: thank you!10:24
popeyMirv: sorry, one more http://s-jenkins.ubuntu-ci:8080/job/reminders-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.reminders_0.5.248_armhf.click please10:29
jameshbrendand: from above, RTM silo 14 does contain the required fixes.  I was looking at the wrong page of the dashboard10:30
sil2100cjwatson: btw. do we have a madison.cgi for ubuntu-rtm?10:35
brendandjamesh, the required fix for the RTM blocker right? i.e. 'Play in music app' is broken for songs on the SD card10:36
jameshbrendand: correct.10:36
brendandjamesh, ok, i wasn't expecting it would10:36
brendandjamesh, if a test in the test plan fails because of it, just note the bug as the reason why10:36
cjwatsonsil2100: just the normal one - use rmadison10:36
brendandjamesh, and one should :)10:36
cjwatsonsil2100: (I fixed that last Thursday)10:37
brendandjamesh, so if not then maybe you need another test :)10:37
evsil2100: thoughts on those backups?10:37
sil2100cjwatson: ah! Indeed, I see ubuntu-rtm :D10:37
sil2100ev: taking a look at that now10:37
jameshbrendand: I guess so.  At the moment, I wrote most of the test plan but none of my devices have an SD card10:38
brendandjamesh, oh i see10:38
evsil2100: thanks10:38
brendandjamesh, every team should really have someone with a krillin to test landings. that doesn't seem to be the case at the moment10:39
jameshbrendand: once we've got mediaplayer-app updated to accept video: URIs and the videos scope updated to match, the special cases for the file:///home/*/Music in the URL dispatcher can be removed10:39
brendandjamesh, might be worth it to add the test anyway with a note like 'mark this test as skipped if you do not have a device with an SD card'10:40
asacscreen not going off automatically is a known regression/blocker?10:40
jameshbrendand: at that point, there should be no difference between music in the home directory and on the SD card: they'll either both work or both fail10:40
* asac had that on utopic yesterday and today on rtm10:40
cjwatsonsil2100: I think dbconfig-common is probably actually published, but the archive-reports business that (as a side-effect) updates rmadison's view of the world is being slow - it'll catch up by itself before I can do anything about it, but I'm going to look into some of the current perf problems there10:41
cjwatsonsil2100: yep, it shows as published now, so I expect you can kick an image build10:41
sil2100ogra_: can you kick a new RTM build then?10:42
sil2100cjwatson: thanks :)10:42
cjwatsoncan't you?  should be on iso.qa10:42
sil2100It's on iso already?10:42
sil2100Last week it still wasn't10:42
cjwatsonhas been for a while10:42
cjwatsonI thouht10:43
cjwatson+g10:43
ogra_asac, i saw someone mention it on one ML10:43
ogra_but not sure there is even a bug for it10:43
ogra_it seems to be very random10:43
cjwatsonanyway I get http://iso.qa.ubuntu.com/qatracker/milestones/321/builds linked from the front page10:43
ogra_(i have seen it too before)10:43
ogra_sil2100, on it10:43
ogra_cjwatson, no products there yet10:43
cjwatsonoh, "no build available".  hmm.10:43
ogra_there is a section10:43
ogra_but stgraber need to add some content for us :)10:43
asacogra_: who would usually right person to talk about what info to extract when i get to that point again?10:43
cjwatsonright, ok, can be done manually then :)10:43
asacis that powerd? or rather unity?10:43
ogra_i pinged him about that during debconf ... he had no time and we both forgot again10:43
ogra_asac, krillin ?10:43
asacboth10:43
sil2100ogra_: thanks :)10:43
asacfirst on n4 yesterday10:43
asactoday on krillin10:43
asacthink its all same same10:44
ogra_asac, krillin has a very specific kernel fix10:44
ogra_i have never seen it on mako here10:44
asacright. i had it yesterday for hours on mako10:44
ogra_i think since the kernel change got in i see it on krillin ... but really rarely ... every third or second day once10:44
ogra_asac, so yeah, file a bug, that points more towards powerd then10:45
asacogra_: who owns tpowerd? doesnt help to file a bug if i cannot extract any info i am sure... folks will say they cannot reproduce10:45
asacso next time i see i want to talk what to extract to help debugging10:45
brendandsil2100, where can i see the version of X package in proposed for RTM?10:45
cjwatsonbrendand: rmadison <package>10:45
ogra_asac, well, phonedations ... kind of ... i think10:46
brendandcjwatson, rmadison of course10:46
cjwatsonbrendand: or https://launchpad.net/ubuntu-rtm/+source/<sourcepackage>/+publishinghistory10:46
sil2100brendand: right, rmadison and check the ubuntu-rtm/14.09 version10:46
asacogra_: ok so ChickenCutlass :)10:46
asacwill just go through him next time10:46
* asac leaves ogra alone who surely has more important things to fix like image not flashing :)10:46
asaclol10:47
ogra_asac, twiddling thumbs waiting for the publisher is my main job currently :P10:47
ogra_fixes are uploaded10:47
sil2100ogra_: ;)10:47
cjwatsonogra_: waiting for which packages?10:47
sil2100ogra_: fixes or reverts?10:47
ogra_cjwatson, android-tools10:47
asacogra_: can you extend the testplan for that component so we test upgrading nmext time?10:48
ogra_sil2100, fixes ... the adb not starting was a dumb quoting issue in an upstart script (' vs ")10:48
asacnot sure how to do, but thats the key to avoid these in future i am sure10:48
asacthink its about adding that you flash another time after first try10:48
cjwatsonogra_: right, so you're currently waiting for proposed-migration and then the publisher, but yeah :)10:48
ogra_asac, both packages will get QA testing in silo 13 today, so yes, there will be a test plan attached we can re-use later10:49
ogra_(for rtm)10:49
ogra_asac, the prob is that you can not easily test android-tools on krillin at all ... thanks to the device tarball bind mounting upstart jobs over the originals10:49
asacok10:50
ogra_we need to drop that habit :P10:50
asacwell. think that needs to be tackled or at least started10:50
asacmaybe its a tooling problem that we can improve without having to kill that habit short term10:51
ogra_upstart jobs need to be fixed in the package, not by overlaying with a device specific hack10:51
ogra_(this is ok during porting, but part of the porting work should be to get the fixes merged in the actual packages :) )10:51
sil2100ev: ok, so... the ~/silos directory has the complete state of the backend for the CI Train, so it actually has all the config files and project files without which we can't build or publish things properly10:52
sil2100ev: when are the backups made?10:52
evdaily10:52
sil2100ev: where do we have the backups stored?10:53
evsil2100: we're going to move them to Swift10:55
evsil2100: is there a pattern under silos we could exclude?10:56
evsome of the build dirs, perhaps?10:56
bzoltanbrendand: ToyKeeper mentioned that she had trouble with the phablet-click-test-setup --distribution=ubuntu-rtm --series=14.0910:56
brendandbzoltan, oh i didn't hear about that10:58
bzoltanbrendand: I just got it crashing10:58
brendandbzoltan, btw i just confirmed a bug in your new silo11:00
brendandbzoltan, i'll check if it's in utopic and file a bug11:01
brendandoh crap - i can't flash utopic11:01
brendandogra_, can i flash utopic yet?11:01
ogra_brendand, nope, still waiting for one package ... then 1.5h build time11:01
ogra_(for the image)11:02
cjwatsonit's waiting for autopkgtests11:02
brendandbzoltan, so something breaks dialer-app11:02
sil2100ev: let me think...11:02
brendandbzoltan, when you drag up the recent calls list it messes the ui up11:02
sil2100ev: for sure we can get rid of the build-area/ directory inside11:02
brendandbzoltan, like this: http://people.canonical.com/~brendan-donegan/recent.png11:02
cjwatsonwhich are done, actually, so should work on the next pass11:03
brendandbzoltan, it's not in the silo ToyKeeper just landed, but the new one11:03
sil2100ev: the ubuntu/ directory should be removable as well11:03
brendandbzoltan, i assure you i only upgraded uitk, nothing else11:03
=== MacSlow is now known as MacSlow|lunch
brendandbzoltan, the AP tests for dialer-app did not fail, so are not adequate to catch this11:03
bzoltanbrendand:  we have the standup  right now ... could you please join11:04
bzoltanbrendand: Mumble - orange room11:04
evsil2100:  thanks11:04
sil2100ev: the most important things in the silo directories are: the config file, *.project* files and the bzr source directories11:04
brendandbzoltan, actually i'm just going on my lunch breal11:04
brendandbreak11:04
brendandbzoltan, and i don't have mumble set up anyway11:04
Mirvpopey: reminders done too11:05
brendandhaven't since 201211:05
* popey hugs Mirv 11:05
bzoltanbrendand: :D11:05
* Mirv thinks fresh air would sound good11:05
brendandMirv, is the air quite fresh in Finland in September?11:06
brendandMirv, or still warm?11:06
Mirvbrendand: usually a bit "fresher", now +20'C11:06
brendandMirv, well that's no shirt weather here in GB11:06
bzoltanMirv:  we need you on the standup11:07
bzoltanbrendand:  it is possible that the UITK in the silo9 is not thr right one11:08
bzoltanbrendand:  the point here in Finland is that when you talk about 20'C then you have to put the + sign :)11:09
popeypsivaa: http://91.189.93.70:8080/job/generic-mediumtests-utopic-python3/285/console getting core dumps in music app...11:09
popeypsivaa: related... /tmp/hudson8910191033881077787.sh: line 81: 10540 Aborted                 (core dumped) qmlscene /tmp/main.qml11:09
popeypsivaa: seems strange given the music app main file isn't called main.qml... so wondering where that is coming from?11:10
psivaapopey: looking11:13
sil2100brendand: hey, you done with silos for now?11:14
brendandbzoltan, you mean not the one you tested?11:16
brendandsil2100, semi done. bzoltan will confirm if i'm testing the right uitk or not11:16
brendandsil2100, but i also have to have lunch now11:17
brendandsil2100, did you want me to check something out? i can take care of it when i come back online11:17
sil2100brendand: no worries - after you're done, could I interest you in some autopilot investigations? ;)11:17
bzoltanbrendand:  I am afraid that the UITK on the silo is missing a fix what landed on Ubuntu Utopic11:17
bzoltansil2100: brendand: so something might be very wrong11:18
bzoltanbrendand: Note that I have just learned today from ToyKeeper that the phablet-click-test-setup in default uses the Utopic tests and not the RTM tests....11:19
bzoltanbrendand:  so, let's rewind11:19
ogra_ah, android-tools moved on a bit :)11:22
sil2100bzoltan: if this was a sync from ubuntu to ubuntu-rtm, then everything from UITK from ubuntu should be in that silo - but maybe you're missing some dependencies that are required?11:23
sil2100bzoltan: and yeah, our tool seem not to be completely ready for RTM handling...11:23
brendandbzoltan, well i leave it up to you to provide a silo that is tested and ready for landing in RTM. let me know when that's the case11:24
bzoltansil2100:  I am afraid that the RTM silo was synced with the Ubuntu Silo before it still got a fix11:24
bzoltanbrendand:  OK, but for that I would need a functioning phablet-click-test-setup :(11:25
bzoltanbrendand:  but better be safe and check twice and hurry and make a mistake11:25
=== brendand is now known as brendand-afk
brendand-afksil2100, just tell me the details and i will look at it after an hour11:27
sil2100bzoltan: let me check how the silo is configured, maybe all we need is just press 'build'11:28
bzoltansil2100: that is what I hope11:28
sil2100bzoltan: hm, it seems to be up-to-date to what's in utopic!11:29
popeywhy was there no image 30 for krillin built last night?11:32
popey29 is latest, and that's yesterday, right?11:32
ogra_popey, archive screwup11:32
popeyah okay11:32
ogra_rtm you mean, right ?11:33
=== ubot5` is now known as ubot5
popeyyes11:33
popeythanks11:33
bzoltansil2100:  zsombi just checked on Utopic image and the problem is not there11:33
ogra_should pop out of the builder soon11:33
ogra_https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch ... rootfs is already done ...11:35
psivaapopey: the actual cause appears to be a transient error:  'Autolaunch error: X11 initialization failed.'. when running 'jack_control start'11:35
psivaafor the failure in http://91.189.93.70:8080/job/generic-mediumtests-utopic-python3/285/consoleText that is11:36
popeyhmm11:36
psivaathere were some xorg, x11 related packages upgraded11:36
popeyah okay11:36
ahayzenpopey, so does that mean it is 'no us' ? but something in the platform?11:37
popeyyes, not your fault11:37
popey.... this time....11:37
ahayzenlol11:37
psivaapopey: yes11:37
popey☻11:37
psivaapopey: i say this transient because the next job with the same parameters succeeded. please ping us if you see this again11:37
ahayzenwhats pulling down jack_control? or does that get pulled with part of pulse/gst?11:37
popeyok thank you!11:37
popeyyeah, that's odd, i wouldn't have expected to see jack at all11:38
ahayzenpsivaa, it seems to be randomly happening...over the past day or so i would say we've had it ~3-4 times and if we rerun it then usually passes11:38
psivaaahayzen: hmm, yes seeing the same reason here: http://91.189.93.70:8080/job/generic-mediumtests-utopic-python3/279/consoleText11:40
psivaalet me dig in a bit more11:40
ahayzenpsivaa, thanks11:40
pete-woodsbrendand-afk: we have started compiling the sheet you asked for here: https://docs.google.com/a/canonical.com/spreadsheets/d/17FjOXaT-OsTnuSPnyv7kzEfubJadTaEjDO1gSAjRNCM/edit#gid=011:43
davmor2thostr_: grooveshark scope has no album art any more is this a known issue?11:51
bzoltanbrendand-afk: sil2100: Mirv: I am blocked with the RTM validation of the UITK -> http://pastebin.ubuntu.com/8318350/11:52
ogra_cjwatson, gah, my ssh connection to nusakan has dropped, do i need to re-run without --live ? seems while the rtm rootfs has built it didnt get published11:53
cjwatsonogra_: did you run it in screen?11:54
ogra_indeed not :P11:54
cjwatsonget into the habit :)11:54
ogra_heh, yeah11:55
cjwatsonogra_: I expect you will need to rerun without --live, yes11:55
ogra_ok11:55
cjwatsonit doesn't appear to be running now11:55
ogra_i build directly on nusakan so raraely nowadays that i dropped the habit ... i used to use screen11:55
psivaaahayzen: popey: still no concrete idea why 'jack_control start' fails intermittently this way. something underneath is racy. i'd talk to fginther to about it11:55
cjwatsonI have a local "s" command that I basically always use when connecting to DC machines, so I don't forget11:56
cjwatson#! /bin/sh11:56
cjwatsonexec ssh -t "$1" screen -ARD11:56
ogra_bah, stale lock11:56
ogra_lockfile: Sorry, giving up on "/srv/cdimage.ubuntu.com/etc/.lock-build-image-set-ubuntu-touch-ubuntu-rtm-14.09-daily-preinstalled"11:56
ogra_Another image set is already building!11:56
cjwatsonwait one moment then11:56
ogra_k11:56
ahayzenpsivaa, thanks for looking into it11:56
ogra_hmpf ... and the iso tracker forgot all my checkmarks ... i get all images listed and it doesnt keep it when i uncheck the checkboxes ... weird11:57
cjwatsonogra_: ok, try again11:57
ogra_cjwatson, yep, better11:57
* cjwatson -> lunch11:58
cjwatsonbtw I've hopefully sped up the proposed-migration cycle a bit by filtering out some junk from http://people.canonical.com/~ubuntu-archive/testing/utopic_probs.html which was taking ages to analyse11:58
ogra_yay11:59
ogra_thanks11:59
cjwatsonstill needs work but it should help11:59
Mirvsil2100: just so you know, I triple-checked that yes the uitk rtm landing seems intact and identical to utopic archive version, so whatever problem comes from something else than the uitk being wrong version.11:59
Mirv(identical, but rebuilt)12:00
=== psivaa changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings.
ogra_sil2100, could you sync ubuntus latest lxc-android-config and android-tools into rtm silo 13 ? (or Mirv if you feel like)12:01
sil2100Mirv: so just as I expected, thanks!12:03
sil2100ogra_: I'm in the middle of consumption but let me take a look at that :)12:04
thostr_davmor2: not known... just wondering why 7digital still has...12:04
davmor2thostr_: I'll write up a bug for it then12:05
thostr_davmor2: thanks12:06
imgbot=== trainguards: IMAGE 237 building (started: 20140911 12:10) ===12:09
ogra_there we go12:10
* ogra_ hugs sil2100 12:12
thostr_davmor2: just check, album art seems to work for us12:14
thostr_davmor2: the issue is, that we switched from lastfm to 7digital for album art retrival12:15
* sil2100 hugs ogra_12:17
davmor2thostr_: https://bugs.launchpad.net/unity-scope-grooveshark/+bug/1368198  I see it on rtm for krillin and mako12:17
ubot5Ubuntu bug 1368198 in Unity Grooveshark Scope "Grooveshark is not showing any album art" [Undecided,New]12:17
davmor2thostr_: it might be that there is a scope update that you have that I don't12:18
thostr_and 7digital does not provide such a rich album art db12:18
ogra_sil2100, hmm, the custom tarballs cause the same prob we have with the krillin device ones ... i guess we need to make sure to also have the cusom guys coordinate their tarball pushes with us12:18
sil2100ogra_: who's responsible for those?12:20
ogra_sil2100, i guess cwayne12:20
ogra_or at least he should knwo if he isnt12:20
davmor2thostr_: just added another screenshot to the bug, that shows a search for bat out of hell 7d shows it grooveshark doesn't12:20
=== MacSlow|lunch is now known as MacSlow
=== brendand-afk is now known as brendand
brendandpete-woods, that's useful information, but what i was hoping for was a list of the test cases in each plan with the heading 'test,tester,result,comments'12:29
imgbot=== trainguards: RTM IMAGE 30 DONE (finished: 20140911 12:30) ===12:29
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/30.changes ===12:29
brendandpete-woods, we're sort of looking for explicit confirmation that each test was run and passed12:30
ogra_langpacks galore12:30
ogra_asac, btw, i can confirm your "screen doesnt shut off" bug on krillin now12:31
pete-woodsbrendand: so you want us to enumerate each test in the wiki page, and write "tested" next to it in the spreadsheet?12:33
Ursinhamorning12:33
pete-woodsbecause that's pretty much what will happen12:34
brendandpete-woods, 'pass/fail/skipped'12:34
brendandpete-woods, if skipped, comment why12:34
pete-woodssurely skipped would not be acceptable?12:34
asacogra_: ok ... is there new image with the fixed android tools already?12:35
brendandpete-woods, normally it wouldn't yes - but i there might be some cases12:36
asach i see that image build is in progress12:36
asac237 ... /me will wait12:36
ogra_asac, see above ... 237 is building since 15min12:36
brendandpete-woods, at least we'd know it was skipped for X reason, not that someone just chose not to run it12:36
brendandpete-woods, if doing this really feels like a lot of overhead then please let us know, but we're kind of trying to get better traceability into this process. you're being used as a guinea pig12:37
pete-woodsit's quite a lot of overhead, yes12:37
pete-woodsnow you've added this second part12:37
brendandpete-woods, really? initially perhaps12:37
pete-woodsbecause someone has to go through the wiki page, and turn it into a form to fill in12:37
pete-woodsevery time they run the test12:38
brendandpete-woods, you can do as little as copy it into a text file12:38
brendandpete-woods, and append notes to each line12:38
pete-woodsif you want a tick list for running the steps, we need something better than a wiki page manually transformed into a form12:38
thostr_brendand: I can see where you come from, but I'm wondering if that really improves testing12:39
thostr_brendand: since somebody who doesn't test properly can just tick off all tests12:40
thostr_brendand: wouldn't it be sufficient as first step to add two more columns to ci sheet if necessary12:41
thostr_brendand: that would be a) name of tester and b) comments about the test12:41
brendandthostr_, device tested on too12:43
thostr_brendand: sure12:43
thostr_brendand: but let's not overdue it, otherwise I feel that people will just ignore it and put in random stuff if at all12:44
brendandthostr_, pete-woods - to be honest i really don't see how, if the tests are actually being stepped through, that it's so much overhead just to write the outcome next to it. it can even be handy for the tester to see which tests they have run already12:44
thostr_brendand: it's the little heres and theres that add up12:45
dbarthwill we get another round of images today / tomorrow?12:45
brendandthostr_, you do realise this requirement was provoked by the fact that whoever ran the test plan for this silo very obviously did *not* run all the tests on the test plan12:45
thostr_brendand: I'm fully aware of this, therefore my comments12:45
thostr_brendand: what we (I) need to fix is the attitude of individuals12:46
sergiusenssorry for meddling, but sloppy testing can't be prevented; people that don't have a "testing" mindset generally miss a lot of things12:46
thostr_brendand: adding more buerocracy won't help12:47
thostr_sergiusens: +112:47
brendandsergiusens, but the problem is right now we have so little ability to trace what actually happened and try and improve things12:47
brendandthostr_, i really don't feel it's bureaucracy - transparency is what we're aiming for12:48
pete-woodsyes, but relying upon a "sloppy tester" to provide the information about whether he was sloppy or now seems flawed12:48
brendandthostr_, pete-woods - we should be able to distinguish between a case where someone has been sloppy and one where someone made a mistake or misunderstood something12:50
=== fginther changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings. Latest flash update hung all makos on s-jenkins.
brendandthostr_, pete-woods - can either of you actually tell me why this happened? is it because the test plan wasn't run full stop, or another reason?12:52
thostr_brendand: yes, which is because of sloppy testing12:52
thostr_brendand: the very same guy would have ticked all tested ok boxes12:52
brendandthostr_, i will add that what you suggested is definitely an improvement12:53
thostr_brendand: good. and as said, the rest is up to me to fix12:54
evsil2100: 1:47 PM <Spads> ev: ./var/lib/jenkins/citrain-preprod_old12:55
ev^ can we kill that?12:55
Spadssil2100: hi!12:55
Spadsit's dated 5 September12:55
brendandsergiusens, slopppy anything usually comes down to part of a process being difficult to understand or otherwise flawed12:55
sil2100ev: yes, I guess this is some backup from the past12:55
brendandsergiusens, e.g. ambigious test cases12:55
sil2100Spads, ev: so feel free to wipe this one out12:55
Spadscooool12:56
brendandsergiusens, it's not that common actually for people to make mistakes just because12:56
sergiusensbrendand: everyone makes mistakes; test plans that are manual will always have human error; be it sloppy or not12:57
brendandsergiusens, heck even automated tests do :)12:57
brendandsergiusens, human error all over the shop12:58
sergiusensbrendand: it would be nice to have something to tick when testing; but it would be another manual thing to do (even the setup for it)12:58
sergiusensbrendand: I guess what I'm saying is; no one would complain if it gets 'autocreated' on silo assignment and I just have to tick things (which I do visually while reading from the wiki plans anyways)12:59
brendandsergiusens, ok for now we won't require that level of detail - let's see if the additional information that thostr_ suggested gives us all the information we need12:59
sergiusensbrendand: it could be free form now, heck I do that13:00
brendandsergiusens, do you provide testing notes with your silos?13:00
sergiusensbrendand: I just add something into the comments saying I only tested certain surface areas as the MPs don't cover other isolated components13:00
sergiusensbrendand: if I have a special comment on why or what, yes13:00
davmor2dbarth: hit a snag,  can you add the ppa, open reminders, click on create account and then try and add an evernote account, for me I get the reauthorise popup I click on yes and online accounts crashes13:01
davmor2dbarth: _usr_bin_online-accounts-ui.32011.crash which has gone to errors.ubuntu.com13:01
dbarthdavmor2: i've seen this one13:03
dbarthdavmor2: ah no, not *that* particular one13:03
brendandsil2100, is this something we can add to the spreadsheet - tester name, device tested on, test comments13:03
dbarthhmm13:03
brendandsil2100, they might fit in other fields already i guess13:03
sil2100brendand: regarding lander testing?13:04
brendandsil2100, we could change the 'Testing pass' format to 'Yes (30) - brendand, krillin'13:04
pete-woodsit'd be better with separate fields for the data13:04
brendandsil2100, comments could go in comments, but that's kind of overloaded right now13:04
brendandpete-woods, i agree - if it doesn't cause any issues adding new fields13:04
sil2100brendand: the device name would make sense - as for the tester, we usually assume it's one of the landers doing it13:05
sil2100So not sure if that's required13:05
brendandsil2100, there can be several landers though13:05
brendandsil2100, we already had this case that it wasn't immediately apparent who did the testing13:05
brendandsil2100, so i would really like to add that13:14
pete-woodssil2100: I think brendand is looking for there to be a log of who ran the tests (as opposed to who filled in the sheet), so we can educate "sloppy" testers13:14
brendandsil2100, that way i don't need to waste my, and another persons time, we can talk to the person directly13:14
brendandpete-woods, not even always sloppy13:15
brendandpete-woods, sometimes people are working with broken tools, poorly defined test cases etc13:16
pete-woodssure, I understand that13:16
brendandin fact there's a perfect example from yesterday where recording the result of each test would have prevented a mix up in landing an apparmor silo13:16
sil2100brendand: makes sense13:16
tedgbrendand, I have an assana ticket to add that to ci train, so the test cases get listed there.13:17
tedgSorry, ci airline13:17
brendandtedg, ah the airline13:17
tedgbrendand, Big task there is pulling the test items out of the branches and putting them in the ticket.13:17
tedgSo, I think the most important thing today is getting a common format for the tests.13:18
tedgThough, that discussion leads to flame wars more quickly than I realized :-)13:18
brendandtedg, oh i was just talking to balloons about this last night13:18
brendandtedg, oh you don't need to tell me that13:18
brendandsomething for D.C. i think13:18
tedgbrendand, And honestly, I *really* don't care about the format. I just want it to be documented and have a tool to verify I'm doing it right :-)13:19
dbarthdavmor2: could not reproduce on utopic13:20
dbarthdavmor2: do you have a pointer to that crash file? is that https://errors.ubuntu.com/problem/a6d442cbf6ce43f0fe5feaf8ee61106574d3991b ?13:20
brendandbzoltan, so what's up with that silo?13:21
brendandbzoltan, will i get to retest it any time soon (today)?13:21
davmor2dbarth: let me try and figure it out for you13:23
tedgSo is it safe to upgrade my mako to the latest image?13:26
tedgI'm a bit confused by the message of all the devices being down in the lab.13:26
ogra_tedg, OTA is fine, fresh flash isnt13:27
ogra_(you might need to re-enable developer mode via the UI though)13:28
tedgogra_, K, thanks!13:28
ogra_tedg, anouther 30min and there is a fixed image (oi hope)13:28
tedgOh, that's better :-)13:28
ogra_be my guineapig ;)13:28
tedgHaha, you may want a guineapig with a faster internet connection ;-)13:30
* ogra_ wonders if rtm 30 will ever finish its apparmor run :( 13:31
ogra_this is so awful :(13:32
ogra_3min apparmor and counting ...13:32
bzoltanbrendand:  We confirmed that the RTM silo has the same UITK what was released to  Utopic13:34
brendandbzoltan, i still can't install utopic to confirm i see the bug there. were any of your team able to check?13:35
bzoltanbrendand: I am struggling with setting up my device ...13:35
bzoltanbrendand:  zsombi said that the problem is not there on Utopic13:36
brendandbzoltan, i'd like to verify that myself - but it could be that dialer-app was updated to compensate for the change13:36
zsombibzoltan: brendand: at least not with the image I've tested with...13:37
bzoltanbrendand: sounds complicated13:37
bzoltanbrendand:  the boot time just tripled for my device13:40
jdstrandogra_: I've been thinking about how to ship cache files either as part of the click or as a separate download in the upgrade process. obviously not for rtm, but I think there is something there13:45
jdstrandI'll bring it up with my team post-rtm13:45
jdstrand(we've always said we could do that, and the work we did this cycle would support that)13:45
jdstrandthat should help developers who upgrade to the latest all the time13:46
ogra_jdstrand, but when apparmor gets updated we'll have to re-generate again13:47
ogra_which will re-introduce the issue13:47
jdstrandogra_: what I am thinking about takes that into account13:48
ogra_oh, cool13:48
ogra_yeah, thne that might work indeed13:48
jdstrandcjwatson: so, rsyslog is stuck: http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_excuses.html13:49
jdstrandrsyslog-mysql/armhf unsatisfiable Depends: dbconfig-common13:49
jdstrandoh heh13:49
jdstrandcjwatson: nm, looks like someone noticed it :)13:49
jdstrandI needed to refresh the page :)13:49
imgbot=== trainguards: IMAGE 237 DONE (finished: 20140911 13:50) ===13:49
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/237.changes ===13:49
sil2100\o/13:50
ogra_well13:50
ogra_dont party to early13:50
sil2100_o_13:51
ogra_sil2100, hmm, somehow android-tools didnt end up in rtm 1313:52
ogra_oh !13:52
ogra_my mako refuses to OTA13:53
* ogra_ looks for charger to get that working ... nice, we have a battery check now :) 13:53
* ogra_ was just heavily shocked to find the same bug ... to then notice ther version isnt the latest ... phew13:54
ogra_ok, adb comes up in 237 ... no issues13:55
ogra_tedg, safe to upgrade13:55
sil2100davmor2: are you taking care of the unity8 silo?13:57
ogra_hmm13:57
ogra_mterry, i dont get asked for the existing pin when switching to swipe in 237 (utopic)13:57
davmor2sil2100: I was I just hit issues in online accounts and the edges fix doesn't seem to of fixed anything13:58
mterryogra_, that can happen if you've recently changed password -- cached policykit authentication13:58
ogra_(settung pin and pw finally works as wexpected though :) )13:58
sil2100davmor2: oh?13:58
sil2100davmor2: damn13:58
ogra_mterry, uh, i thought pk cant cache13:58
ogra_mterry, that has always been the complaint from gksudo fans :)13:58
sil2100davmor2: btw. do you remember if the edges bug appeared on normal ubuntu as well?13:58
davmor2sil2100: never checked13:59
sil2100davmor2: since I wonder how they were fixing it, and since they mentioned it's fixed in ubuntu now I wondered if it was reproducible there as well13:59
mterryogra_, it can if you set the policy type to something like auth_admin_keep13:59
sil2100davmor2: anyway, did you make sure you have all the packages from the silo installed?13:59
ogra_ah, good to know13:59
davmor2I'm double checking that now but it's hard to tell14:00
brendandogra_, how do i recover my mako now? shouldn't power+volup boot in fastboot mode?14:01
davmor2bregma: power + vol up + vol down14:01
ogra_dunno, might be power+vol-dn or power and both vol buttons14:01
* ogra_ hast had to do that in ages14:01
davmor2brendand: even ^14:01
ogra_sil2100, do i need to dput android-tools to rtm silo 13 ?14:02
sil2100ogra_: let me check14:02
sil2100ogra_: is 4.2.2+git20130218-3ubuntu33  not up-to-date enough?14:03
ogra_sil2100, no14:03
ogra_thats the broken version14:03
sil2100ogra_: btw. is it a problem if the lxc-android-config has ~rtm appended to the version number?14:03
ogra_not for me :)14:03
sil2100ogra_: so, I can press the build button and it will fetch android-tools from ubuntu and build it, but... it will append that ~rtm bit (which I guess is not wanted every-time)14:04
ogra_i dont really care14:04
ogra_the next version will surely be higher anyway14:05
sil2100ogra_: ok, let me press14:05
sil2100Yeah, that's the point actually14:05
ogra_ubuntu33 needs to go and get bruned14:05
ogra_(that was a 4 line upstart job  change ... but somehow a wrong quilt patch ended up in the same upload ... )14:06
sil2100ogra_: ok, I think I need to handle this better... anyway, could I ask you to dput the 0ubuntu34 version to the PPA?14:08
sil2100ogra_: since I see that the ~rtm addition can be troublesome here14:08
ogra_heh, sure, np14:08
sil2100ogra_: I must add a flag 'dont add the ~rtm' to the build job :|14:08
sil2100Since for packages that we build using CI Train it makes sense14:08
ogra_what makes it troublesome ?14:08
sil2100But for others, well, my heuristics don't do the right job14:09
ogra_ah, beacuse for the +git and stuff in the version ?14:09
sil2100ogra_: yeah, you only increment the ubuntu versioning with each release here, while the sync code tries to out-smart everyone and append ~rtm to the upstream version14:10
sil2100Which was not bumped for a while14:10
sil2100(as it assumes it's bumped with every release)14:10
sil2100Well, something I have plans to improve ;p14:10
ogra_yeah14:10
ogra_and likely wont be for another looong while :)14:11
ogra_in fact we should fork it to udbd14:11
ogra_:)14:11
ogra_instead of adbd14:11
sil2100hehe14:11
ogra_there is not much left of the original code :)14:11
bzoltanogra_:  what could be the reason for the extreme long boot time? I am still on #23514:17
ogra_bzoltan, apparmor upgrade14:18
bzoltanogra_:  What should I do?14:18
ogra_it regenerates all profiles ... and does that before the screen is initialized14:18
ogra_so it sits on the bootloader screen til it finished14:18
bzoltanogra_:  In the last 2-3 hours I simple could not flash and set up for testing my mako ... random reboots, boot times like 5-10 minutes, random failing network setup ...14:20
ogra_i dont see that here14:21
ogra_i saw a 5min boot after upgrading to 237 ... but thats expected14:21
ogra_(and only happens on very first boot after OTA or flashing)14:22
bzoltanogra_:  5 minutes? good to know ...14:24
ogra_well, or 3.5, i didnt stopwatch it :)14:24
ogra_it takes very long14:24
bzoltanogra_: ohh, it does14:24
ogra_but you only get that when there were new apparmor bits usually14:25
bzoltanogra_:  I am flashing my device like 20+ times a day14:25
ogra_well, as jdstrand said above ... there are plans to improve that14:25
jdstrandbzoltan: does that device have a ton of apps on it or just the default ones?14:26
bzoltanjdstrand:  just the default14:26
jdstrandright, it won't take terribly long for just the default apps14:26
bzoltanjdstrand:  All I do is flash and set up for testing ... but today was a bad bad day14:26
jdstrandsounds like today was not apparmor-- it won't take 2-3 hours :)14:26
bzoltanjdstrand:  it takes ages ... 3-5 minutes + random reboots + netwok config does not work + click test setup does not work + whatever14:27
jdstrandalso, with default apps, we use precompiled policy14:27
jdstrandyeah, that sounds no good14:27
brendandagh what's wrong with my mako14:28
bzoltanbrendand:  welcome to the club, dude14:28
* jdstrand refrains from updating his mako14:28
brendandbzoltan, it seems dead14:28
jdstrandbzoltan: curious, are you on the rtm branch?14:29
bzoltanbrendand:  boostrap might help .. thatis what I am doing right now ...14:29
brendandbzoltan, mine is just dead14:29
bzoltanjdstrand:  no, on Utopic.. on RTM there are more  problems14:29
bzoltanbrendand:  like bricked?14:29
jdstrandhuh. mako on rtm has been 'ok' for me (annoying not responding to touch after being in my pocket bug notwithstanding). I think that may be fixed now14:29
ogra_brendand, how dead ?14:30
ogra_mine is just fine after OTA to 23714:30
* tedg is fearfully flashing 23714:32
sil2100brendand: don't scare us14:33
bzoltansil2100:  I am straggling with my mako and with the tools all day. Not kidding... a wasted day14:34
sil2100bzoltan: on 237 or 235?14:35
* tedg is now paranoid, is the ubuntu logo spinning slower than before?14:35
ogra_tedg, come on, have a little trust in my :)14:35
ogra_*me14:35
bzoltansil2100:  237 is in the queue14:36
sil2100davmor2: did you get any info from Saviq on the edges bug-fix?14:36
davmor2sil2100: no I was in a meeting14:36
* Saviq never got pubg14:36
Saviqpung14:36
tedg237 flashed and works for me. Scopes, music, etc.14:36
tedgmako14:36
bzoltansil2100:  but it is a combination of problems ... 235 become super slow to boot14:36
tedgogra_, ^14:36
ogra_tedg, adn ?14:36
ogra_err14:36
ogra_adb14:36
sil2100Saviq: so, davmor2 reported that the qtmir landing doesn't seem to fix the input bug14:36
sil2100Saviq: for ubuntu-rtm14:36
tedgogra_, Yeah, got a shell as phablet14:37
Saviqsil2100, it fixes one part of it14:37
sil2100bzoltan: ugh14:37
sil2100Saviq: oh, so it's not a complete fix then?14:37
Saviqsil2100, davmor2, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1295623/comments/2114:37
ubot5Ubuntu bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress]14:37
tedgCool, and 237 has the versions of systemd-shim and upstart that I need.14:39
* tedg does a happy dance.14:39
ogra_tedg, awesome !14:41
dobeyanyone have a good suggestion to test on rtm without having a device without rtm, and without reflashing and killing what i'm currently working on, on a device? can not the test plan and qa signoff be a single step process?14:42
brendanddobey, you mean can QA run the tests for you?14:44
dobeybrendand: right, is there an exact need for me to run the test plan and tick "yes" in that column on the spreadsheet before QA does the exact same thing?14:45
ogra_tedg, does "adb shell env" give you upstart and dbus addresses too ?14:45
ogra_thats the main purpose of the fix14:46
tedgogra_, Yes: http://pastebin.ubuntu.com/8319459/14:46
ogra_\o/14:47
ogra_no more "sudo -u phablet -i" in scripts from now on :)14:47
tedgHeh, I'm still not over automatically typing "phablet" into the sudo prompt though.14:47
sil2100davmor2: once you're around, could you comment if what you see in the silo is what is expected as per the comment Saviq made? ^14:47
davmor2sil2100, Saviq: I'm just reading it now, so I have hit both I think.  I dragged up the additional scopes and got hit by it there where the scopes screen I couldn't do any thing with at all,  the other was by the test case of holding the browser icon on the apps scope while dragging out the launcher and opening the app there too14:50
Saviqdavmor2, if you could not do anything at all (not even laucher or right edge), that sounds like either unity8 was hanging / crashing14:51
dobeybrendand: does that make sense?14:51
Saviqdavmor2, do you have steps to repro the dash overview issue?14:52
=== Ursinha changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings. Latest flash update hung all makos on s-jenkins.
sil2100brendand: do you know if we had any exploratory dogfooding made in the last few days on krillin?14:52
davmor2Saviq: no I was just running various tests for the silo and that is part of unity8 so it is tested14:52
brendanddobey, really it is the development teams responsibility to make sure their silo is tested. QA just provides a final verification. this may include running the test plan as well as additional testing14:53
davmor2Saviq: I'm currently reflashing to ensure I got everything installed from the silos and then I'll be retesting so I'll keep an eye out for it and any crashers14:53
brendanddobey, you present something to us that you believe is of sufficient quality to land, and we attempt to prove otherwise14:54
Saviqdavmor2, k thanks14:55
brendanddobey, do you have an issue with being able to run the tests?14:55
brendanddobey, overloaded device resources maybe (by what you've been saying)14:56
cjwatsondobey: is it runnable in the emulator?14:56
cjwatsonat least minimally14:56
dobeybrendand: yes, i don't have rtm on my mako, and i'm working on something else so i'd rather avoid flashing it at the moment.14:57
dobeycjwatson: probably, but i don't have an emulator set up and not quite sure how to at this point.14:58
ogra_bzoltan1, gah, the spreadheet cheated me (i edited one line above your line 25 and after "enter" it jumped into your field) i might have set your "testing pass" wrongly now14:58
brendanddobey, can someone else test?14:58
dobeybrendand: that's what i'm asking :)14:58
brendanddobey, apart from us :)14:58
ogra_davmor2, have fun with silo 13 ;)14:58
cjwatsondobey: https://wiki.ubuntu.com/Touch/Emulator14:59
cjwatsonarmhf is dog slow, --arch=i386 was at least somewhat reasonably fast last I tried14:59
davmor2ogra_: not touching it I'm having enough fun with 10 and 1714:59
ogra_heh, k14:59
dobeyyeah, i did armhf once a long long time ago, and it was completely unusable for me15:00
dobeywould be neat if --arch=amd64 worked...15:01
davmor2dobey: you want to ditch those crappy low powered machines you have for work and buy a beast it works really slowly then instead of not at all ;)15:02
dobeydavmor2: if a core i7 with 16 GB RAM is "low powered" then something is seriously wrong with the world15:03
brendanddobey, --arch=i386 will still work on amd6415:03
davmor2dobey: that was my point ;)15:03
brendanddobey, to some degree of 'work'15:03
dobeybrendand: sure15:03
dobeyooh. 14MB/s from the image server. nice15:05
bzoltanogra_:  you accidentally flipped that tested switch just 3 minutes after the silo actually passed the tests. You have magic power. Do you want to join the SDK team? :D15:10
ogra_lol15:11
brendandbzoltan, zsombi - bad luck - i have the bug in utopic too. you are getting booged :P15:18
brendandbzoltan, dunno how zsombi didn't see it15:19
sil2100brendand: what's up?15:21
dobeyok, emulator is not working so great. mouse clicking doesn't work so great, and typing correctly in the emulator is pretty well impossible :-/15:21
sil2100davmor2: so, what's the state of QA sign-off of the unity8 silo? Is it really broken and -1?15:22
brendandsil2100, you wanted me to do something earlier right? i never heard from you :)15:22
sil2100brendand: yeah, wanted to have some test results for 237 first through, but it seems to proceed slowly - anyway, did we have any exploratory testing for krillin images this week?15:24
bzoltanbrendand: have you removed the ~phablet/autopilot/ubuntuuitoolkit ?15:26
brendandsil2100, i've only been on silos, davmor2 would know better15:26
sil2100davmor2: pong15:26
brendandbzoltan, it's nothing to do with autopilot15:26
brendandbzoltan, https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/136829515:26
ubot5Ubuntu bug 1368295 in ubuntu-ui-toolkit (Ubuntu) "latest UI toolkit causes visual glitch in Recent tab of dialer-app" [Undecided,New]15:26
davmor2sil2100: nothing yet15:26
sil2100davmor2: did you do any exploratory tests this week?15:27
brendandbzoltan, i haven't run any AP tests15:27
=== robru changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Latest flash update hung all makos on s-jenkins.
bfillersil2100: if I want to just sync a package from ubuntu to ubuntu-rtm, how do I enter that in the sheet?15:27
davmor2sil2100: no as there was no image to consider.15:27
brendandbzoltan, although i found it because of the dialer-app AP tests15:27
bzoltanbrendand:  ohh ... in that case you caught me :) thanks for the bug15:27
sil2100davmor2: I thought we're doing exploratory testing per-image, at least per selected images every now and then :)15:27
bzoltanbrendand: why on earth it did not show on my tests -> http://people.canonical.com/~bzoltan/ap-2014_09_10-19_29_44/ap-2014_09_10-19_29_44-dialer_app-1.tests15:28
davmor2sil2100: om26er_ has been testing image on mako from utopic and rtm while everyone else has been concentrating on silos15:28
brendandbzoltan, the dialer-app tests aren't that complete15:29
sil2100Ok15:29
sil2100om26er_: hey!15:29
brendandbzoltan, there is no test to check that15:29
bzoltanbrendand:  okey.. good to know15:29
brendandbzoltan, i only noticed it because i watched the test run15:29
sil2100om26er_: how does the ubuntu-rtm situation look like for mako?15:29
bzoltanbrendand:  ahh.. watching the tests? That is so 80's15:29
* sil2100 hopes for it to be at least some approximation of how things look15:29
brendandbzoltan, should i deliberately look away :P15:30
davmor2sil2100: broken I can tell you that ;)15:30
bzoltanbrendand:  :D depends on your wallpaper15:30
brendandbzoltan, but the version in the silo is right and i can continue testing?15:30
sil2100davmor2: but but..!15:30
sil2100davmor2: it can't be THAT broken, right?15:31
bzoltanbrendand:  yes, that is confirmed ... the silo has exactly the same as Utopic15:31
davmor2sil2100: don't make me list the ways we get told off for spamming the channels :P15:31
brendandbzoltan, so i'll finish testing and see if there are any more issues. you may as well fix them all at once15:32
om26er_sil2100, davmor2 i am testing utopic today15:33
davmor2om26er_: how was rtm yesterday then?15:34
bzoltanbrendand:  if you see the same problem with the clock and the messaging app then it  is a clear UITK bug, if not than the app does something funny15:35
om26er_davmor2, the manual plan succeeded15:35
om26er_davmor2, it was fine15:35
brendandbzoltan, i don't agree with that15:36
brendandbzoltan, they are not going to be using the same code15:36
bzoltanbrendand:  we fix it regardless of anything15:36
brendandbzoltan, even if slightly similar15:36
brendandbzoltan, well the fix may be in dialer-app, but your silo caused the regression so you need to investigate15:37
bzoltanbzoltan:  No question about that.15:37
brendandbzoltan, messaging and clock seem fine15:38
bzoltanbrendand:  Good to know.15:38
bzoltanbrendand:  i do not promise fix over night, but tomorrow it will be nailed down15:39
bfillersil2100: can I have a silo for line 57 when you have a chance please?15:42
sil2100bfiller: hey! Sure, one moment, let me see if it's possible15:42
alecuhi trainguards: both installation of new apps and uninstallation seem to be broken on #23715:42
alecuis that known?15:43
=== alecu is now known as PyAr
=== PyAr is now known as alecu
sil2100bfiller: oh, but you already seem to have a sync silo for ubuntu-keyboard15:46
bfillersil2100: I didn't see it, which one?15:47
sil2100bfiller: I see silo 11 is already assigned with ubuntu-keyboard and syncing from ubuntu/utopic15:47
brendandalecu, what error do you get?15:47
bfillersil2100: ah ok15:48
bfillersil2100: does the sync silo need to get rebuilt if the original silo was reconfigured with additional MR's or does that happen automatically? I just want to make sure what's in the sync silo matches what was released in the ubuntu silo yesterday15:49
alecubrendand: no error during uninstallation, and the error cannot be seen on installations; I'm enabling debugging now to see if I get some more info15:50
bfillersil2100: nm, it looks correct15:50
sil2100bfiller: it's targetting ubuntu now, so if you press build (and mention 'ubuntu-keyboard') then you'll double-check if it's up-to-date there15:50
brendandalecu, yeah i confirm that on utopic. unfortunate15:53
ogra_sil2100, i'll be a minute late15:59
ogra_(or two)15:59
alecutrainguards, I think pkcon is broken in image #237, was there any landing for click? (not the scope, but click itself)16:04
alecucjwatson: mvo_ ^16:04
alecuphablet@ubuntu-phablet:~/.cache/upstart$ pkcon -p remove "com.ubuntu.developer.webapps.webapp-amazon;1.0.9;all;local:click"16:05
alecuFailed to contact PackageKit: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PackageKit timed out16:05
cjwatsonclick was landed recently-ish but the packagekit plugin wasn't changed16:05
cjwatsonpackagekit was changed in rtm at the same time to add an option to packagekit; but that upload had been in devel-proposed for a while16:06
alecuit's the same when trying to install any click:16:06
cjwatsonthe click change was in 23516:06
cjwatsonalecu: what log file would I expect to see this in when installing from the scope?16:09
alecucjwatson: it should be in .cache/upstart/scope-registry.log, but it seems to only be logged after setting the click scope to debugging mode via an env var.16:11
Mirvbzoltan: MP:s not approved https://ci-train.ubuntu.com/job/ubuntu-landing-003-2-publish/17/console16:11
alecucjwatson: anyway, it's easy to see by running the commands via phablet-shell16:11
cjwatsonalecu: yeah, does udm leave the downloaded click packages anywhere?16:12
cjwatsonso I don't have to scrabble about for one16:12
alecucjwatson: since pkcon is returning zero, udm is deleting the files; I'll send some clicks your way16:12
alecucjwatson: but you can also see it when trying to uninstall:16:13
alecucjwatson: http://pastebin.ubuntu.com/8320061/16:13
cjwatsonright.  this doesn't really feel like click breakage, I suspect something wrong with packagekit/policykit/something, but what ...16:15
alecusounds reasonable16:16
cjwatsonstricter permissions somewhere?16:16
cjwatsonwondering if it could be fallout from the developer mode stuff16:16
Mirvsil2100: hey. consider running https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-2-publish/build?delay=0sec forced, after checking that yes indeed the landing seems to be already in rtm, somehow weirdly still in the dashboard but not in the spreadsheet16:17
cjwatsonguess I could strace dbus and see what it's doing16:17
cjwatsonit's executing packagekitd, at least16:22
cjwatsonwhich dies quickly16:23
alecucjwatson: when doing a dbus call like this, dbus activation will start the process and then wait for it to expose the dbus interface that's being called.16:23
cjwatsonyeah I know16:24
alecuso, it must die before exposing the interface, because I don't see packagekitd running16:24
cjwatson6512  16:23:32.190353 write(1, "Failed to load the backend: opening module aptcc failed : /usr/lib/arm-linux-gnueabihf/packagekit-backend/libpk_backend_aptcc.so: undefined symbol: forkpty", 155) = 15516:25
cjwatsonThat's novel16:25
sergiusenscan I get a silo for line 54?16:25
cjwatsonlibpk_backend_aptcc.so doesn't link against libutil16:26
alecushould I assign the bug to packagekit? https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/136824616:28
ubot5Ubuntu bug 1368246 in unity-scope-click (Ubuntu) "Installation of Apps not functioning" [Critical,Invalid]16:28
cjwatsonyes please, I'm still investigating but the missing linkage is a smoking gun16:28
cjwatsonthe question is how it ever worked16:29
cjwatsonalecu: do you have a confirmed image number where it previously worked?16:29
alecucjwatson: I think it worked on #236; I can reflash and check16:30
cjwatsonalecu: would be useful to know, thanks.  I'll fix it in parallel though16:30
dbarthseb128: ping? qq did you unblock the uss location silo btw? i see it is still mentioned as "after silo 15" or so16:32
seb128dbarth, yeah, not sure but I think those changes landed in rtm, since we synced u-s-s from utopic16:33
dbarthso the line can be killed?16:33
dbarthi'll double the bug is gone while testing something else16:34
dbarthdouble check16:34
seb128yes, I think so16:35
AlbertA2jibel: on ubuntu-rtm/landing-001 QA testing.... automated CI testing has already ran...no need to worry about that...16:41
cjwatsonalecu: building a candidate fix on the porter box now16:41
alecugreat16:42
jibelAlbertA2, are the results published somewhere?16:43
AlbertA2kgunn: camako: ^16:43
camakoAlbertA, if you go to the build page, you can find the build artifacts.. CI testing should be one of them16:47
cjwatsonalecu: any luck?16:48
AlbertA2camako: ok16:50
AlbertA2jibel: https://launchpadlibrarian.net/184437882/buildlog_ubuntu-rtm-14.09-armhf.mir_0.7.1%2B14.10.20140909.1~rtm-0ubuntu1_UPLOADING.txt.gz16:50
dobeyalecu, cjwatson: i can definitely confirm that pkcon install-local worked on 235 on mako, since i did it plenty (but it did require me to do --allow-untrusted)16:51
cjwatsonthe latter's expected now, yes16:52
alecucjwatson: it's dog slow to download images here... still 75% of 236.16:52
cjwatsonI think apt innocently dropped -lutil for some other reason and this exposed a latent packagekit bug16:52
AlbertA2jibel: and for ubuntu-rtm/landing-005, to answer the question posted - the fix touches code that is also used in krillin hence why it must be tested for krillin too...16:53
cjwatsonbut I'm trying to find the actual change to make sure16:53
cjwatsongot it, http://anonscm.debian.org/cgit/apt/apt.git/commit/?id=223ae57d468fdcac451209a095047a07a569821216:56
cjwatsonno longer references openpty so the linker drops the -lutil linkage16:57
cjwatsonmakes sense now16:57
bzoltanogra_: nice ... phablet-network says "Error: No Wi-Fi device found."17:03
dbarthseb128: image 33 contains the fixes; i'll suppress the line now17:07
cjwatsonalecu: fix uploaded.  doesn't affect rtm since it has an older apt.17:07
cjwatsonhave to run to dinner now17:07
cjwatsonthanks for the heads-up17:07
cjwatsonalso https://github.com/hughsie/PackageKit/pull/1117:07
alecugreat, thanks!17:09
alecubtw, probably no longer needed, but I just confirmed that 236 was broken17:09
cjwatsonalecu: right, the apt change landed in 23617:10
fgintherrobru, are you online today?17:11
robrufginther: I am, what's up?17:11
cjwatsonsil2100,robru: heads-up for the above conversation between alecu and me; doesn't affect RTM; I suggest building a new devel-proposed image once "rmadison -s utopic packagekit" says 0.8.17-4ubuntu317:11
loolHey trainguards; we've fixed the main issue with the positioning engine for location-service; would like to land the changes now; it's probably location-service branch + lxc-android-config upload17:16
loolin utopic for now17:16
loolMay I take row 57?17:16
sil2100robru: ^ ? :)17:17
robruhey hey17:18
loolsil2100: for native pkgs, am I supposed to use regular version numbers in silo, and the source + bins get copied to Ubuntu17:18
loolI've listed stuff on line 57; waiting for silo17:19
davmor2sil2100: hey so dbarth has managed to reproduce the bug and it looks like there is a temporary work around we can use for evernote account creation.  So I am going to let dbarth file the bug as I'm sure he can add more detail and then carry on testing silos 10 and 1717:20
davmor2and see if we can't get them landed17:21
dbarth+1 bug filed17:22
dbarthand nice catch davmor2, legendary bug-finding-fu :)17:23
ogra_yeah ... long term he will own launchpad :)17:23
ogra_karma: 398623159085610385617:23
davmor2ogra_: haha17:24
loolrobru: is that enough to assign a silo?17:30
loolheya, if you have a minute, lp:~phablet/ubuntu-location-provider-here/trunk didn't autoland the last MP; I merged it by hand, would you know what's preventing this?17:31
sil2100lool: robru will be your guide, but in overall it's usually tricky when native packages are related - usually it's best to use a rule of the thumb: if you see that the given package doesn't impact RTM much and is safe to do a bin copy, then a binary copy should be fine17:33
sil2100robru: btw. I'm merging some fixes to the sync thing - if you notice any additional issues, please feel free to revert that17:34
davmor2ogra_: actually my karma stays around 1650-1700 because I mostly just file bugs you don't get much karma for find them only fixing them :D17:36
loolsil2100: okay; thanks!17:42
robrusil2100: ok17:45
robrulool: one sec17:46
robrulool: why does it say "WIP" under merge proposals?17:46
loolrobru: we will submit an updated merge proposal (I have one here, but I'm not 100% sure it's the one we want to send)17:48
loolrobru: should I leave this empty until we have the final one? (in an hour or so)17:48
robrulool: It's not clear to me what you're trying to accomplish with this landing request. why would I give you a silo with no MPs? it's certainly not valid to write 'WIP' in the MP field.17:50
loolrobru: I'd like to land lxc-android-config there, then let thomas list his mp17:51
robrulool: also, what's the deal with lxc? you said sync: but the landing is for utopic. That makes no sense. sync means "sync from utopic to rtm". so sync only makes sense in the context of an rtm silo17:51
robruok17:51
loolok; I thought was for sync out of the silo into archive17:51
looland had to be listed when you were uploading sources17:52
robrulool: you have to list sources when you're uploading sources. The 'sync:' syntax is just for RTM.17:52
robrulool: so I fixed your request and got you silo 2. you can upload lxc in there now17:53
loolrobru: yup, understood now17:53
robrusil2100: hey what happened with your latest branch on cu2d?18:11
robrusil2100: like, it merged with test failures.18:13
robruhmmm18:13
sil2100robru: uh?18:25
sil2100robru: strange, I didn't touch that places at all18:25
sil2100robru: as you can see it's nothing in my branch18:26
Ursinhasometimes tests fail because of unintended side effects :) (I don't know what is the case here)18:28
robrusil2100: what I can see is that you changed the build job xml template, which I happen to have a test against (I wrote a test that confirms the new string.format templating works, and it happens to check the exact results of loading build.xml.tmpl, which your commit changes the result of ;-)18:29
robrusil2100: not sure how that managed to land on trunk, working with Ursinha to prevent that from happening again, but also I'm changing that test to just check for the important bits of build.xml without being so flaky about unimportant changes there18:30
bfillerrobru: silo 15 can be published again, all MR's are now approved18:30
robrubfiller: ok published, you're now building in rtm12 https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-012-1-build/12/console18:33
bfillerrobru: ty18:33
sil2100robru: it landed?18:33
robrusil2100: yeah your branch is in trunk18:33
sil2100robru: that's confusing - https://code.launchpad.net/~sil2100/cupstream2distro/cu2d-syncfixes/+merge/234346 <- says it's not merged yet18:34
tvosssil2100, hey :) welcome back18:35
tvosssil2100, got a question for line 9 in the spreadsheet18:35
Ursinhasil2100: that branch was changed from Merged to Needs Review, I think (if that's what you're using to infer that)18:35
sil2100tvoss: hey!18:35
sil2100Ursinha: that might be the case here, strange thing as the autolander said it failed as well ;)18:36
sil2100tvoss: what's up?18:36
robrusil2100: yeah, so what happened was that you probably marked the branch approved, so the -autolanding job came in and said "oh, it's approved, lets merge that to trunk, ok now that it's merged I'll run the tests again just to be safe. ooops, test failure! reject! needs fixing!" but it's in trunk already...18:36
tvosssil2100, so line 8 landed in utopic, have a hard time making sense of line 918:36
Ursinhasil2100: apparently that's not considering the test result to proceed with the merging, we're working on it18:36
robrusil2100: anyway don't worry about your code branch, I have some other refactoring going on, I merged it into the work I'm doing.18:37
Ursinhawell, fginther mostly as he's the man who knows the stuff, I watch and learn18:37
sil2100tvoss: it seems it's failing to build, hmm18:37
sil2100Ursinha, robru: thanks ;)18:37
robrusil2100: you're welcome!18:37
tvosssil2100, ah, got it18:38
sergiusensrobru: hey, I have a line request since 8am and I don't see lack of silos being an issue19:19
sergiusensand now I also added line 5919:19
bzoltanToyKeeper:  I finally managed to provision  my mako for RTM testing. It was everything but easy. No I started to run the tests, but I already see that tests crash without much reason and without any result19:22
ToyKeeperbzoltan: Sorry, I'm missing a little context.  Didn't you already have a mako set up for that?  The one which tested UITK on image mako-rtm 32?19:26
bzoltanToyKeeper:  we agreed with brendand to run the tests again, because we have found a visual problem what was not discovered by the AP tests. https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/136829519:27
bzoltanToyKeeper:  and so i started to provision my device and it failed big time...19:28
bzoltanToyKeeper:  it is not going to be a joyride ... something is wrong19:29
ToyKeeperbzoltan: I heard about the dialer-app bug, but what's wrong with provisioning?  Did mako's feed hit a bump today?19:30
ToyKeeperI've gotten a little out of touch since I spend all my time on krillin these days.19:30
bzoltanToyKeeper:  the dialer app thing is a minor problem, we will fix it tomorrow19:30
bzoltanToyKeeper: My mako is just unstabe, or the tools are unstable...no idea19:31
bzoltanToyKeeper:  as start the boot time went up to 6 minutes from 1, as second the phablet-network is unreliable or the network service is unreliable. phablet-network fails or the device does not connect to the wlan after reboot19:32
bzoltanToyKeeper:  it reboots randomly for hack knows what reason...19:33
ToyKeeperOh, hmm.  I've never used phablet-network.  Seemed irrelevant since I'm not using network-manager.19:33
bzoltanToyKeeper:  One Ubuntu release (236) had no adb support19:34
ToyKeeperNo adb is definitely a big problem.19:34
bzoltanToyKeeper:  phablet-network could be important if you script the process19:34
ToyKeeperbzoltan: No, no need: adb shell nmcli d wifi connect APNAME password APPASSWD iface wlan019:35
bzoltanToyKeeper:  Well... that is something I will not ever put in a script :) for obvious reasons ...19:36
bzoltanToyKeeper:  but it is a good fallback solution19:37
ToyKeeperJust put the private details in ~/.private/wap_info or something, and source it in the script.  No need to publish the details on launchpad.19:38
bzoltanToyKeeper:  I make this script for the whole SDK team... it should be simple. I expect the phablet-network to work. It is a tool from the ubuntu archive.19:39
bzoltanToyKeeper:  but that is not the only troublemaker ... more scary that AP tests simple crash19:40
ToyKeeperI've been trying to use NetworkManager for almost a decade, and have never gotten it to function reliably on a notebook, so I use something else.  phablet-network is a neat idea, but it relies on NM so I can't use it.19:40
bzoltanToyKeeper:  I am using nm for almost 3 years without problem. I am lucky :) But I am not sure that the problem here is the nm ... the wlan0 interface just disappears sometimes from the device19:42
ToyKeeperThat would definitely be an issue.19:42
sil2100o/19:43
ToyKeeperAs for tests failing, I found that several test suites had high failures rates...  49/51 failed on unity8, 7/7 failed on calendar_app, 17/17 failed on music_app, 13-29/41 failed on gallery_app.19:44
bzoltanToyKeeper:  It is soon 11pm here, so I give it up for today...19:44
ToyKeeperonline_accounts_ui didn't even run (found 0 tests).19:44
bzoltanToyKeeper:  not failing .. _crashing_19:44
ToyKeeperIn any case, it sounds like I should avoid updating mako for a while, since I'm not actively involved in fixing whatever just failed.19:45
bzoltanToyKeeper: LOL ... my mako has a wlan12 interface19:46
slangasekcan anybody explain to me what I'm doing wrong here?:19:49
slangasek~ ~/bin/ubuntu-emulator create --arch=i386 --channel=ubuntu-touch/ubuntu-rtm/14.09 rtm19:49
slangasekFailed to locate latest image information19:49
bzoltanToyKeeper: brendand: I stop the RTM silo9 UITK validation. I give it an 8 hours rest and try again in the morning :)19:49
bfillerrobru: need silos for line 55 and 60 when you have time19:50
robrubfiller: line 55 is missing target distro (column H)19:52
bfillerrobru: fixed19:53
bzoltanslangasek:  are you sure that there is an i386 build of the RTM?19:53
robrubfiller: thanks. hm, seems there are 0 rtm silos available... i'll see if I can free one up19:53
slangasekbzoltan: well, apparently there isn't - the channel exists and is empty!19:53
slangasekbzoltan: thanks, I was just about to check that19:54
bzoltanslangasek:  it would be cool to have an RTM emulator19:54
robrubfiller: you got utopic10 at least19:54
bfillerrobru: thanks, silo 11 and 12 in rtm are good to be published19:54
slangasekbzoltan: yes, I would say it should have been a baseline requirement ;)19:54
slangaseklet me fix that19:54
bzoltanslangasek:  :) go for it19:55
=== ken__ is now known as kenvandine
slangasekoh, it's because I wasn't using -proposed and we don't have any promoted images yet :(19:56
robrubrendand: ToyKeeper: mandel: what's going on with silo rtm-6? it's been awaiting signoff since august 29th... would be nice to get that either approved or rejected so we can reclaim the silo.19:57
robruelopio: ^19:58
elopiorobru: last comment from rvr: According to mandel, this was working with previous images, but something else must be changed that prevents the location-service to work as expected. They are looking into that and will ping us when ready.19:58
elopioI'm not sure if the process is to wait for the developer, or to reject it so the silo can be reused.19:59
brendandrobru, august 29th?20:01
brendandrobru, it wasn't set to QA sign-off until tuesday20:02
robrubrendand: well the packages in the ppa were built on the 29th.20:04
robruelopio: not a hard rule there... we're out of silos so I'm looking for ones to free. don't want to screw them if they're actively working on it, it just happened to look very stale an inactive based on simple heuristics...20:04
elopiorobru: that comment is from this morning, so I would hope mandel to get back to us tomorrow. It would be nice if he can keep the silo, but if you need it I guess he'll also understand.20:06
brendandrobru, you probably want to ask mandel why it took him a week and a half to test it20:09
cjwatsoncan I build a new devel-proposed image so that click package installation works again?20:09
cjwatsonor are we just going to wait for cron?20:09
brendandrobru, 18 has been sitting around since the beginning of the week as well20:12
brendandrobru, and 3 seems to be having some trouble20:14
Saviqfginther, hey, could you please delete https://code.launchpad.net/~ps-jenkins/unity8/ubuntu-utopic-proposed20:14
robrubrendand: wait what's happening in 3? was it published?20:15
Saviqfginther, or at least run http://people.canonical.com/~msawicz/unity8/strip-u8-tags.py on it20:15
brendandrobru, it was signed off20:15
brendandor maybe not20:15
robrubrendand: signed off or not, rtm has what's in that silo! ;-)20:16
robrufreeing it...20:16
brendandrobru, i suppose it was classed as 'bugfix only'20:16
fgintherSaviq, I can delete that20:16
Saviqfginther, I know you can, you're the only one ;)20:17
fgintherSaviq, done20:18
Saviqfginther, thans20:19
Saviqk20:19
* Saviq needs to get used to using more force20:19
cjwatsonok, I guess nobody really objects; image build requested, will run shortly20:19
robruWarning: I am about to deploy a massive overhaul to ci train. It may shoot deadly beams into your eyes and then explode, so get your safety goggles ready.20:24
imgbot=== trainguards: IMAGE 238 building (started: 20140911 20:25) ===20:24
robrubfiller: you got silo rtm3 for your font sync, and congrats on being the 2000th landing in citrain ;-) https://ci-train.ubuntu.com/job/prepare-silo/2000/console20:29
kenvandinerobru, did you break the spreadsheet?20:31
kenvandine:-D20:31
kenvandinecolumn C is broken20:31
robrukenvandine: yeah I broke something...20:31
kenvandineok, i need to reconfigure... but the train got angry20:32
robrukenvandine: actually I think the spreadsheet might have just crapped on itself... I was only tinkering with jenkins20:32
kenvandinedamn spreadsheets :)20:33
kenvandineseb128, ^^^ that'll hold up getting that other fix in there20:34
seb128kenvandine, k20:34
robrubfiller: https://launchpad.net/ubuntu/+source/ttf-ancient-fonts-symbola this package name you're trying to sync doesn't seem to exist20:41
robrukenvandine: ok sorry was putting out a different fire. what's up with your thing?20:44
robrukenvandine: which row / silo?20:44
kenvandinerobru, row 6120:45
kenvandineit's building in silo 420:45
kenvandineit won't let me reconfigure it because the spreadsheet doesn't know it's in a silo20:45
kenvandinerobru, and scrolling up i see some older ones with no status that are already checked as tests passed and qa verified20:47
kenvandineprobably already landed, but no status20:48
robruhm20:51
kenvandinerobru, thanks, can i reconfigure now?20:52
robrukenvandine: already did ;-)20:53
kenvandinethx :)20:53
kenvandinerobru, did you kick a new build?20:53
* kenvandine will if not20:53
robrukenvandine: oh, nope20:54
kenvandineok, good20:55
kenvandinei'm doing it20:55
robrukenvandine: which ones in the spreadsheet did you say looked like they'd been landed but had wrong status?21:00
robrufound a couple in silos missing their status, wasn't sure what landed.21:00
kenvandinerobru, 4121:02
kenvandineshows testing passed...21:02
kenvandineso must have been built21:02
kenvandineline 33 too21:03
kenvandineoh... you're finding them :)21:03
ralsinatrainguards, I swear line 43 has already landed :-)21:04
kenvandineralsina, QA even tested it21:05
ralsinayep :-)21:05
kenvandineralsina, robru: so it was in a silo at least21:05
ralsinait was in rtm-821:05
ralsina[17:34:48] [queuebot] Silos: ubuntu-rtm/landing-008 (ralsina) Landed. Cleaning silo. (account-polld, ubuntu-push)21:05
ralsinathat's 30 minutes ago21:06
robruyeah the spreadsheet is messed, sigh21:08
ToyKeeperrobru: Er, what?  Silo rtm-6 is that old?  I see an archived card for it which was marked as "pass" on Aug 26, then a new card for the same silo number which was created today.22:04
imgbot=== trainguards: IMAGE 238 DONE (finished: 20140911 22:05) ===22:04
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/238.changes ===22:04
robruToyKeeper: yup it's just been sitting there since the 29th as far as I can see22:05
ToyKeeperrobru: The latest status I see on the card is from a few hours ago.  "Victor wrote: According to mandel, this was working with previous images, but something else must be changed that prevents the location-service to work as expected. They are looking into that and will ping us when ready."22:05
ToyKeeperrobru: I see this in the IRC log, which I think is when the card got created: 2014-09-08 08:37:56 -queuebottrainguards, ubuntu-rtm/landing-006: Packages built. Testing pass. QA needs to sign off.22:07
ToyKeeperBefore that, the previous event was at 2014-08-29 06:45:0422:07
ToyKeeperI'm guessing the 08-29 event probably got missed by the auto-card-creator (was buggy at the time) and not noticed by any humans (who thought the bot was functional).22:08
robruhmm22:08
ToyKeeperIn any case, it got lots of attention today and is apparently waiting on upstream fixes.22:09
robruToyKeeper: no worries now, three other silos freed up, so no pressure to free that one. just curious that it's been around so long22:09
ToyKeeperI don't really know the story; this is just what I could dig up.22:09
robruToyKeeper: no worries, thanks22:13
=== ondra- is now known as ondra

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