/srv/irclogs.ubuntu.com/2015/09/10/#ubuntu-ci-eng.txt

=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
Mirvmornings04:29
oSoMoNubuntu-qa: good morning, is there an ETA for silo 23 validation?07:38
mzanettitrainguards, in bileto I can't find the link to the adt results if something is hanging in the proposed pocket, can you point me to it?07:55
robrumzanetti: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html07:57
mzanettirobru, good morning07:57
mzanettirobru, in the dashboard, the link would directly bring me to the packages I'm trying to land. can we have that back in bileto?07:58
robrumzanetti: yeah, please file a bug about this in lp:bileto07:58
robru(1am here, I'll get to it tomorrow)07:59
Mirvmzanetti: true, that would be useful08:09
mzanettiMirv, hey, looking at unity8/qtmir adt logs but don't really understand what's going wrong. bootest has some issue. have you seen this before?08:10
jibeloSoMoN, likely today08:11
oSoMoNjibel, cool, thanks!08:11
Mirvmzanetti: I don't know what's the current status of boottests, they have had non landing related problems in the past. but seeing that the latest unity8 job was started by francis manually, at least they have been looking at it. let's ping ci_help if they can understand about the boottests more. all I see is that adt-run was Killed in the log.08:15
mzanettiah ok... so you would agree that it rather looks like a system failure than some real regression in the branches we're trying to land?08:16
Mirvogra_: it seems there was some action on wily image side this morning? (I see 20150910.changes, although empty)08:16
Mirvmzanetti: I'd say there's no reason to assume there's something wrong in the landing before we know more.08:16
Mirvmzanetti: and probably highly likely it's a system failure08:16
mzanettiok :)08:17
Mirvoh, I didn't ping cihelp. now I did :) unity8/qtmir boottest failures.08:17
psivaaMirv: now, you have :)08:18
Laneyis it okay to upload livecd-rootfs and lxc-android-config to wily and then spin an image?08:24
Laneyor is there some better way to QA changes to this?08:25
MirvLaney: ogra_ knows a trick to test at least the latter, but not sure about livecd-rootfs. note that lxc-android-config just joined the train, so landing via MP preferable.08:35
Mirvand hmm the previous landing is stuck in proposed similar to unity8/qtmir08:36
Laneygood old boottest08:36
oSoMoNogra_, or anyone familiar with how touch images are built, it looks like oxide 1.8.4 from the overlay PPA takes precedence over oxide 1.9.1 that is in the -security and -updates pockets, how can we ensure that the images get the latest version? Does this require a seed update, or copying oxide to the overlay PPA?09:17
oSoMoN(note that we should wait for oxide 1.9.2 to be out in any case, as 1.9.1 has a critical issue that breaks all webapps)09:17
=== chihchun_afk is now known as chihchun
MirvoSoMoN: you will need to land to overlay PPA. overlay PPA "always wins", so that a normal 15.04 update can't break touch image. only packages that are not in overlay PPA at all get automatic updates from 15.04.09:36
MirvoSoMoN: so in this case for example webapps didn't get broken :)09:36
MirvoSoMoN: QA will also want to verify it normally09:37
oSoMoNMirv, ok, thanks09:37
Mirvheh, right, that needs fixing09:46
Mirvfinally, done09:51
=== chihchun is now known as chihchun_afk
=== alan_g is now known as alan_g|lunch
mzanettiMirv, do you know whom to ping about the boottest issue?12:09
mzanettioh... I just see you (accidentally) did already :)12:11
Mirvmzanetti: my best guess would be fginther since he was poking the jobs yesterday12:15
Laneydo you mean lxc-android-config?12:17
MirvI guess he means unity8/qtmir boottest failures12:21
=== cwayne-afk is now known as cwayne_
=== alan_g|lunch is now known as alan_g
mzanettiLaney, sorry, missed that, yes. I mean unity8/qtmir boottest12:53
pstolowskirobru, hey, what's the issue with silo 10? is it just upload permission problem now?12:59
jibelfginther, do you know why http://d-jenkins.ubuntu-ci:8080/view/Wily/view/BootTest/job/wily-boottest-apport/19/ fails13:01
jibelcihelp ^13:01
rvrkenvandine: Approving silo 913:33
kenvandinervr, thx13:33
fgintherjibel, looking13:53
rvroSoMoN: bzoltan: In silo 23 (ui-toolkit), there is also a modification to webbrowser-app, anything special to check?14:21
oSoMoNrvr, only that context menus work as expected (they are dismissed when clicking an action), and that autopilot tests all pass14:29
rvr1. The webbrowser-app failures were all caused by the the direct usage of AbstarctButton object type from the AP tests.14:29
rvrThe https://code.launchpad.net/~bzoltan/webbrowser-app/UCAbstractButton/+merge/270369 patch fixed it and the browser.sh/browser.logs provides the extra tests.14:29
rvrNice14:31
=== alan_g is now known as alan_g|afk
=== nik90 is now known as nik90|AFK
jhodappdavmor2, is there a delay between marking something as ready for QA in bileto until it shows up in the QA Trello board?15:25
jibeljhodapp, 10 minutes max15:26
jibeljhodapp, which ticket?15:26
jhodappjibel, ok, I just marked silo 55 as ready for QA15:26
jhodappjibel, I want to make sure whomever ends up testing it speaks with me first before testing it...there's some specifics they need to know about first15:27
robrujhodapp: that's what the Test Plan field is for ;-)15:27
jhodapprobru, yes indeed, but there's more to it than that for this one :)15:28
jibeljhodapp, you can add a comment in bileto, most of the time the person doing the verification reads it :)15:28
jhodappyeah I did, but I insist, they really need to speak with me15:28
=== alan_g|afk is now known as alan_g
pstolowskirobru, hello, have you seen my earlier query?15:36
robrupstolowski: no, what?15:36
rvrmzanetti: The "reboot" button in the power dialog is now grey instead of green. Do you know who can confirm that's intended and not a regression?15:38
pstolowskirobru,  what's the issue with silo 10? is it just upload permission problem now? all good with packaging?15:39
fgintherMirv, robru, in case anybody asks, the devices used for boottest have gone into a bad state and need to be manually recovered. A handful of recent tests failed because if the device problems and will be retested once the devices are working again. Let us know if there are any packages that need priority.15:39
robrufginther: thanks15:40
robrupstolowski: it needs packaging ack15:40
=== fginther changed the topic of #ubuntu-ci-eng to: Train trouble? ping trainguards | CI problems? ping cihelp | Train: http://bit.ly/1hGZsfS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: OTA-6 final freeze in effect, but the vivid-overlay landing gates opened. sil2100 away, small trainguard gap between EEST & RDT (robru daylight saving time) timezones, boottest devices have fallen over - test failures will be retried
robrukenvandine: if you're around can you ack & publish this one? https://ci-train.ubuntu.com/job/ubuntu-landing-010-2-publish/79/ thx15:40
pstolowskirobru, k, thanks15:41
robruyou're welcome15:41
kenvandinerobru, looking15:42
robruthanks15:43
=== nik90|AFK is now known as nik90
kenvandine-Package: libunity-scopes1.015:44
kenvandine+Package: libunity-scopes315:44
kenvandinewith no replaces/conflicts for libunity-scopes1.015:44
kenvandinewhich exists in wily15:44
kenvandinenot sure about that15:44
bzoltanrvr: oSoMoN: the AP tests I have copied to the usual place .. all good15:45
kenvandineis that package in the overlay?15:45
rvrbzoltan: Great15:45
rvrkenvandine: Yesterday I approved a unity-scopes-api silo15:46
kenvandineso the libunity-scopes1.0 binary is in the overlay ppa?15:47
kenvandineah, no it isn't15:47
mzanettirvr, that's intended. there was a bug that the old one was looking like a "tricolor", so design took out some colors15:48
rvrmzanetti: Cool, thanks!15:48
kenvandinerobru, it's a nack from me15:49
kenvandinerobru, there needs to be a replaces/conflicts for the binaries that landed in wily that aren't built anymore15:49
robrukenvandine: ok, thanks15:49
kenvandinehttps://launchpad.net/ubuntu/+source/unity-scopes-api/1.0.1+15.10.20150826-0ubuntu115:50
kenvandinethere are a few binaries in wily that aren't in this package15:50
rvroSoMoN: The font size of the context menu looks small in arale16:02
pstolowskikenvandine, hey, can you give an example? do you mean e.g. libunity-scopes-qt0.1 vs libunity-scopes-qt0.2_1.0.1 ?16:06
rvrbzoltan: oSoMoN: Approving silo 2316:06
robrubregma: uh? why doesn't 41 need QA? it's dual16:06
bregmait's also not used in any image16:07
robruhm16:07
robruok16:07
robrukenvandine: here's a simpler one if you can please ;-) https://ci-train.ubuntu.com/job/ubuntu-landing-041-2-publish/12/16:08
robrukenvandine: and another one? ;-) https://ci-train.ubuntu.com/job/ubuntu-landing-023-2-publish/39/16:10
bzoltanwow robru is not authorized?16:13
robrubzoltan: new rules16:14
robruI am powerless16:14
bzoltanrvr:  cool, thank you16:14
bzoltanrobru:  I told you to be nice and kind :)16:14
robrubzoltan: I can only upload if there's no packaging diff, "not authorized" is the new "packaging changes need manual ack"16:14
bzoltanrobru: I see... we need a jedi for that16:15
robrubzoltan: yes. I pinged kenvandine but he's a bit swamped I'm sure16:16
rvrjgdx: Silo 15 has a merge proposal which needs review16:18
jgdxrvr, which one?16:18
jgdxon my list all of them are approved16:19
rvrjgdx: https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/allow-insecure-hotspot/+merge/26967116:19
rvrjgdx: But I see it was already approved16:19
fgintherSaviq, anpok, does the unity8 currently in proposed-migration require mir updates? The unity8 boottest is failing because the shell doesn't come up (but it is possible to adb shell in). It does work installing everything from the -proposed pocket16:32
kenvandinerobru, sure, i'll look16:35
bzoltankenvandine:  thank you!16:36
kenvandinerobru, ^^ what's that exception?16:43
robrukenvandine: uh16:46
robrukenvandine: can you try it again? that shouldn't happen16:47
kenvandineexceptions should never happen :)16:47
robrukenvandine: I just did a rollout, maybe you caught something halfway16:48
kenvandinerobru, boom16:48
bzoltanrobru: kenvandine: thank you boys :) good job16:48
robrukenvandine: oh, well the test plan field is empty in bileto ;-)16:48
robruodd, that error should be printed nicer than that16:48
kenvandinebzoltan, np16:49
robruhang on a second guys, disk issue16:49
kenvandinerobru, well i acked the packaging changes... let me know if you need me to publish it later16:50
robrukenvandine: yeah I will16:52
kenvandinethx16:52
robrukenvandine: ok can you publish now?16:54
robrubfiller: sorry, in the middle of a rollout, hold off for a sec and retry a bit later16:56
bfillerrobru: ok16:57
robrubfiller: ok I retried it: https://ci-train.ubuntu.com/job/ubuntu-landing-046-1-build/71/consoleFull16:58
robruhopefully that one works16:58
pmcgowanjibel, is someone grabbing silo 55? very anxious for that one16:59
kenvandinerobru, i can try16:59
robrukenvandine: it should work now17:00
kenvandinerobru, seems to be working17:03
robrukenvandine: seems to be stalled, oh god what have i done17:04
=== alan_g is now known as alan_g|EOD
robrukenvandine: it's stuck at "writing packagelist", which should be done in microseconds, it literaly just writes a short text file. the fact that it's been running for over 4 minutes is horrifying17:05
robrukenvandine: can you cancel it and try again17:05
robruhopefully that's just some kind of fluke, because I didn't really change that part of the code... also if there was a bug there it should just raise an exception, I can't imagine why it would block like that17:06
robrukenvandine: can you publish with DEBUG checked?17:06
robrukenvandine: or apparently it's fine17:07
robrukenvandine: nm about retrying, thanks for your patience17:08
awe_robru, when you get a chance could you take a peek at the latest build failure for ofono?17:10
awe_https://requests.ci-train.ubuntu.com/#/ticket/33817:10
robruawe_: bash: ./debian/rules: Permission denied17:11
awe_yea, trying to figure out how that happened17:11
awe_the permissions didn't get changed17:12
awe_they're the same in the trunk branch and mp17:13
robruawe_: I just branched your branch and the debian/rules file is not executable. I don't know how it happened but you're going to want to chmod 755 it17:13
awe_that said, the executable bit isn't set, so maybe an update on the builder side caused this to get caught?17:13
awe_ok, will update it17:13
awe_maybe it got changed in the last update17:14
robruawe_: I dunno, if it worked before without being set executable that's a fluke, debian/rules is expected to be executable17:14
awe_ack17:14
awe_thanks17:14
robruawe_: you're welcome17:14
bzoltanrobru:  would you be so kind to assist thesilo35's landing?18:06
robrubzoltan: you're trying to merge it before it's landed?18:06
bzoltanrobru: :D yes18:07
robrubzoltan: generally that's not recommended but if you want to do that you need to check FORCE to skip the version check18:07
bzoltanrobru:  actually i would prefer to properly land it first18:08
robrubzoltan: so what's stopping you from landing properly?18:08
bzoltanrobru: "bzoltan is missing the Job/Build permission"18:09
robrubzoltan: on what job?18:09
bzoltanrobru: https://ci-train.ubuntu.com/job/ubuntu-landing-035-2-publish/build18:10
robrubzoltan: So what you're really trying to say is that you want me to publish the silo?18:10
bzoltanrobru: Yes :) Sorry  for confusing18:11
robrubzoltan: ok, we'll see if I can18:11
robrubzoltan: ok, should be good to go then18:19
awe_robru, ofono failed again... this time it's a single unit test failing on wily for 5/6 arches;  I can't reproduce the failure using a wily sbuild.  Is there any way to get at other build artifacts in a PPA ( eg. the file test-suite.log )?18:26
robruawe_: uh, I don't have any special access to the PPA, but if there's a file generated in the source tree at source-package-build-time I might be able to fetch it from jenkins.18:27
robruawe_: what's the file called?18:27
awe_test-suite.log18:27
robruawe_: in the source root?18:27
awe_nah, it's generated during the binary build18:28
awe_this is gonna be a fun one ot find18:28
awe_s/ot/to/18:28
robruawe_: yeah you'd have to change your packaging to include that file in a deb to be able to get it from the PPA then. or maybe ping a launchpad person to poke at that18:28
awe_k, thanks18:28
robruawe_: you're welcome18:28
bzoltanrobru:  thank you .. there were so many automatization recently :) that i almost thought that I can trigger a publishing process and then the trainguards just need to ack it :)18:41
robrubzoltan: that may happen one day soon... it's all coming together18:41
robrukenvandine: another packaging ack pls? ^ ;-)18:47
kenvandinerobru, looking18:49
robruthanks18:49
kenvandinerobru, done18:51
robrukenvandine: great, thanks18:51
kgunntrainguards unity8 seems stuck in proposed still from silo14, is that still being worked...see bootest retry but manually aborted18:52
robrufginther: ^^ boottest love?18:52
fgintherkgunn, I posted a question about unity8 to Saviq and anpok earlier. Tested by itself, the UI does not come up when testing unity8. It does work when the rest of silo 14 is added.  Is that expected and will these all migrate together?18:58
kgunnfginther: yes, all of silo14 needed to go together18:59
fgintherkgunn, thanks, I'll get them unblocked then19:00
kgunnfginther: thank you!19:02
kgunnoh and yeah Saviq is on vacation19:02
=== ahayzen_ is now known as ahayzen
jhodapprobru, is it possible to have a silo depend on another for building - e.g. silo A has a package that silo B needs as a prereq to build, but it's not appropriate to put the MRs for B into A21:04
robrujhodapp: it may be possible with manual futzing but I'd have to check into that. Why aren't the MPs appropriate in the same silo? Sure sounds like it should all be in the same silo if it depends on the other to even build.21:08
jhodapprobru, well they only depend on each other because the version number got bumped because of an interface change21:09
jhodapprobru, but that's the only relationship they have, they definitely belong in separate landings21:09
robrujhodapp: what makes you think they are definitely separate? There isn't a limit on how big a silo can be.21:10
robruHah21:12
jhodapprobru, because one silo has a scope of fixing MPRIS only which is what bumped the version number, and the other has nothing to do with MPRIS21:12
jhodappcould they technically land together, sure, but functionally it'd be inappropriate21:13
robrujhodapp: so the thing is, I can add PPA dependencies the way you describe, but it's quite a manual thing, it's not something you can define in the request.21:15
robrujhodapp: and then it becomes super important for me to remember to undo that change when you're done21:15
jhodapprobru, yeah not a huge deal and I know it's a niche circumstance, but was curious enough to ask :)21:15
jhodappas soon as silo 55 lands this is a non-issue21:15
robrujhodapp: so generally it's gonna be a lot easier (for me, heh) if you just put them in the same silo, or land one and wait for it to complete before building the second21:15
jhodapprobru, I blame davmor2 ;p21:16
jhodapphe needs to hurry up and test silo 5521:16
robruah, qa ;-)21:16
robrujhodapp: oh, I suppose an easier thing would be to just copy the necessary packages from the original silo into the new silo, and then delete them later before publishing21:19
robruthen I don't have to remember to undo PPA changes.21:19
robrujhodapp: lemme know if you want me to do that, what packages from what silo to what silo21:20
=== ahayzen_ is now known as ahayzen

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