[01:05] Errr mah gerd === _salem is now known as salem_ === salem_ is now known as _salem === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:38] cihelp could you help me to understand https://jenkins.qa.ubuntu.com/job/indicator-keyboard-15.04-vivid-amd64-ci/3/console ? [08:38] "bzr: ERROR: Permission denied: "Cannot create '15.04'. Only Bazaar branches are allowed."" [08:38] what's the issue? [08:38] that's the CI on https://code.launchpad.net/~seb128/indicator-keyboard/use-new-gee/+merge/278552 [08:38] also why is it trying to use 15.04? [09:03] seb128: i'll take a look at that error [09:03] psivaa, hey, thanks [09:26] seb128: this is occurring since the target branch for vivid builds have been marked as lp:indicator-keyboard/15.04 [09:26] seb128: this is inline with all the projects in http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/revision/1261#stacks/vivid/indicators.cfg [09:27] for e.g. indicator bluetooth: https://code.launchpad.net/~indicator-applet-developers/indicator-bluetooth/trunk.15.04 [09:27] psivaa, where is the vivid coming from? [09:27] psivaa, we land to xenial by default it's a desktop project === joc|away is now known as joc_ [09:30] seb128: back in last May, we asked for the teams to let us know what releases each projects needs to be built and run against, and https://docs.google.com/spreadsheets/d/1xaUV9QDNl_r9QJJ0DwiaigxD1qTYUW5V3aperJMRqsI/edit#gid=0 is the information we obtained [09:31] line 66, is the relevant one [09:37] psivaa, l67 states trunk should build against wily [09:44] psivaa, l66 is lp:indicator-keyboard/15.04 but that branch doesn't even exist [09:44] https://code.launchpad.net/indicator-keyboard [09:44] we have just trunk [09:45] seb128: we could just remove the lp:indicator-keyboard/15.04 part if that does not exist [09:46] psivaa, +1 [09:46] seb128: ack, thanks. will work on it [09:46] thanks [10:19] cihelp https://jenkins.qa.ubuntu.com/job/cu2d-choo-choo-ci/931/console "Unable to create directory /var/lib/jenkins/.pylint.d" this used to work, did something change? [10:21] robru: will give that a look in a little bit [10:21] psivaa, thanks [10:23] psivaa, oh nm that might be a false positive, there's a test failure hiding further up the log [10:27] psivaa, yeah, sorry for the noise, that's all me [10:27] robru: ack, thanks [10:28] yw [14:20] cihelp: hey, seeing "Could not add content object 'None' due to IO Error: [Errno 2] No such file or directory: '/var/log/syslog'" in autopilot tests run by jenkins. Why is that? [14:27] jgdx, that is something the test or autopilot itself is doing. Autopilot is trying to add a section of /var/log/syslog as an artifact to the test case in the event it has messages relevant to the test. [14:28] jgdx, that should have no impact on the outcome of the test, it just means that it couldn't supply richer content. I recommend following up with the QA team if you still have questions. [14:28] fginther, okay, thank you [14:47] fginther, what about ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? ? [14:47] jgdx, looking [14:47] it's new, seems to have happened post krillin migration [14:47] jgdx, oh, do you have an example? [14:47] fginther, https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-touch/4268/console [14:47] or post jenkins upgrade [14:47] not sure what the timelines are [14:49] jgdx, that build timed out while running. Looks like the test got stuck after a little more than 20 minutes [14:50] fginther, i see [14:50] jgdx, that explains why there were no test results. As to why the test got stuck, no real idea. [14:51] jgdx, it appears to get stuck when autopilot tries to launch the app [14:52] fginther, too bad there are no artifacts left over === michihenning is now known as michi [14:56] jgdx, yeah. it's hitting the jenkins build timeout which doesn't give the test a chance to cleanup and collect any artifacts. We might be able to improve that. I'll create a task for this and see if someone has a chance to investigate [14:56] fginther, appreciate it. I'll try to figure out why it crashed. [15:29] Mirv: if you're still around i think we can go ahead and publish silo 15 now :) [15:36] dobey: kind of not anymore but I can still do that [15:36] Mirv: it's not? or you're gone for the day? [15:37] I can publish if needed [15:37] dobey: yes, I stop usually 1h ago, if I try to have a free evening. but as you can see I'm still here occasionally :) [15:38] Mirv: no worries, can bug someone else to publish it. go enjoy your evening :) [15:38] sil2100: sure, sure, with your great new powers! :) [15:38] * sil2100 feels so powerful now [15:38] ;) [15:39] Mirv: anyway, go back to enjoying your EOD, I'll review the changes and publish if all is good [15:40] sil2100: I've reviewed them, but now I shall go yes. the new src doesn't need prenewing, as it will actually go to the correct queue. [15:46] sil2100: robru: one more thing, it doesn't seem https://ci-train.ubuntu.com/job/ubuntu-landing-015-2-publish/133/console published the new package qtpurchasing... probably a train bug https://ci-train.ubuntu.com/job/ubuntu-landing-015-2-publish/lastSuccessfulBuild/artifact/packagelist_rsync_ubuntu-landing-015/*view*/ [15:47] sil2100: robru: the two other packages naturally appeared in archives, but the package not included in the rsync file didn't end up in NEW queue. copied manually now. [15:48] hmmm [15:48] I've published new sources before with the train, so this might be due to some of robru's later changes. it tries to debdiff against empty in the log and fails. [15:48] I think we didn publish a new package some time ago already and then it got copied correctly IIRC [15:49] also "WARNING qtpurchasing-opensource-src version 5.6.0~git20151023.2f454143-0ubuntu1 not greater than None, skipping." [15:49] Oho [16:12] jibel, can https://trello.com/c/WnDtwp1e/2518-665-ubuntu-landing-002-webbrowser-app-osomon be updated? the MR has been approved [16:13] oSoMoN, yes, thanks. [16:14] and done === chihchun is now known as chihchun_afk [17:55] jamesh: Approved silo 40 === alan_g is now known as alan_g|EOD [18:31] Mirv, sil2100, indeed that regression is my fault, sorry, will fix shortly [19:43] jhodapp: ^ any minute [19:46] davmor2, yay awesome!! [19:46] davmor2, thanks for testing [19:47] jhodapp: yeah I just tested for regressions and couldn't see any as the current music-app keeps the back and forward buttons disabled [19:47] davmor2, yep that's very good [19:48] davmor2, and it was still determined that any current issues were with music-app dev anyway, so we are good with music-app stable and dev [19:48] \o/ [19:48] kenvandine, you're a core dev right? [19:48] jhodapp, yup [19:48] jhodapp, what can i do for you? [19:48] jhodapp: so is sil2100 [19:48] kenvandine, mind landing silo 9 for us please since it has a source pkg only? [19:49] * kenvandine looks [19:50] lots of packaging changes there... [19:50] reviewing [19:50] kenvandine, yup [19:51] kenvandine, ok thanks, abeato had also reviewed them as well [19:51] kenvandine, also double check that we're ok on the qtmultimedia-opensource-src-gles [19:52] rvr, hey, how is testing of silo 2 going so far? [19:53] oSoMoN: I just started [19:53] oSoMoN: I understand the tab animation must be different [19:53] rvr, it must be much smoother [19:54] kenvandine: man it's only 5000-ish lines it's not like it's a lot ;) [19:54] rvr, perhaps the most visible difference is that the black flash that was happening when switching tabs is now gone [19:54] oSoMoN: Stupid question: is that on the phone, right? [19:55] rvr, yes [19:55] jhodapp, shouldn't one of these packages build dep on the new version of qtmultimedia? [19:55] rvr, actually the black flash was also happening on desktop, and that is fixed with this silo, but the bulk of the improvements concerns the animation on phone [19:56] kenvandine, no since it's a dynamic plugin loaded at run time [19:56] qtubuntu-media [19:56] ok [19:56] good question though! [19:57] i guess it should have been obvious that wasn't the build dep :) [19:57] feels like friday already :-p [19:58] hehe [19:58] indeed it does :) [19:58] oSoMoN: I see, much smoother indeed [19:58] oSoMoN: I'm going to test other things, but that looks good [19:59] rvr, thanks, let me know if anything comes up, I’ll be around for another hour or so [20:23] kenvandine, thanks for landing that [20:29] jhodapp, np === salem_ is now known as _salem === ralsina is now known as ralsina_ === ralsina_ is now known as ralsina === vrruiz_ is now known as rvr [21:38] cihelp: any idea why sudo fails like that [1]? HW failure? [1] http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-touch/4281/console [21:39] jgdx, looking [21:40] fginther, thanks. I just ran the whole suite on my mako, all green :( [21:41] jgdx, it looks like the network failed to connect, but the error message is very confusing [21:44] fginther, seems to have happened before as well.. e.g. http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-touch/4241/console [21:49] fginther, is there a way to just do the autopilot builds, i.e. using a previous set of debs instead of building them every time? [21:50] jgdx, it is possible to just rebuild that job, (http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-touch/4281/rebuild/) [21:50] fginther, but that will rebuild debs [21:50] jgdx, the only downside is that doesn't automatically update the MP with the results [21:50] aah [21:50] okay [21:50] that's fine [21:51] jgdx, that's your quickest workaround to the problem. It may be possible to improve the retry logic for the networking failure, but that obviously doesn't help you right now [21:53] fginther, no issue now that I can rerun the ap jobs directly. Thanks for that === _salem is now known as salem_