#ubuntu-ci-eng 2014-04-01 <robru> sergiusens, sure <robru> kgunn, oh ok <robru> kgunn, ok you got silo 5 <robru> sergiusens, you got silo 10 <sergiusens> thanks <sergiusens> tools always get 10 <robru> hehe, luck of the draw! <kgunn> robru: thank you sir <robru> you are both welcome. sorry for the delay there I was afk <sergiusens> slangasek: hey, there's a merge conflict with your MRs; I'm guessing it's the changelog; do you want me to merge separately or in one stance? if you remove the changes from debian/changelog the train will generate one from the commit message set on the MR/MP <slangasek> sergiusens: it is the changelog; happy to have the changelog entries removed to make the merge work; what's the best way forward? <slangasek> sergiusens: they certainly don't need to be separate merges, so whatever's best to fix up the merge, let's do it <sergiusens> slangasek: just revert them <slangasek> sergiusens: updated lp:~vorlon/phablet-tools/sane-adb-shells/ with changelog dropped - is that enough, or should I be dropping both changelog entries? <sergiusens> slangasek: drop both, or you'll only get that one entry <slangasek> phooey ;) <slangasek> sergiusens: done <sergiusens> thanks, building now <cwayne_> cihelp ping <cjohnston> cwayne_: that's not very helpful... <cwayne_> cjohnston, having some issues with the jenkins job http://s-jenkins.ubuntu-ci:8080/job/savilerow-trusty/25/console, seems its not actually pulling the latest rev somehow <cwayne_> as in, it's missing some files in the tarball that i know are in the branch.. <cjohnston> cwayne_: "revno:6" <cwayne_> cjohnston, right but it's missing the entire src/system/custom/lib dir <cwayne_> which is there if a do a fresh branch <cjohnston> cwayne_: seems like "tar Jcvf custom.tar.xz -C src/ system/" may be an issue <cjohnston> to me (not knowing anything about whats going on), it doesn't look like there would be a src/ and system/ <cwayne_> it's making the tarball itself fine though, it's just missing src/system/custom/lib <cwayne_> it's got src/system/custom/everything-else <cjohnston> cwayne_: is there a problem running it manually? <cwayne_> cjohnston, nope <cwayne_> just now ran it on a fresh branch <fginther> cjohnston, cwayne_, any chance someone did a push --overwrite on this? <cjohnston> fginther: it the branch seems to have it <cjohnston> + ls src/system/ <cjohnston> custom <cjohnston> ahh, I see what your saying.. <fginther> care if I retry a build after wiping the workspace? <cjohnston> +1 <imgbot> === trainguard: IMAGE 271 building (started: 20140401 02:05) === <fginther> cwayne_, any harm in trying a clean rebuild? <cwayne_> fginther, none at all <fginther> nice, jenkins throws an exception trying to delete /home/ubuntu/jenkins/workspace/savilerow-trusty/src/system/custom/click/com.ubuntu.developer.alecu.qr-code/current. I'll check the host <fginther> cwayne_, the console looks like it found lib this time <cwayne_> fginther, awesome, thanks! <cwayne_> must've been a push --overwrite or something weird <fginther> cjohnston, cwayne_ 'current' was a symlink. I've seen a few jenkins bugs related to issues with symlinks <cwayne_> ah, could be <cwayne_> could we setup this job to always do a fresh branch? <cjohnston> seems like the job should only be firing when there is a code change <fginther> cwayne_, that might work, or the job may have to do some cleanup before it finishes <fginther> cwayne_, the job does a poll of the bzr tree, if the workspace is left in a bad state, the pollling may not go well <cwayne_> fginther, yeah, that makes sense <cwayne_> i can try and add some cleanup <cwayne_> thanks for the help fginther <fginther> and he leaves <fginther> cjohnston, /me thinks cwayne should be introduced to the jenkins charm <cjohnston> hehe <sergiusens> doanac: hey, care to run the andy job against https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=28 ? <imgbot> === trainguard: IMAGE 271 DONE (finished: 20140401 03:35) === <imgbot> === changelog: http://people.canonical.com/~ogra/touch-image-stats/271.changes === <Mirv> morning <Mirv> didrocks: bzoltan1 has set uitk to be tested but it'd need a packaging ack: http://502.619.2016/job/landing-018-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-ui-toolkit_0.1.46+14.04.20140331-0ubuntu1.diff <didrocks> Mirv: good to me, +1 :) <Mirv> thanks <Mirv> bzoltan1: re: your notes from other channel, this is your last chance to discuss if there's still some doubt on your mind :) <Mirv> apparently sdk team has found a flakiness happening in clock app tests that shouldn't be coming from UITK, and sometimes all tests pass <Mirv> but I guess the confusion was about why it's not flaky on the test infra or something <bzoltan1> Mirv: correct <bzoltan1> Mirv: the only flaky test is the ubuntu_clock_app.tests.test_stopwatch.TestStopwatch.test_click_clock_center_with_stopwatch_started_must_stop_it and the ubuntu_clock_app.tests.test_timer.TestTimer.test_delete_preset_must_remove_from_presets_list <bzoltan1> Mirv: that means, that 2 out of 8 run failed ... <bzoltan1> Mirv: http://paste.ubuntu.com/7187031/ http://paste.ubuntu.com/7187032/ <Mirv> bzoltan1: ok. I guess we can assume at this point, especially as your people have studied it quite a lot, that it shoudn't be coming from UITK <didrocks> bzoltan1: this test was never flaky beforehand, did you work with QA? <bzoltan1> Mirv: I really do not think it has anything to do with the UITK <didrocks> Mirv: we didn't have those testing failing over 20 runs <bzoltan1> didrocks: Mirv: we worked with elopio <didrocks> Mirv: so I think we should reallly have jibel's team expertise first <bzoltan1> didrocks: I am not happy with that .. .but not landing the UITK will cause bigger issues soon <Mirv> bzoltan1: what did elopio have to say? <didrocks> bzoltan1: yeah, so then, you put the pain in the CI team to get the things fixed? <bzoltan1> didrocks: Mirv: elopio said that he has been running clock tests on his mako with image 270 and the 18 silo ppa for one hour with no failures like 12 times <didrocks> cihelp: seems that the tests don't unlock the screens? <Mirv> didrocks: it'd be good to understand as much as possible. I know I can't replicate test infra results myself, for example yesterday notes-app failed for me consistently but ok on test infra. <bzoltan1> didrocks: Mirv ^^ <didrocks> bzoltan1: with your new UITK? <Mirv> yes, silo 18 is the new UITK <bzoltan1> with image 270 and the 18 silo ppa <Mirv> bzoltan1: that sounds good at least <didrocks> bzoltan1: ah, so this is good to me <bzoltan1> Mirv: yes it does ... but I hate to see different test results than the dashboard shows <bzoltan1> didrocks: I am confident, but I would like to see what the CI's dashboard shows <Mirv> bzoltan1: so maybe a mental note to ask from elopio how he runs the tests, to try to get as good results in the future? <Mirv> bzoltan1: that'll come with CI Airlines only unfortunately, getting the test infra to do the current manual work.. <bzoltan1> Mirv: That is what I will do when elopio comes online <didrocks> bzoltan1: like, if only you got it, someone else rerun it multiple times without getting it, knowing how hard and subtle flaky issues we can have, yeah, that's fine <didrocks> plars: no email on the phone ML where #270 failed completely? <Mirv> ok, but 12 times no failures from elopio is good enough, and I already know no other failures were found <didrocks> soâ¦ I was tellingâ¦ <didrocks> bzoltan1: ah, so this is good to me <didrocks> bzoltan1: like, if only you got it, someone else rerun it multiple times without getting it, knowing how hard and subtle flaky <didrocks> issues we can have, yeah, that's fine <didrocks> plars: no email on the phone ML where #270 failed completely? <didrocks> did you get my messages? <Mirv> depending on who you're asking from, yes I saw those three messages twice now <didrocks> ok, I'm lagging/disconnectedâ¦ <Mirv> bzoltan1: published. it'll go to release team's unapproved queue, since it's also seeded on ubuntu/xubuntu/edubuntu desktop images <bzoltan1> Mirv: Cool. Please ping me when I can merge to the trunk... * bzoltan1 goes and starts to prepare the next landing :) <Mirv> sure <sil2100> Morning everyone <sil2100> didrocks: so, in the end, we decided to drop the PHONECON ruleset as defined during vUDS? <bzoltan1> Mirv: who should we ping from th release team to approve the UITK package? <didrocks> good morning sil2100 <didrocks> sil2100: seems soâ¦ <didrocks> sil2100: also as we can't have any good test results for quite a whileâ¦ <didrocks> sil2100: do you feel better today? <sil2100> didrocks: smoketest infra problems again? :( <sil2100> didrocks: a bit, yes - I guess the cold and fever are slwoly giving up <Mirv> morning sil2100! <Mirv> bzoltan1: just hang around at #ubuntu-release and you can ask generally if you're in a hurry or if it seems it takes extra amount of time for them to review it. in general they go in the order of uploads, see https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text= for the queue <didrocks> sil2100: I don't know, we need to wait for the CI team <didrocks> sil2100: however, the previous days, no crashers reported (due to the imageâ¦) <sil2100> :| <tvoss> sil2100, didrocks silo 20 is tested and good from my side. Would appreciate a round of exploratory testing <sil2100> tvoss: sure, let me take a quick look <tvoss> sil2100, thx <sil2100> hm, strange, latest image doesn't boot for me, I wonder if I need to reflash or something <sil2100> I mean, it boots but no unity8 can be seen <didrocks> sil2100: I'm upgrading, will tell you in a few :) * didrocks reboots <didrocks> sil2100: anything in upstart logs? <didrocks> sil2100: yeah, reproducing <didrocks> (process:2351): GLib-GIO-ERROR **: Settings schema 'com.canonical.Unity.Launcher' is not installed <sil2100> Yeah, I see the same, you think this can be the root cause? <didrocks> it is <didrocks> gsettings segfaults when the schema isn't available <sil2100> Oh, how lovely <didrocks> it's intendedâ¦ :/ <didrocks> ok, so the schema is shipped by /usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml <didrocks> so libunity-core-6.0-9 <didrocks> "Drop unity-core based scopes in scopes plugin, expose attributes to shell" <didrocks> I wonder if it's not what retained it into the image <didrocks> and yeah <didrocks> working then <didrocks> plugins/Unity/Launcher/backend/launcherbackend.cpp: QGSettings gSettings("com.canonical.Unity.Launcher", "/com/canonical/unity/launcher/"); <didrocks> so, it needs a dep on libunity-core <sil2100> hm, why was this dropped from the image? <didrocks> yep <sil2100> Did we seed it then somehow? Since I don't see in the package diff any updates that could have dropped it <didrocks> see my previous line <didrocks> it was pulled by the scopes <didrocks> not anymore <sil2100> Ah, right, -plugin-scopes, damn, I'm blind <sil2100> didrocks: should I poke Saviq to include the dep, or should we do it ourselves? A dep in unity8 I guess? <didrocks> sil2100: no, I'm doing an upload <sil2100> ACK <didrocks> sil2100: didn't merge it back though, as I think the proper fix is to remove the schema from that package <didrocks> have it on its own <didrocks> and dep on that <didrocks> Saviq: once you read that ^ <didrocks> 7.84+14.04.20140327.1-0ubuntu2 uploaded <didrocks> cihelp: unping on latest image not providing results. Would be good though to know about the previous one though <psivaa> didrocks: ack, looking at it now <didrocks> thanks psivaa :) <sil2100> Let me drink some meds to be less coldish for the meeting <didrocks> oki * psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - <didrocks> Saviq: let's talk about the best strategy, as we'll have click vs non click, maybe having unity8 shipping its own schema will make rather sense (as there is no more unity-common) <Saviq> sil2100, didrocks, I don't think we should need it... * Saviq greps <didrocks> Saviq: you do in plugins/Unity/Launcher/backend/launcherbackend.cpp <Saviq> ah right <Saviq> we share the same launcher list <didrocks> yep <didrocks> I think with click, it doesn't make sense anymore, wdyt? <Saviq> didrocks, you uploaded a fix directly, did you? and now we should fix in our trunk? <Saviq> didrocks, we won't only support click <didrocks> Saviq: yeah, but I think it's not really a fix (to depend on libunity-core for that) <Saviq> didrocks, when we move to desktop <didrocks> Saviq: yeah, but unity7 will never support click <didrocks> so I guess having 2 list of launcher icon + handling the transition would make sense <Saviq> didrocks, mhm <Saviq> but now we'd need to handle the transition one way... and then the other... :| <psivaa> didrocks: the apparent failures with 270 is due to a dashboard issue of mixing results from prev runs. trying to sort that out <Saviq> didrocks, can we patch-aid it with the dep for now, and fix it properly through a bug? <didrocks> Saviq: just one way I would say <didrocks> Saviq: that works as well for me <didrocks> psivaa: oh? <Saviq> didrocks, it's not just us, we'd need to let customization know that the key changed and such <Saviq> and put that key in a schema somewhere (ubuntu-touch-schemas?) <didrocks> Saviq: oh right customization, let's do baby-steps then <didrocks> Saviq: let me propose a branch then :) <psivaa> didrocks: yea, http://ci.ubuntu.com/smokeng/trusty/touch/mako/270:20140331.1:20140331/7488/ubuntu_filemanager_app/ shows the passed ones and the failed prev run of the same image <didrocks> Saviq: in few minutes :) <Saviq> didrocks, thanks * Saviq files a bug then <ogra_> imgbot, status 271 <imgbot> Image 271 test results on mako - Total: 134, Pass: 110, Crashes: 4, Rate: 80% <ogra_> urgh <davmor2> didrocks: todays image is a bit ummm broken for me <didrocks> davmor2: yeah <didrocks> davmor2: I uploaded a new unity8 <davmor2> didrocks: admittedly I can only find one fault with it <davmor2> didrocks: oh so it's all your fault :P <didrocks> davmor2: no <didrocks> davmor2: I pushed the fixed <didrocks> we can maybe wait 4 minutes and discuss in the meeting? :p <sil2100> ;) <davmor2> sil2100: \o/ you feeling better dude? <ogra_> at least all tests have 80% <ogra_> thats something :P <davmor2> ogra_: and I can't break the image at all it is 100% daveproof "Ship it!" ;) <ogra_> haha <ogra_> well xnox uploaded a change to adb <ogra_> i know he ran AP tests with it but he most likely didnt test screen unlock <sil2100> davmor2: more or less <Mirv> popey: davmor2: is this the one, can I get some AP test report or such on it? http://s-jenkins.ubuntu-ci:8080/job/camera-app-click/48/artifact/out/com.ubuntu.camera_156.14.161.1428_armhf.click <popey> Mirv: ack <popey> davmor2: are you guys saying unity doesn't start on #271 ? <davmor2> popey: that is correct you just get a black screen <popey> works here <popey> phablet 2546 9.7 6.6 431676 125564 ? Ssl 10:06 0:17 unity8 <popey> current build number: 271 <popey> how odd. <davmor2> didrocks: ^ <Mirv> popey: you have better #271 than us <popey> bet this is because my phone was rw when i updated <popey> probably some lib that is still hanging around from #270? <Laney> Are the calendar-app AP tests known to be dodgy when run locally? <popey> Laney: not that I'm aware, bugs welcome. <Laney> hmm <Laney> lemme see <davmor2> ogra_: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1287208 <ubot5> Ubuntu bug 1287208 in android (Ubuntu) "ubuntu-device-flash doesn't remove the .writable_image flag" [Undecided,Fix committed] <ogra_> davmor2, thanks * didrocks reboots to previous kernel <Laney> Mirv: When you run the calendar-app tests using that recipe you gave me yesterday, does test_monthview_go_to_today_prev_year work for you? <didrocks> tvoss: Laney: seb128: mhr3: Mirv: sil2100: going to stop CI train to move to prodstack in few minutes (of course, current builds aren't be stopped) <didrocks> expect the downtime to be < 10 minutes <seb128> didrocks, ok <seb128> great <Laney> ok, good luck! <didrocks> thanks :) <tvoss> didrocks, good luck <didrocks> will tell you when I shut down jenkins <mhr3> thx for headsup <seb128> Laney, having fun with autopilot since yesterday it seems ... is all that only to test your qt patch from the other day? <Laney> ues <Laney> yes <Laney> velocity! <seb128> crazyness <seb128> you patched a "leaf" api <Laney> anyway the same thing happens with the old version of qtdeclarative <sil2100> didrocks: ACK :) <Laney> so Not My Problemâ¢ <didrocks> Laney: yeah, just don't regress the image, only what we ask :) <didrocks> don't fix stuff you can't/are not supposed to fix :) <Laney> it's just disturbing when things are different locally vs. in CI <didrocks> Laney: yeah, agreed :/ * seb128 impressed by Laney's perseverance <seb128> I wouldn't have bothered to run all autopilot tests for a 1 liner to a tz function <Laney> haha <Mirv> Laney: it did succeed yesterday when I tested new UITK, ie calendar-app 12 tests passed (if I'm reading the correct line). but it's not like unheard that running AP tests locally does not easily yield same results as on the test infra <Laney> mmm <Mirv> I guess the normal "pass" is "same result as without the update" when doing the local tests <popey> Mirv: camera passes, stick it in the store and I'll get it approved <Mirv> popey: ok <Mirv> popey: it says package scan took too long, and that one should check status at https://myapps.developer.ubuntu.com/dev/api/click-scan-complete/93/ <popey> Mirv: i cant see that â¹ <Mirv> before that it did say it got submitted to https://myapps.developer.ubuntu.com/dev/api/click-upload/com.ubuntu.camera/ <popey> or that <Mirv> well it does say "Please check the status later at...", so I wonder who much later <Mirv> we might need sergiusens then <popey> yeah, i don't have the creds for that account, so can't see it <davmor2> Morning all <didrocks> Mirv: seb128: Saviq: sil2100: tvoss: mhr3: thostr_: stopping jenkins for the migration <sil2100> didrocks: ok, good luck ;p <Saviq> didrocks, have fun! <didrocks> will try :p <sil2100> ;) <seb128> didrocks, ok <Mirv> popey: ok, I experimented what happens if I retry, and it worked.. Please check out the application at: https://myapps.developer.ubuntu.com/dev/click-apps/506/. <popey> Mirv: i see it now <popey> Mirv: approved it <Mirv> nice! <didrocks> all is transition, we have an issue on librarian firewall FYI <didrocks> waiting on webops to check/open the firewall FYI <Saviq> didrocks, seems there's a problem with SSO <Saviq> didrocks, it redirected me to https://job/landing-002-1-build/build?delay=0sec <didrocks> Saviq: please don't run anything for now <didrocks> Saviq: sso was working for me <didrocks> though <Saviq> didrocks, sure, just saying <didrocks> Saviq: let me unlog and relog <Saviq> didrocks, it logged me in fine, but redirected to the wrong url <Saviq> once, at least <plars> didrocks: on 270 I was trying to rerun some things into late last night, and was hopeful that the previous failed attempts was just due to a typo in the test list <plars> didrocks: but I fell asleep before it finished, so I didn't get to see until now, sorry <plars> didrocks: I'm still not sure what happened there, but it looks like there is something wrong in the current image too <didrocks> ev: I don't know why Saviq has that, seems that the juju charm was executed right? <plars> didrocks: nothing changed in the ci code that could explain it though (no new unlocker or anything) <didrocks> plars: ok, no worry, just an email on the ML next time :) <didrocks> ev: may be the callback from sso side is wrong? <plars> didrocks: sorry, intendted to <didrocks> Saviq: weird, I'm redirected to the right url here <didrocks> Saviq: let me try from another one <didrocks> Saviq: yeah, working :/ <didrocks> Saviq: and same from https://ci-train.ubuntu.com//job/landing-015-1-build/build?delay=0sec <didrocks> Saviq: can you unlog/retry? <ev> didrocks: that'd be surprising, given it redirected me just fine <Saviq> didrocks, yeah let me try again <didrocks> ev: yeah <didrocks> I tried 3 configurations here <Saviq> didrocks, ok, can't repro any more <ev> yay <didrocks> Saviq: can we blame you or your browser? :p <didrocks> realistically, keep us posted if you see so <didrocks> soâ¦ <ev> it's one to watch out for though <ogra_> stop using oxide :P <Saviq> didrocks, you can <ev> I doubt that came from nowhere <didrocks> ev: agreed, let's see if more people get it <didrocks> everything is back but the firewalling <didrocks> so as long as you don't prepare or watch a build, you can resume working :) <didrocks> (so publication + m&c) <didrocks> 12:48:05 moon127 | didrocks, I've getting branch reviewed now. I would expect ~20 mins to land it on the firewall and make <didrocks> | live. <didrocks> Saviq: seb128: Mirv: sil2100: thostr_: mhr3: tvoss: ^ <didrocks> Laney: ^ <didrocks> (so, you can publish, m&c, just not build/watch) <Laney> neat <Mirv> ok <sil2100> ACK <didrocks> 12:49:58 moon127 | didrocks, we've rushed that one through, and I can wget that file on the jenkins instance <didrocks> so all should be back to normal, feel free to build things :) <didrocks> Saviq: seb128: Mirv: sil2100: thostr_: mhr3: tvoss: Laney ^ <sil2100> Yessss <sil2100> ;) <Laney> yay for cloud <sil2100> Thanks o/ <tvoss> \o/ <Laney> lemme try to publish qtdeclarative <Saviq> \o/ <sil2100> didrocks: it seems I don't have permissions on the new jenkins to do builds! <didrocks> Laney: some packages failed to build? <Laney> did they? <didrocks> sil2100: did you check the ubuntu-unity box? <Saviq> "saviq is missing the Job/Build permission" ;( <sil2100> hm, right, it didn't even ask me that, just redirected instantly, let me relog <Laney> I believe spreadsheet is false false false <sil2100> didrocks: it doesn't allow me to <Saviq> sil2100, /me too, logging out and back in doesn't help * Saviq goes to login.ubuntu.com <Mirv> sil2100: also check to login from top right corner <sil2100> didrocks: when I press 'login' then I just instantly get logged in without any prompts <Mirv> hmm, yeah same here <sil2100> Mirv: just did that <didrocks> Saviq: sil2100: do you have the teams you are in checkbox? <Laney> didrocks: I got redirected to 'job' after SSOing <didrocks> Laney: ^ <Laney> known? <sil2100> didrocks: which checkbox? I have no checkboxes <Laney> is that what they are saying? <didrocks> Laney: jobs? <Laney> Firefox can't find the lauren32@example.com. <Saviq> denied :| <didrocks> ev: around? ^ <Laney> https://job/landing-008-1-build/build?delay=0sec <Mirv> Laney: try again, I got the same the first time <didrocks> Laney: hum, where are you clicking? <sil2100> didrocks: when I press 'log in' I instantly get logged in, without any checkboxes <didrocks> argh, so it's a real issue <Saviq> didrocks, it's not asking for the team membership for some reason <Laney> build, SSO 2fa prompt, bogus redirect <Mirv> didrocks: first time double clicking from spreadsheet it goes to https://job/ somehow after a couple of redirects <Laney> I didn't notice the checkboxes I'm afraid <Mirv> the next time works <Laney> Mirv: I bet if you log out and back in it does it again <didrocks> ev: really need you here ^ <Laney> anyway it works if you're already authenticated <Laney> just the error on first login <ev> hi <Laney> (notwithstanding the permissions check that I didn't notice, sorry) <didrocks> so first login is an issue? <moon127> didrocks, hi <didrocks> hey moon127 <Laney> lemme try re-logging-in <didrocks> so it seems first login is failing for everyone <didrocks> and redirect to https://job/landing-008-1-build/build?delay=0sec for instance <ev> didrocks: they shouldn't see the page with checkboxes as ci-train.u.c is in the SSO whitelist <didrocks> ev: ah, ok <sil2100> ev, didrocks: then how can I get my permissions correctly now? * didrocks tries in a anonymous session <Laney> hmm I didn't get the 'job' thing that time <didrocks> Mirv: are the permissions working then? <Laney> perhaps that only happens the first time you log in <didrocks> ok, so here, on a anonymouse section, I login <didrocks> then, I'm redirected <didrocks> but unlogged <didrocks> I reclick on "signing in" <Laney> ah no, I got it in a new browser that time <didrocks> and I have rights <didrocks> Laney: but then, do you have the right perms to run jobs? <Laney> didn't try yet <Mirv> "timo-jyrinki is missing the Job/Build permission" <didrocks> do you mind trying? (my user has more rights, so unsure it maps) <Mirv> didrocks: ^ <Laney> I want to publish 008 so let me see what happens <Mirv> tried watch only in landing-011 <didrocks> moon127: ev: ok, so it seems the teams attributes are not send to jenkins <Laney> yeah same as that <didrocks> moon127: ev: and there is another issue on first login (doesn't redirect to the right url) <didrocks> Mirv: Saviq: sil2100: seb128: Laney: tvoss: meanwhile, if you have any requests, proxy it to me, I can handle the pushing buttons <Laney> ok, please publish 008 then <Laney> actually I'm not sure how that works for direct uploads <Laney> I guess it's publish and clean, no merge <seb128> didrocks, noted, I'm going to have a few in the afternoon, thanks <didrocks> (done) <Laney> thanks! <didrocks> I found the issue on perms <didrocks> I can fix it, some secs <didrocks> ok <didrocks> so guys, can you retry? <Mirv> didrocks: works! https://ci-train.ubuntu.com/job/landing-011-1-build/1/console <didrocks> Laney: Mirv? ^ <didrocks> phew :) <sil2100> Indeed, works \o/ <didrocks> only the "first blank redirect remains in the list for now". Otherwise, you are all good to click in what you need :) <didrocks> Laney: seb128: mhr3: tvoss: Saviq: ^ <Laney> nice work didrocks <seb128> didrocks, thanks, well done! <tvoss> didrocks, nice one :) <didrocks> yw, thanks for your patience (took a little bit longer than wanting, but hopefully, didn't block anyone for too long) * didrocks kicks an image build to celebrate that <didrocks> (with the fixed unity8) <Saviq> \o/ <sil2100> didrocks: so, PPA for silo 20 had the unity-scopes-api package already removed over an hour ago and running 'Build' with 'watch only' still makes the job look for unity-scopes-api in the PPA <didrocks> sil2100: ah, the fix for Qt5.2 probably created this <sil2100> How can I workaround this ;)? <imgbot> === trainguard: IMAGE 272 building (started: 20140401 11:20) === <didrocks> sil2100: reading the code? * didrocks looks <didrocks> but sorry, other requestsâ¦ <didrocks> hum <didrocks> sil2100: can you provide the trace? <didrocks> for pkg in src_ppa.getPublishedSources(distro_series=series, status="Published"): <didrocks> so I guess it's still published <didrocks> hum <didrocks> unity-scopes-api is a branch right? <didrocks> have you reconfigure to remove it? <davmor2> didrocks: so 271 mostly works by the look of it so just making unity8 work by default to fix that :) <didrocks> seems so <didrocks> you reconfigured it <didrocks> (answering as you are not around) <sil2100> Yeah, I was looking in the code myself <sil2100> didrocks: tvoss reconfigured it yesterday already, I did that today as well <didrocks> weird <sil2100> Since I thought it might somehow help <didrocks> after the reconfigure <didrocks> we still have unity-scopes-api.project <didrocks> if this bug was real, we would have it a lot more before <didrocks> sil2100: # remove all files related to sources that are not in the configuration anymore <didrocks> oh <didrocks> sil2100: did you remove in the ppa <didrocks> and then run reconfigure? :/ <sil2100> didrocks: what I did was: <sil2100> didrocks: in the morning I removed the package from the PPA and just press 'rebuild' <didrocks> why did you remove the package from the PPA? <didrocks> rather than reconfiguring? <sil2100> didrocks: after and hour I retried that, it was still looking for the project, so I reconfigured and reran build again <sil2100> didrocks: because tvoss said he reconfigured it yesterday <didrocks> seems he didn't :/ <sil2100> And that this package in the PPA was somehow only a leftover after something <didrocks> sil2100: no, the reconfigure removes the package <didrocks> that's why the source isn't cleaned from the config <didrocks> for (source, version, rev, branch) in packageinppamanager.get_all_packages_uploaded(): <didrocks> if source not in all_silo_projects: <didrocks> see prepare-silo <tvoss> didrocks, sil2100 I'm confused, what did I do wrong? <didrocks> tvoss: seems you didn't rerun the reconfigure job after removing the MP for unity-scopes-api <sil2100> tvoss: not sure, you mentioned that you reconfigured silo 20 yesterday, right? <tvoss> sil2100, yup, I might have done something wrong ... not sure what, though <didrocks> well, anyway, there is a way to patch the code to prevent that I guess <sil2100> Not sure what went wrong as well that the package .project file remained, hm <popey> psivaa: why am I not seeing a newer build of calendar in jenkins than 222 on 28/3? trunk has 226. <Laney> didrocks: is publishing working? <Laney> wait <Laney> I forgot unapproved :P <Laney> ignore me <didrocks> Laney: tssss :p <psivaa> popey: mind pasting the jenkins link pls? <didrocks> Laney: it's a potential failure though <Laney> it is in there <didrocks> ah ok :) <didrocks> so the rsync is working :) <popey> psivaa: http://s-jenkins:8080/job/calendar-app-click/ <didrocks> (I checked it, but good that we have a real life confirmation :p) <psivaa> popey: thx. looking <popey> ta <didrocks> sil2100: wdyt about that? http://paste.ubuntu.com/7189309/ <psivaa> popey: this job has been manually triggered mostly by balloons in the recent past. so the absence of that appears to be the reason :) <popey> psivaa: ah, can you press the same buttons? <sil2100> didrocks: looks ok, a bit safer in case of such hick-ups as today ;D <sil2100> Thanks! <didrocks> sil2100: ok, pushing and putting that in production, then rerunning configure <Saviq> sil2100, reconfigure silo 015 please? needed to add thumbnailer there <psivaa> popey: sure, done. still pending the slaves to be free to execute <sil2100> Saviq: ok <popey> psivaa: thank you. <psivaa> yw <didrocks> sil2100: hum <didrocks> doesn't seem to have worked <sil2100> didrocks: so... maybe the previous reconfigure really helped? <sil2100> I mean <sil2100> Not helped, but worked? <sil2100> And allowed_components_from_previous_config doesn't have what we need? <didrocks> sil2100: it didn't and still don't <sil2100> Saviq: reconfigured <Saviq> sil2100, thanks <Saviq> didrocks, upload fails https://ci-train.ubuntu.com/job/landing-002-1-build/3/console ? <Saviq> twice already * sil2100 looks <Mirv> hmm <didrocks> firewall again <didrocks> moon127: still around? <didrocks> moon127: uploading to the ppa from the machine fails <didrocks> (traditional dput ppa:â¦) <didrocks> seems like launchpad firewall rules are really compartimentend <didrocks> ev: ^ <sil2100> :( <didrocks> sil2100: oh one sec, on unity-scopes-api <didrocks> I think I tried "actions" <didrocks> instead of scopes <didrocks> sil2100: it's like if rmtree wasn't working * cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - <didrocks> Saviq: so moon127 isn't around and there is no vanguard on #webops :/ <sil2100> o_O <moon127> didrocks, Saviq - looking <didrocks> sil2100: I'm pretty sure there are some permissions issues as well <moon127> didrocks, can you just confirm that is dput ftp rather than ssh <didrocks> moon127: yeah, it's dput ftp <sil2100> That would be strange..! <didrocks> sil2100: OSError: [Errno 2] No such file or directory: 'unity-scopes-api' <didrocks> hum, maybe I'm not in the right dir <didrocks> sil2100: yeah, found the issue <sil2100> clean_source looks ok? <didrocks> sil2100: I'm not in the silo path when cleaning <sil2100> uh, so how did that work before? :o <moon127> didrocks, firewall change is live <sil2100> Saviq: ^ can you retry? <didrocks> moon127: thanks! <didrocks> Saviq: you should be good now <didrocks> sil2100: it never worked at this stage I guess <didrocks> sil2100: phew: https://ci-train.ubuntu.com/job/landing-020-1-build/7/console <sil2100> didrocks: thank you! I see the change to silo_path ;) <didrocks> sil2100: yeah, while cd, better to change for a better name :) <sil2100> A lot of changes, just hope it doesn't break anything else ;p <sil2100> hah, sure <sil2100> :) <didrocks> sil2100: it's just Ctrl + D -> rename config_path to silo_path * didrocks waits on Saviq's source package creation to finish to see the uploads <didrocks> hum <didrocks> moon127: seems it didn't work <sil2100> ;/ <didrocks> moon127: default dput to a ppa is ftp though, right? <didrocks> [ppa] <didrocks> fqdn = ppa.launchpad.net <didrocks> method = ftp <didrocks> incoming = ~%(ppa)s/ubuntu <didrocks> login = anonymous <didrocks> from dput.cf <didrocks> orâ¦ /me has a terrible doubt <didrocks> moon127: is dput installed on the machine? <moon127> didrocks, checking - fwiw I can open an ftp connection to ppa.launchpad.net manually <moon127> ha ha it is not!! <didrocks> it's weird, it was pulled from other depends <didrocks> not sure what is different on that machine <didrocks> ok, I'm adding it explicitely in the charm then <didrocks> moon127: mind installing it meanwhile? <moon127> didrocks, sure <didrocks> thanks :) <didrocks> and then, let's reretry :p <moon127> done <rsalveti> ogra_: didrocks: hey, did we find what broke 271? <rsalveti> just saw the email * didrocks retries <didrocks> rsalveti: yeah, a schema not installed <didrocks> and so gsettings segfaults <didrocks> (libunity-core got dropped from the scopes) <didrocks> but unity8 is using the schema <rsalveti> oh, interesting <didrocks> which is in libunity-core <ogra_> rsalveti, all fixed already <didrocks> #272 should be ready soon <rsalveti> thought it could be kernel, android or something I did :-) <ogra_> 272 is already building <rsalveti> great <didrocks> rsalveti: ahah, not that low :p <rsalveti> great :-) <ogra_> hmm, i should add buildinfo to imigbots status command <Mirv> lots of click app updates will be in the next image :) <ogra_> fun <didrocks> sil2100: seems that process-cpp can be published, right? <didrocks> Saviq: 2014-04-01 12:42:43,995 WARNING A version (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1) is available at the destination archive for that component but is not in the destination branch which is lauren32@example.com+14.04.20140324-0ubuntu1. You need to ensure that your version contains the fix in the destination or you can force rebuild to bypass the check. <didrocks> I need to run with "don't care" :p * didrocks reruns <imgbot> === trainguard: IMAGE 272 DONE (finished: 20140401 12:45) === <imgbot> === changelog: http://people.canonical.com/~ogra/touch-image-stats/272.changes === <ogra_> there we go <didrocks> great :) <didrocks> welcome back libunity-core! <ogra_> ah, and there is the camera-app too <didrocks> yep :) <ogra_> oh, whats that initramfs change * didrocks reflashes to retry before sending an email to the ML * davmor2 ota updates <dbarth> didrocks: sorry, but silo 7 seems different: it has no build button anymore <dbarth> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=25 <didrocks> dbarth: hum, someone copied and paste and mess with the spreadsheet I guess :/ <dbarth> honestly i don't think i messd that cell up <didrocks> dbarth: I restored the formula from another silo <didrocks> dbarth: can be anyone :p <dbarth> thanks didrocks! <didrocks> yw <davmor2> didrocks: so ota from 271 to 272 gives me a working phone from a working phone. I'm just flashing 271 see if the manual route does work <didrocks> davmor2: manual route, being? <didrocks> davmor2: system-image-cli? <davmor2> didrocks: yeap <didrocks> davmor2: ok, keep me posted <didrocks> you just run system-image-cli <didrocks> and then reboot your phone <didrocks> right? <davmor2> ogra_: ^ system-image-cli -d 0 isn't it? <ogra_> probably with the channel <didrocks> davmor2: I don't think you need -d 0 <ogra_> but yeah <didrocks> just system-image-clic <didrocks> cli* <didrocks> you don't need a full download <ogra_> -d 0 forces a full image reinstall <didrocks> yeah <didrocks> we don't want that <ogra_> i would always run it with -v <davmor2> ogra_: thanks <ogra_> else it stays completely quiet <didrocks> davmor2: so, just system-image-cli -v <ogra_> (which is irritating since it can take a while) <davmor2> didrocks: indeed <ev> didrocks: are we all good on the prodstack move? <didrocks> ev: still need to check that dput is working <didrocks> https://ci-train.ubuntu.com/job/landing-002-1-build/6/console <didrocks> is the last trial <davmor2> didrocks, ogra_: well that seems to of updated now to see if I get a shell <didrocks> davmor2: excellent! <davmor2> didrocks, ogra_: I do http://paste.ubuntu.com/7189617/ <davmor2> video and music still in place too woohoo!!!! <didrocks> heh <tedg> In silo 1 I've got a "url-dispatcher is in the UNAPPROVED queue" - how do I fix that? <didrocks> tedg: get the release team to approve it :) <didrocks> they are reviewing the queue regularly <didrocks> so, it should be ping-less :) <tedg> Okay, where do I see that queue? <didrocks> everything that is seeded in any flavor (but Touch) is getting in UNAPPROVED <didrocks> tedg: https://launchpad.net/ubuntu/trusty/+queue?queue_state=1 <ogra_> or by being in the #ubuntu-release channel ... the queuebot there announces package states <tedg> Ah, interesting. <tedg> I was surprised it didn't show up on the source package page. <Saviq_> didrocks, this really doesn't work still https://ci-train.ubuntu.com/job/landing-015-1-build/6/console :| <didrocks> tedg: as long as it's not approved, you can kick it back and reaccept with the same version <tedg> didrocks, Not sure what that means? <didrocks> Saviq: argh, I was looking at the another landing (longer) <didrocks> yeah, so seems the upload doesn't work <didrocks> grrrr <didrocks> Saviq: I'm asking the webops vanguard, they told it was openedâ¦ <Saviq> :| <Saviq> didrocks, it looks like -build jobs are much slower now, any idea? <sil2100> Hardware differences, but I would expect it to be for the better <didrocks> Saviq: I don't control the architecture at all anymore <didrocks> Saviq: so yeah, I would say hardware difference, but I agree with your feeling <cjwatson> tedg: accepted now, sorry for the delay <Saviq> didrocks, kthx <tedg> cjwatson, Great! Thanks! <mhr3> sil2100, silo for 27 pls? <sil2100> mhr3: oh, something set to ready? <sil2100> mhr3: let me look <sil2100> Oh, something new <sil2100> mhr3: assigning <mhr3> ty <sil2100> mhr3: silo 13 <didrocks> psivaa: plars: do we have full test results on image #270 now? <plars> didrocks: no, there was a problem with the reruns I tried at the end - just ignore those <plars> didrocks: 271 was already in progress though <didrocks> plars: so, we will never have test results on #270? <didrocks> knowing it was the first one for the crash files <didrocks> and #271 is lost <plars> didrocks: I can try to pull something off for 270 <didrocks> I thought psivaa was working on that since this morning <plars> didrocks: at worst, I can run them locally on a mako if you like <plars> oh, maybe - psivaa is that right? <didrocks> so maybe check with him? <psivaa> didrocks: plars: i was trying to get the dashboard right, which i could not <plars> psivaa, didrocks: so I do have one idea how to do it. Let me give it a shot. If it works then I may have an idea how we can make it an option for reruns <plars> make image id an option that is <didrocks> plars: great! <plars> didrocks: and if all else fails, I'll just kick off a local run and confirm that all of those missing ones look ok <didrocks> Saviq: seems I didn't get traction on the speed regression :/ <didrocks> plars: ok, thanks! <Saviq> didrocks, yeah I saw that, it took an hour to prep silo 002, that's rather bad :| <Saviq> even if it built as many packages as it did <didrocks> Saviq: I don't even have ssh access anymore to itâ¦ so really can't help <Saviq> didrocks, I understand, just saying that we need to talk to someone that can <didrocks> that's what I tried, ev has good connexion with them, so maybe himâ¦ <ev> hm? <Saviq> didrocks, do you have logs from previous silo 002 preps? to check how much it took there? <didrocks> ev: see our discussion with webops <didrocks> Saviq: I have to restart jenkins for that, and I'm afraid some people will try to reprepare from it <didrocks> Saviq: without having any links <popey> psivaa: http://s-jenkins:8080/job/calendar-app-click/106/console it failed.. any idea why? <didrocks> Saviq: I meant, keeping previous links <psivaa> popey: 1 sec pls <Saviq> didrocks, :/ <didrocks> Saviq: I can temporarly if you know what you want to check <Saviq> didrocks, yeah, just want to find a build-002-1-build <didrocks> Saviq: started <Saviq> didrocks, that prepared the whole thing <didrocks> tell me once I shut down :p <ev> didrocks: I think we need to go beyond just saying it's slower. Can we instrument the code to provide timings? <didrocks> ev: jenkins itself gives timing, and Saviq has exactly the same set <ev> oh great, so where is it taking longer? <ev> I didn't see that in the #webops chat <didrocks> ev: the build part to prepare source packages <didrocks> I restart the previous jenkins for Saviq to gives more infos <ev> just build? It's not debootstrapping or anything? <ev> or hitting apt in any way <didrocks> ev: I don't have finer grain <didrocks> so we won't be able to compare <didrocks> between old and new infra <ev> it builds a package cache after the first run, no? <didrocks> yeah <psivaa> popey: that appears to have been because of an rm op failing. i think i've fixed it and kicked another run. <Laney> You should try the -nc that I told you about before to avoid needing build-deps <popey> psivaa: thanks, will that happen again? <psivaa> popey: i dont think so because i changed the job config. (strange that it has been happening so far though) <popey> psivaa: ah okay, thanks. <psivaa> popey: the next build succeeded. <popey> great! <didrocks> Saviq: any luck? I would prefer to shutdown the old instance to avoid people getting mislead <Saviq> didrocks, http://pastebin.ubuntu.com/7189814/ <Saviq> didrocks, shut it down <Saviq> 3 times slower for unity8, for example :| <didrocks> ev: ^ <didrocks> Saviq: thanks, stopped <ev> hmmm interesting <ev> didrocks: why are those info lines different though? That seems to imply we don't quite have a like for like comparison here - that it might have actually gone down a different code path * Saviq uploads the log <Saviq> http://paste.ubuntu.com/7189823/ <Saviq> that's the one from the old instance <didrocks> ev: once is with "force rebuild" not the other one I guess <ev> so they're not going down separate code paths? <didrocks> ev: the difference is: <didrocks> http://paste.ubuntu.com/7189830/ <ev> rm -rf taking a long time strikes me as strange, to say the least. There's not a lot of IO overhead in that. <didrocks> ev: so, one is before the other, and the function called is just doing diff -Nrup old/ new/ <didrocks> ev: so the second one is in theory few ms faster than the first one <didrocks> (less checks) <didrocks> let's say with launchpad api call, 2s faster <didrocks> (while it's the contrary, it's way slower) <didrocks> ok, really late exercising/first break <didrocks> I'll probably be back on time for the meeting <ev> didrocks: when you get a chance, can you do the following on the canonistack instance that you were running ci-train from: <ev> sudo hdparm -Tt /dev/sda <ev> and <ev> dd if=/dev/zero of=/home/ubuntu/output bs=1M count=1024; rm -f ~/output <ev> then we can ask #webops to do the same and further isolate this problem <didrocks> ev: http://paste.ubuntu.com/7189886/ <didrocks> ev: /dev/vdc1 is /var/lib/jenkins (so first matches first, second matches second) <didrocks> cowbuilder is in the second <didrocks> sil2100: if I'm late for the meeting, mind starting it? <sil2100> didrocks: sure :) <didrocks> thx :) <bzoltan> didrocks: sil2100: I would need a silo for a single line change in the QtC Ubuntu plugin project ... important for jono and dpm <dpm> bzoltan, wait, that change is not important until the other bug fix lands <sil2100> bzoltan: I can assign a silo, sure <sil2100> kgunn: hi! You can m&c line 24 if anything ;) <dpm> bzoltan, sil2100, let's not add a silo until bug 1297190 is addressed <ubot5> bug 1297190 in qtcreator-plugin-ubuntu "Need to integrate the Unity Scopes Tool to Qt Creator" [Undecided,New] https://launchpad.net/bugs/1297190 <kgunn> sil2100: yes sir! <sil2100> dpm: oh, too late... I guess having a silo is not a big deal anyway <dpm> ok, I was just trying to avoid extra work <sil2100> dbarth: the webbrowser oxide landing is ready for a m&c as well - if you have the moment, could you press the button? :) <dbarth> sil2100: will do right now <Saviq> didrocks, looks like platform-api didn't get uploaded? https://ci-train.ubuntu.com/job/landing-002-1-build/6/consoleFull <sil2100> dbarth: thanks <sil2100> I wonder why the autopilot landing didn't move at all since such a long time * doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - <ChickenCutlass> rsalveti: hangout <ChickenCutlass> rsalveti: oh right â your out <ChickenCutlass> lol <plars> didrocks: so it looks like something changed with permissions on /root, which is causing 'bash: /root/.bashrc: Permission denied' when the click image test tries to run a command with adb. I think we can work around it in the test, but that's why that's happening. <plars> didrocks: *that's why the click image test is failing <ogra_> plars, talk to xnox <ogra_> plars, adbd was changed <plars> ogra_: ack, thanks <ogra_> it now processes a login shell ... which means you get a home, locale etc for root <ogra_> i wouldnt expect /root/.bashrc not being writable to be a blocker for anything though <ogra_> that should just be a warning <popey> davmor2: can you replicate bug 1300847 <ubot5> bug 1300847 in webbrowser-app (Ubuntu) "OSK won't come up in twitter/fb webapps #272 on flo" [Undecided,New] https://launchpad.net/bugs/1300847 <Saviq> didrocks, https://ci-train.ubuntu.com/job/landing-002-1-build/8/console silo broke? :/ <Laney> do I need to do ONLY_FREE_SILO for source package only silos? <Saviq> Laney, tried without it? <Laney> no <Laney> scared <Saviq> Laney, I assume it's published? <Laney> ya <Saviq> Laney, then just do without <Saviq> Laney, worst case it will fail <Saviq> Laney, but doubt that <Saviq> Laney, it will just not find any MPs, so it will just do the usual <Laney> I guessed it would, but wanted to confirm <Laney> now I have a scapegoat, so ok :P <plars> didrocks: ok, I still need to do the jenkins bits to make it complete, but I've done the script changes for allowing an arg to specify the revision all the way through the ci process and ran locally. It just finished up and those other tests passed just fine it seems, but there were 3 failures in ubuntu_system_settings on this run <sil2100> Laney: citrain is a smart system, it will bail out if something is wrong so no worries! <didrocks> Saviq: was is fixed? <didrocks> it* <Saviq> didrocks, let me try <Laney> seems to be working <didrocks> Saviq: I dunno, just back from exercise :) <didrocks> so I was asking <Saviq> didrocks, nope, https://ci-train.ubuntu.com/job/landing-002-1-build/9/console <didrocks> Laney: yeah, it should do the right thing <didrocks> Saviq: hum <didrocks> Saviq: ok, so same thing than yesterday <ogra_> imgbot, status 272 <didrocks> Saviq: what leaded to that? I would be interested <Saviq> didrocks, not sure <imgbot> Image 272 for mako has not finished the tests, status is: Running <Saviq> didrocks, I interrupted the previous job (which I think failed to upload platform-api) <ogra_> slow stuff is slow ... <didrocks> Saviq: yeah, seeing that, but that doesn't explain <didrocks> Saviq: I try to commit in an atomic way <Saviq> didrocks, and the next run was like that - tried to rebuild platform-api and u-s-c <didrocks> Saviq: yeah, I need to understand how that can happen <Saviq> didrocks, last reconfigure was way before that <didrocks> Saviq: with shell access willbe harderâ¦ <Saviq> didrocks, +out <didrocks> Saviq: right :p <didrocks> http://people.canonical.com/~platform/citrain/landing-002 <Saviq> didrocks, looks like valid json <didrocks> Saviq: yeah, but no status <didrocks> I wonder howâ¦ <Saviq> ah <didrocks> Saviq: it was "building" as the status before, right? <Saviq> didrocks, maybe it didn't update in time? <Saviq> didrocks, between me interrupting the old build and starting a new one? <dbarth> sil2100: can i have a new silo for a doc fix (html api)? <dbarth> line 30 <didrocks> Saviq: no, this is done in sync <Saviq> didrocks, no idea then :| <sil2100> dbarth: looking <sil2100> dbarth: sure, it's ready? <didrocks> Saviq: I'm trying to sync hard :p <sil2100> dbarth: since the ready field is not set yet ;p <didrocks> Saviq: think* <ogra_> you think you are trying to sync ? <didrocks> :p <didrocks> Saviq: I really don't get it, is it urgent? Otherwise, I'll appreciate a fresh eye to see if we do have a race <dbarth> sil2100: ah sorry, just setting it; i was reviewing the branch <didrocks> robru: around? <didrocks> plars: ^ <cyphermox> rsalveti: I'd like to land mtp today; should I bother going through you guys for the citrain landing stuff or just file it myself, since I have the necessary knowledge and access? I'd just need an extra pair of eyes for additional testing before landing <cyphermox> well. that and I really need to write the test plan and all :) <sil2100> mhr3: m&c ready! <mhr3> sil2100, ty, cleaning <davmor2> popey: so no I can't replicate it I can log in no problems it gives me the wrong facebook view let me try twitter instead <davmor2> popey: do you ever get this closing an app http://davmor2.co.uk/~davmor2/apps-nil.png ? <fginther> bfiller, I just found a package ofono-phonesim-autostart error for dialer-app that prevents CI testing on the phone: https://bugs.launchpad.net/dialer-app/+bug/1300880 <ubot5> Ubuntu bug 1300880 in dialer-app "CI can't install dialer-app debian packages on image 272" [Undecided,New] <fginther> bfiller, please let me know if there is someone else I should ping <popey> davmor2: i rarely close apps, so no. <popey> kinda annoyed I can't start update-manager on #250 <bfiller> fginther: boiko should know <fginther> boiko, any thoughts on https://bugs.launchpad.net/dialer-app/+bug/1300880 ? <ubot5> Ubuntu bug 1300880 in dialer-app "CI can't install dialer-app debian packages on image 272" [Undecided,New] <bfiller> fginther: have changes been made recently to the ofono-phonesim-autostart? <davmor2> popey: it should in theory open it was tested on 250 <popey> davmor2: and surely someone would have said by now!? <davmor2> popey: so I guess it's just you] <popey> bah <t1mp> what can cause this? 2014/04/01 18:25:21 Cannot push /home/tim/.cache/ubuntuimages/pool/ubuntu-c3473594f772b94d7a14e917124a119e3439da5658c4265077eda3b16b186f4b.tar.xz to device <t1mp> see http://pastebin.ubuntu.com/7190485/ I get it when I try to flash image 272 <t1mp> where is it pushing it? maybe the partition is full? http://pastebin.ubuntu.com/7190500/ <fginther> bfiller, it looks like the current version of the package was uploaded march 5 <t1mp> oh, wrong channel <ogra_> t1mp, to /cache ... <fginther> bbiab <ogra_> (which translates to /android/cache/ on a running ubuntu) <boiko> fginther: hmm, that's the first time I see this error, let me take a look at the ofono-phonesim-autostart script <t1mp> ogra_: none 4.0K 0 4.0K 0% /android <t1mp> that is weird * t1mp rebooting device <ogra_> t1mp, /android/cache/recovery is what you want to check <ogra_> or just /android/cache <ogra_> /android is just
{'channel': 'ubuntu-ci-eng', 'month': 4}