robruErrr mah gerd01:05
=== _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
seb128cihelp could you help me to understand https://jenkins.qa.ubuntu.com/job/indicator-keyboard-15.04-vivid-amd64-ci/3/console ?08:38
seb128"bzr: ERROR: Permission denied: "Cannot create '15.04'. Only Bazaar branches are allowed.""08:38
seb128what's the issue?08:38
seb128that's the CI on https://code.launchpad.net/~seb128/indicator-keyboard/use-new-gee/+merge/27855208:38
seb128also why is it trying to use 15.04?08:38
psivaaseb128: i'll take a look at that error09:03
seb128psivaa, hey, thanks09:03
psivaaseb128: this is occurring since the target branch for vivid builds have been marked as lp:indicator-keyboard/15.0409:26
psivaaseb128: this is inline with all the projects in http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/revision/1261#stacks/vivid/indicators.cfg09:26
psivaafor e.g. indicator bluetooth: https://code.launchpad.net/~indicator-applet-developers/indicator-bluetooth/trunk.15.0409:27
seb128psivaa, where is the vivid coming from?09:27
seb128psivaa, we land to xenial by default it's a desktop project09:27
=== joc|away is now known as joc_
psivaaseb128: 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 obtained09:30
psivaaline 66, is the relevant one09:31
seb128psivaa, l67 states trunk should build against wily09:37
seb128psivaa, l66 is lp:indicator-keyboard/15.04 but that branch doesn't even exist09:44
seb128we have just trunk09:44
psivaaseb128: we could just remove the lp:indicator-keyboard/15.04 part if that does not exist09:45
seb128psivaa, +109:46
psivaaseb128: ack, thanks. will work on it09:46
robrucihelp 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:19
psivaarobru: will give that a look in a little bit10:21
robrupsivaa, thanks10:21
robrupsivaa, oh nm that might be a false positive, there's a test failure hiding further up the log10:23
robrupsivaa, yeah, sorry for the noise, that's all me10:27
psivaarobru: ack, thanks10:27
jgdxcihelp: 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:20
fgintherjgdx, 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:27
fgintherjgdx, 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
jgdxfginther, okay, thank you14:28
jgdxfginther, what about ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? ?14:47
fgintherjgdx, looking14:47
jgdxit's new, seems to have happened post krillin migration14:47
fgintherjgdx, oh, do you have an example?14:47
jgdxfginther, https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-touch/4268/console14:47
jgdxor post jenkins upgrade14:47
jgdxnot sure what the timelines are14:47
fgintherjgdx, that build timed out while running. Looks like the test got stuck after a little more than 20 minutes14:49
jgdxfginther, i see14:50
fgintherjgdx, that explains why there were no test results. As to why the test got stuck, no real idea.14:50
fgintherjgdx, it appears to get stuck when autopilot tries to launch the app14:51
jgdxfginther, too bad there are no artifacts left over14:52
=== michihenning is now known as michi
fgintherjgdx, 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 investigate14:56
jgdxfginther, appreciate it. I'll try to figure out why it crashed.14:56
dobeyMirv: if you're still around i think we can go ahead and publish silo 15 now :)15:29
Mirvdobey: kind of not anymore but I can still do that15:36
dobeyMirv: it's not? or you're gone for the day?15:36
sil2100I can publish if needed15:37
Mirvdobey: 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:37
dobeyMirv: no worries, can bug someone else to publish it. go enjoy your evening :)15:38
Mirvsil2100: sure, sure, with your great new powers! :)15:38
* sil2100 feels so powerful now15:38
sil2100Mirv: anyway, go back to enjoying your EOD, I'll review the changes and publish if all is good15:39
Mirvsil2100: 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:40
Mirvsil2100: 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:46
Mirvsil2100: 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:47
MirvI'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
sil2100I think we didn publish a new package some time ago already and then it got copied correctly IIRC15:48
Mirvalso "WARNING qtpurchasing-opensource-src version 5.6.0~git20151023.2f454143-0ubuntu1 not greater than None, skipping."15:49
oSoMoNjibel, can https://trello.com/c/WnDtwp1e/2518-665-ubuntu-landing-002-webbrowser-app-osomon be updated? the MR has been approved16:12
jibeloSoMoN, yes, thanks.16:13
jibeland done16:14
=== chihchun is now known as chihchun_afk
rvrjamesh: Approved silo 4017:55
=== alan_g is now known as alan_g|EOD
robruMirv, sil2100, indeed that regression is my fault, sorry, will fix shortly18:31
davmor2jhodapp: ^ any minute19:43
jhodappdavmor2, yay awesome!!19:46
jhodappdavmor2, thanks for testing19:46
davmor2jhodapp: yeah I just tested for regressions and couldn't see any as the current music-app keeps the back and forward buttons disabled19:47
jhodappdavmor2, yep that's very good19:47
jhodappdavmor2, and it was still determined that any current issues were with music-app dev anyway, so we are good with music-app stable and dev19:48
jhodappkenvandine, you're a core dev right?19:48
kenvandinejhodapp, yup19:48
kenvandinejhodapp, what can i do for you?19:48
davmor2jhodapp: so is sil210019:48
jhodappkenvandine, mind landing silo 9 for us please since it has a source pkg only?19:48
* kenvandine looks19:49
kenvandinelots of packaging changes there...19:50
jhodappkenvandine, yup19:50
jhodappkenvandine, ok thanks, abeato had also reviewed them as well19:51
jhodappkenvandine, also double check that we're ok on the qtmultimedia-opensource-src-gles19:51
oSoMoNrvr, hey, how is testing of silo 2 going so far?19:52
rvroSoMoN: I just started19:53
rvroSoMoN: I understand the tab animation must be different19:53
oSoMoNrvr, it must be much smoother19:53
davmor2kenvandine: man it's only 5000-ish lines it's not like it's a lot ;)19:54
oSoMoNrvr, perhaps the most visible difference is that the black flash that was happening when switching tabs is now gone19:54
rvroSoMoN: Stupid question: is that on the phone, right?19:54
oSoMoNrvr, yes19:55
kenvandinejhodapp, shouldn't one of these packages build dep on the new version of qtmultimedia?19:55
oSoMoNrvr, 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 phone19:55
jhodappkenvandine, no since it's a dynamic plugin loaded at run time19:56
jhodappgood question though!19:56
kenvandinei guess it should have been obvious that wasn't the build dep :)19:57
kenvandinefeels like friday already :-p19:57
jhodappindeed it does :)19:58
rvroSoMoN: I see, much smoother indeed19:58
rvroSoMoN: I'm going to test other things, but that looks good19:58
oSoMoNrvr, thanks, let me know if anything comes up, I’ll be around for another hour or so19:59
jhodappkenvandine, thanks for landing that20:23
kenvandinejhodapp, np20:29
=== salem_ is now known as _salem
=== ralsina is now known as ralsina_
=== ralsina_ is now known as ralsina
=== vrruiz_ is now known as rvr
jgdxcihelp: 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/console21:38
fgintherjgdx, looking21:39
jgdxfginther, thanks. I just ran the whole suite on my mako, all green :(21:40
fgintherjgdx, it looks like the network failed to connect, but the error message is very confusing21:41
jgdxfginther, seems to have happened before as well.. e.g. http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-vivid-touch/4241/console21:44
jgdxfginther, 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:49
fgintherjgdx, 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
jgdxfginther, but that will rebuild debs21:50
fgintherjgdx, the only downside is that doesn't automatically update the MP with the results21:50
jgdxthat's fine21:50
fgintherjgdx, 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 now21:51
jgdxfginther, no issue now that I can rerun the ap jobs directly. Thanks for that21:53
=== _salem is now known as salem_

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