/srv/irclogs.ubuntu.com/2016/05/18/#ubuntu-ci-eng.txt

=== chihchun_afk is now known as chihchun
=== marcusto_ is now known as marcustomlinson_
=== marcustomlinson_ is now known as marcustomlinson
oSoMoNtrainguards, chrisccoulson: the armhf build of oxide for xenial failed again in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-003/+packages (linker was OOM), not sure why, could we do a binary copy of the packages from https://launchpad.net/~oxide-builds/+archive/ubuntu/oxide-next-for-stable-phone-overlay/+packages instead?07:39
oSoMoN(and that would get us an updated version of oxide, too(07:39
chrisccoulsonHmmm, this is bad07:45
sil2100eh07:54
sil2100oSoMoN: the question is - why is it failing so frequently when building in the silo07:54
sil2100oSoMoN: also, I see the version number in the PPA being a bit ugly... I guess we could live with that though07:55
sil2100oSoMoN, chrisccoulson: is that PPA building against the overlay? I suspect it does?07:56
oSoMoNsil2100, yes it does07:57
oSoMoNsil2100, I have no idea why it fails to build in the silo, it used to build just fine07:57
chrisccoulsonsil2100, it's failing because we're exhausting the 32-bit address space07:57
chrisccoulsonwe're on thin ice for all 32-bit builds07:57
sil2100Another problem is, well, I don't remember if we can work-around this but since the PPA binaries have a lower version number, not sure I can put those in the PPA07:59
sil2100I suppose I could try deleting the packages and then copying, but I remember launchpad being fuzzy about such things07:59
bzoltansil2100:  When will you have few minutes to discuss about the ubuntu-sdk meta package corrections in the seed?07:59
=== chihchun is now known as chihchun_afk
bzoltansil2100: ^08:14
sil2100bzoltan: hey! We could hangout tomorrow if needed - could you maybe send me an e-mail with your detailed proposition in the meantime? :)08:19
bzoltansil2100: are morning hours like 9-12 good for you?08:19
=== chihchun_afk is now known as chihchun
sil2100Yeah, 11-12 would be the best I suppose08:21
dbarth_hey guys08:28
dbarth_so we need an archive admin to review the new packages in silo 2108:28
dbarth_ref: https://requests.ci-train.ubuntu.com/#/ticket/121908:28
dbarth_can you help us?08:29
sil2100Oh, slangasek checked them out yesterday, not sure what his final verdict was08:31
* sil2100 tries to check the logs08:31
sil2100dbarth_: ok, we have an ACK08:34
bzoltansil2100:  you have got an invitation with a super detailed description of what we need :)08:34
sil2100Wooo, yeah, love the hangout title ;)08:34
sil2100dbarth_: publishing08:35
=== plars_ is now known as plars
=== tedg_ is now known as tedg
=== robru_ is now known as robru
dbarth_sil2100_: thank you08:51
pstolowskijibel, hello, the autopkg test failure in silo 8 is unrelated to the changes in this silo, it's a flaky unity8 test and ltinkl has a fix for that (https://code.launchpad.net/~lukas-kde/unity8/stabilizeFlakyWizardTest/+merge/293999); can you add this silo to your testing queue?09:05
jibelpstolowski, done09:26
pstolowskijibel, thanks09:26
=== sil2100_ is now known as sil2100
=== jin_ is now known as jin-doctor
rvrpopey: Can you take a look to this? There are three different bug reports (one is mine, just discovered them) https://bugs.launchpad.net/reminders-app/+bug/158216911:38
ubot5Launchpad bug 1582169 in Ubuntu Notes app "Missing translations" [Undecided,New]11:38
=== dobey_ is now known as dobey
=== _salem is now known as salem_
=== john-mca` is now known as john-mcaleely
tedgsil2100: I'm looking at this link, is that all the packages in a xenial image? http://people.canonical.com/~lzemczak/landing-team/xenial-transition/staging.pkglist13:45
dobeytedg: those are source packages, not binary packages13:47
tedgdobey: Hmm, okay, I guess my question was more about "all" than the type :-) There seems to be some missing.13:49
dobeytedg: like what?13:50
tedgdobey: lxcfs13:50
dobeythere's no lxcfs on my mako13:50
tedgdobey: Yes, it only exists in Xenial.13:51
tedgThat's untrue, it did exist earlier.13:51
dobeytedg: you mean it's on the pocket-desktop images?13:51
tedgBut I think it is only needed with lxc 2.0 and libpam-cgfs13:52
tedgdobey: No clue if it's on the pd images. More worried about the android container right now.13:53
dobeytedg: i think that's the list of source packages that are required to build the preinstalled image, as far as is currently known. if some other packages need to be added, then maybe something is wrong in the dependency tree; though i'm not sure how that list was generated exactly13:55
tedgdobey: Yeah, trying to figure out what it is a list of first :-)13:56
tedgCould have other filters applied to it.13:56
dobeylooks like it is just the source packages for what is in the preinstalled image13:58
Saviqjibel, sil2100, pmcgowan, ACK on https://requests.ci-train.ubuntu.com/#/ticket/140913:59
jibelSaviq, silo 68 will trigger a rebuilt of 71?14:08
jibelrebuild*14:09
Saviqjibel, no14:09
jibelok14:09
Saviq68 only has mir, ABI compatible14:09
jibeldavmor2, rvr silo 71 is for OTA11, it'd be great to land it today if possible14:09
dobeysil2100: can you retry the two failed unity8 test builds on https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-047/excuses.html please?14:10
rvrOk14:10
Saviqmterry, can you help dobey ↑ - and we really need to land the flaky fixes...14:11
mterrycimi, ok14:11
mterrywhoops14:11
mterrySaviq, ok  :)14:11
dobeythanks mterry14:14
sil2100Saviq: \o/14:29
sil2100rvr: what's the status of testing 68?14:30
sil2100jibel: I suppose I'll do the triple landing switch once both land, since I already dragged this out till today14:30
rvrsil2100: Tested in frieza, doing a quick check in arale and krillin14:31
sil2100Wanted to have 68 landed, now seeing the other silo ready, well...14:31
slangaseksil2100: my verdict was +1 for it... has anyone published it yet? you didn't give me a link to the silo and I didn't go digging :)15:22
slangaseksil2100: ah, you found that in the logs, great :)15:22
sil2100slangasek: yes, found the logs and published :)15:23
sil2100Thanks!15:23
Saviqrvr, are you ok with duping your mouse bug to bug #1521518 ?15:29
ubot5bug 1521518 in ubuntu-ui-toolkit (Ubuntu) "No way to invoke OSK when a hardware keyboard is connected" [Undecided,Triaged] https://launchpad.net/bugs/152151815:29
Saviqah there's ubot515:29
* rvr reads15:30
rvr"The login screen is not usable with mouse connected" Exactly this.15:30
rvrSaviq: Yup15:30
Saviqhmm I wonder15:31
Saviqnope15:31
Saviqrvr, we really can't do anything automagically, as if we fix this, then we could break kbd + touchpad combos15:31
Saviqif we said we ignore keyboards on mice15:31
rvrsil2100: Saviq: Silo 68 approved15:48
sil2100\o/15:49
sil2100Publishing15:49
=== chihchun is now known as chihchun_afk
robruslangasek: hey I'm a little bit blocked, can you take a look at the email I sent last night?16:03
slangasekrobru: it'll be later this morning16:04
renatutrainguards, why silo 36 is saying "Automated SignoffFailed". Where I can check the reason?16:14
robrurenatu: click excuses16:15
robrurenatu: unity8 regression in vivid16:16
renaturobru, ok then we need to wait unitl it get fixed. Right?16:17
robrurenatu: no, you need to investigate if the failure is caused by your branch and then either fix it yourself, or if not, just ask qa to override the failure and review anyway16:18
tedgsil2100: How does this list get built? http://people.canonical.com/~lzemczak/landing-team/xenial-transition/staging.pkglist16:19
sil2100tedg: a script is scanning all packages in the touch armhf manifests and checks if arm64 binaries are present - if not, it tries to determine the reason why they're not there16:19
sil2100Ah16:19
sil2100Wait16:19
sil2100You mean the pkglist16:19
sil2100tedg: so that's basically the first part of the thing I mentioned above16:20
sil2100i.e. runs through the armhf manifest and fetches the source-package names for each binary we have in the manifest16:20
tedgsil2100: Is it looking at the vivid manifests? I think it should have lxcfs from libpam-cgfs?16:21
sil2100tedg: no, it's xenial16:21
tedgsil2100: Can you point me to the xenial armhf manifest?16:21
sil2100tedg: staging is xenial based16:21
tedgsil2100: It seems that libpam-cgfs is here, but lxcfs (it's source package) isn't in the migration list: http://cdimage.ubuntu.com/ubuntu-touch/xenial/daily-preinstalled/current/xenial-preinstalled-touch-armhf.manifest16:25
sil2100Yeah, it should be, I see it in the output of my script here as well16:26
sil2100Let me double check the scrip instance16:26
sil2100tedg: anyway, trying to see why I get different script output locally on my PC and on the remote instance - for now I put the output I generated16:32
tedgsil2100: Cool, it solves my problem, I was worried we didn't have it in the image, but it seems to be there.16:33
sil2100Yeah, well, it should be since the binaries were always there16:33
sil2100Dunno what happened16:34
=== nuclearbob is now known as nuclearbob_afk
sil2100jibel, rvr, davmor2: how far is silo 71 testing?17:07
davmor2sil2100: it is being tested17:09
dobeyhttps://autopkgtest.ubuntu.com/request.cgi?release=vivid&arch=amd64&package=unity8&trigger=unity-scopes-shell%2F0.5.7%2B15.04.20160516-0ubuntu1&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2Flanding-047 <- sigh17:13
=== jhodapp_ is now known as jhodapp
dobeymterry, kenvandine: if you're around, would you mind? https://autopkgtest.ubuntu.com/request.cgi?release=vivid&arch=amd64&package=unity8&trigger=unity-scopes-shell%2F0.5.7%2B15.04.20160516-0ubuntu1&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2Flanding-04718:07
kenvandinedobey, sure18:11
dobeykenvandine: thanks18:12
kenvandinedobey, done18:12
=== salem_ is now known as _salem
=== _salem is now known as salem_
mterryrobru, it would be neat if the "Merge Proposal URLs" section allowed comments (like with #)20:58
mterryrobru, (in citrain)20:58
robrumterry: hmmm20:59
robrumterry: probably not workable, because the train re-sorts the order of the MPs based on prereqs, and I have a massive overhaul branch which actually saves the new order back to the ticket so you can see what order is actually used. so even if it supported comments they'd be lost after the reordering.21:01
mterryrobru, ew :(  I know in u8 silos, we actually like ordering them conceptually -- like all the u8 branches together, sometimes sorted by owner.  Or for a silo I'm working on now, I have a section at the top that includes the content of a whole other silo that will land before mine, so that I can test for conflicts and such21:02
mterryrobru, if the train reordered those on me, it would be a big pain21:03
=== salem_ is now known as _salem
robrumterry: if you don't define prereqs, or if you put them in order of prereqs anyway, then the ordering is stable.21:03
mterryrobru, yeah... but that's not going to happen all the time21:04
robrumterry: anyway the reordering has been in production for 3 years, so it obviously hasn't been a problem for you. the new bit is that it saves the ordering back to the ticket so you can see what order is actually being used. that was a complaint some people had, they couldn't see the result of the sorting.21:04
mterryrobru, yeah I get the complaint.  I don't share it and the new way will bum me out is all21:05
mterryrobru, see https://requests.ci-train.ubuntu.com/#/ticket/1426 for example21:05
mterryrobru, top section is other silo21:05
robrumterry: I don't think this is a problem? you're asking to be able to have one branch define a prereq but then merge the dependant branch before the depended-upon branch?21:05
mterryrobru, and I've had to stuff comments about MPs I am consideringn for the silo but not adding in the Description instead of the Merge URLs section like I would want (if we had comments)21:06
mterryrobru, no no, I just want the order of the Merge URLs section not to change visibly  :)21:06
mterryBut it sounds like other people are asking for the exact opposite21:06
robrumterry: fight it out with dobey, he was the one who complained that the train was changing the order of his MPs and he wanted to see the order the train was using.21:07
mterryit's especially annoying because this reordering would seemingly stop an obviously useful feature (comments)21:08
robrumterry: you're the first person to ask for comments in the 3 years I've been maintaining this.21:08
mterryDoesn't mean I'm wrong  :)21:09
mterrydobey's the first person in three years to ask for reordering  :)21:10
robrumterry: file a bug I guess, perhaps there's some way that it can display the results of the sort in the log instead of in the ticket.21:10
robrumterry: no no it's been reordering all along. dobey just wants to see it21:10
mterryI know21:10
mterryI  meant the first person to ask for visible reordering21:10
dobeydo what?21:11
mterrydobey, you wanted to see the order of the MPs in citrain after it resorts them21:12
mterryapparently21:12
robrudobey: this was a while back, you had a merge conflict in a silo and you couldn't reproduce it locally, train was merging in a different order than you expected.21:12
robrudobey: so I'm working on a big overhaul of the train here, one of the sexy new features is that it saves the result of the sort back to the ticket, so you can see the order it merges in.21:13
dobeyoh right21:13
dobeymterry: well it's not a problem to change the ordering for the unity8 silos, because you can't have prerequisties on branches for other projects in launchpad21:13
dobeyie, you can't have a unity-scopes-shell branch with a prereq on a unity8 branch that has a prereq on uitk or something21:14
mterrydobey, yeah maybe.  Depending on whether we have an interesting internal sorting.  But see https://requests.ci-train.ubuntu.com/#/ticket/1426 where I have multiple u8 sections (because one is a copy of another silo)21:14
mterrydobey, also apparently it means we'll be unlikely to add the ability to have comments in that field21:15
dobeycrikey that's a lot of MPs21:15
mterrydobey, we're running a backlog21:15
dobeywell comments in that field makes no sense21:15
mterryheh, that's judgy21:15
robrudobey: why not? I can sort of see the value in having groups of MPs with little notes about them.21:15
mterrydobey, see the end of the Description field for that silo?  It would be nice to have those in the MP field instead21:16
mterryAnd be able to comment/uncomment MPs individually if they're being added/removed from the silo21:16
dobeyrobru: because the implementation isn't designed that way. comments would make sense if it were a actually a list of things, rather than a text field that is treated as a list, so that you could comment on individual items in the list, or select multiple; ie, like a google spreadsheet does21:17
mterrySo dobey would never use comments, fine.  I would21:18
robrumterry: also I hadn't considered commenting out MPs as a temporary thing, hm21:18
dobeymterry: i didn't say i would never use comments. i said wedging more and more features into a single text field only makes things more complex and a pain to maintain21:18
robrudobey: "line.split('#')[0].strip()" isn't so bad really.21:19
mterryrobru, yeah that's what I want comments for -- commenting out MPs and saying a blurb about why21:19
mterryrobru, maybe sorting order doesn't matter, I could live with all comments having to be on same line?21:19
robrumterry: initially I thought you meant like having a little comment header before each section of MPs21:19
mterryrobru, I mean I could imagine that being useful too21:19
dobeyrobru: well, sorting doesn't preclude having #-comments21:19
robrudobey: the new thing is that it takes the sorted list and dumps it back into the field, overwriting what's there, so you'd lose comments21:20
dobeyrobru: just maintain comment position relative to the thing below it, when reordeering21:20
dobeyrobru: gettext does it, you can too :)21:20
mterryAnd I'm still against reordering on other grounds.  :)  It would make it harder for me to organize branches on silos like this21:20
mterry*now* you want fancy features for the text field  :)21:21
robrudobey: I don't see how that would work, because it changes the order of stuff, so you might have a comment preceding a paragraph, but after sorting there'd be one mp, then a comment, then a bunch more. it'd look weird.21:21
dobeyrobru: no more weird than /etc/apt/sources.list looks by default21:22
dobeymterry: i don't want fancy features for a text field. just suggesting possible compromise21:22
dobeymterry: i still think this is pretty hacky :)21:23
mterryI'm betting I'm not the only person that has weird organizations of the field.  It should be simple to grep all silo jobs and see if there are interspersed groupings of MPs (like u8 MPs, followed by qtmir MPs, followed again by u8 MPs).  Any instances of that would be (presumed-by-me) annoyed by reordering21:23
mterrydobey, well I want no modifications of that field ever.  That's my push21:23
robrumterry: yeah I've seen groupings before, eg where one feature must be implemented in several projects simultaneously, you'll see the "foo-feature" branches for u8 + mir + whatever, then the "bar-feature" branches for the same projects in a second stanza21:24
robrumterry: can you file a bug against lp:bileto? just say you want comments ignored and to have the field preserved. I guess the sorted order can be printed in the logs.21:25
dobeyanyway, i'm not adamant about it either way. my issue was that train was doing something unexpected, and created a weird merge conflict issue that was a bit hard to figure out, because it's hard to see what exactly the train is doing at that point, with minimal verbosity21:26
mterryrobru, ok will file21:26
dobeythe weird parsing of URLs makes the request page a bit hard to read anyway, especially when there are that many branches21:27
mterryrobru, https://bugs.launchpad.net/bileto/+bug/158335221:28
ubot5Launchpad bug 1583352 in Bileto "Support comments in the merges list" [Undecided,New]21:28
robrumterry: thanks21:28
mterryrobru, despite me sounding strident, this is not a life or death feature  :)21:29
robrudobey: noooooo the url shortening makes it easier to read! spaces instead of slashes and underscores removes a ton of punctuation21:29
robrumterry: yeah it'll have to wait a bit, I'm trying to land a massive overhaul, really brutal branch here. 3k lines!21:30
mterryrobru, :)21:30
mterryrobru, sounds good!21:30
dobeyrobru: just translate it to german then. it'll remove all the spaces too!21:30
mterryooh yeah.  /me files bug21:32
=== nuclearbob is now known as nuclearbob_afk

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