=== tyhicks` is now known as tyhicks === plars-off is now known as plars === chihchun_afk is now known as chihchun [06:33] morning [06:45] Hello Mirv, so it seems that there will be no more UITK for OTA9 ... there is an event handling issue with the staging [07:04] bzoltan_: ok then [08:25] good morning everyone [08:26] ubuntu-qa: is silo validation resuming today? I’ve got silo 6 lined up for OTA9 with a number of bug fixes [08:29] I'm not sure if it's starting today or not. I won't be back home and functional for at least 2.5 days. [08:29] oSoMoN, morning. We'll resume landings today [08:29] jibel, excellent, thanks! === davmor2_ho-ho-ho is now known as davmor2 [09:32] jibel: meeting! === alan_g is now known as alan_g|lunch [13:39] jibel: should something in the process be changed so that QA wouldn't start reviewing tickets like https://requests.ci-train.ubuntu.com/#/ticket/821 that are all red because of some arch build failure? before holidays I managed to fix a couple of similar ones with just no-change rebuild of that single arch, but those should be fixed before QA starts working on it. [13:40] I'm trying the s390x rebuild now [13:51] looks like that s390x issue is also solved by rebuild, but sooner or later QA will review some silo that will need additional changes due to breakage === alan_g|lunch is now known as alan_g === chihchun is now known as chihchun_afk [15:19] oSoMoN: ^ [15:19] nice [15:19] davmor2, is 35 next? [15:19] davmor2, cheers mate! [15:20] pmcgowan: look like it [15:20] looking forward to a working phone again [15:21] pmcgowan, yeah it's next in the queue, then we'll try to land 51 again === chihchun_afk is now known as chihchun === josepht` is now known as josepht [16:21] 33 [16:21] oops [16:31] popey: new gallery in store needs to be approved (was approved by QA before the break) [16:31] bfiller, ack === chihchun is now known as chihchun_afk [18:03] hmm, are the "Autopkgtest Results" links on landing requests supposed to be completely useless? :) [18:04] dobey: no, why? what request? [18:05] robru: well anyone i've looked at, they always seem to have tests for packages totally unrelated to the current landings. https://requests.ci-train.ubuntu.com/#/ticket/816 for example has unity-scope-click but the autopkgtest results links show mediascanner2 tests [18:07] dobey: oh apparently you're getting cached results from the previous request assigned in that silo. it doesn't currently update until you set the QA status to 'Ready for QA' [18:07] https://requests.ci-train.ubuntu.com/#/ticket/829 has a trust-store branch only for vivid, and the autopkgtest results link to both xenial and vivid, but for ubuntu-keyboard and the tests being run for ubuntuone-credentials instead [18:08] robru: ah, yeah, that is pretty annoying. can that be fixed? [18:09] dobey: tough to say. one of the long-term goals is to have ephemeral PPAs, which would eliminate this issue, but it's a ways off. [18:09] dobey: I'm not sure why stale results are being added to new requests though... [18:10] robru: when are the autopkgtests being run? [18:11] dobey: for now, you have to set 'Ready for QA' to trigger the autopkgtests to be requested. we'll soon change it so that you can request autopkgtests sooner, and then it only becomes 'Ready for QA' once tests pass, but for now this is the initial iteration [18:18] robru: can they be automatically triggered whenever the build status is "successfully built" instead? [18:20] dobey: i was asked to make them manually triggered as autopkgtest resources are scarce and we don't want them constantly running for every random build that happens [18:20] oh [19:51] woot [20:10] trainguards, can we please publish https://requests.ci-train.ubuntu.com/#/ticket/822 ? [20:11] Saviq: did you try publishing it yourself? [20:11] robru, that never worked for me :) [20:11] * Saviq didn't have rights [20:11] Saviq: it works if there's no packaging diff [20:12] Saviq: you got rights for that months ago [20:12] Saviq: publishing is open to everybody now as long as there's no packaging diff. [20:12] robru, thought there was something else needed, like being a maintainer or so [20:13] robru, wfm then :) [20:13] robru, just replying your email [20:13] Saviq: nope. I no longer have any special publication power that you don't. The only trick is that you need core dev if there are packaging changes [20:14] ack === salem_ is now known as _salem [22:33] robru, I'm missing something obvious (I think) in trying but failing to publish https://requests.ci-train.ubuntu.com/#/ticket/820 [22:33] jhodapp: job hasn't ben run since dec 22nd. [22:34] robru, sorry, wrong one: https://requests.ci-train.ubuntu.com/#/ticket/820 [22:34] jhodapp: it's just like the build job, you click through to jenkins and then run the jenkins job. [22:34] that's the same one [22:34] robru, oops right, looked at the wrong line :) [22:35] robru, yeah when I click through it just brings me back to the same Jenkins job page [22:35] robru, nm, it's working now [22:35] I swear it wasn't working just a min ago :) [22:35] jhodapp: how many times did you try? that's expected once as you start off not logged in, so it logs you in and redirects to the form [22:36] is that why I have to press build twice many times? Any way to fix that so that it logs in and does the build request all in the first click? [22:41] jhodapp: yeah, same reason. no fix that I'm aware of. the sso plugin for jenkins doesn't seem to have any options at all. my preferred solution would be to make the login sessions last at least 12 hours or so rather than the hard-coded value of 4.3 nanoseconds. [22:41] jhodapp: eventually jenkins will go away and this'll all be moot but we're stuck with it for a while yet. [22:42] brb [23:32] robru, ah interesting, that's a bummer that it's not more flexible [23:33] jhodapp: yeah it's been a thorn in my side for years. We have plans to replace it, it'll just take a while to get everything in order [23:34] robru, indeed, bileto and the other things you've done have been a great addition...much appreciated! [23:35] Thanks!