[00:42] <robru> omg I'm so sorry for all the spam today guys I promise this'll settle down son
[00:42] <robru> soon
[09:07] <sil2100> jibel, davmor2, rvr: hey! How did the auto-testing of the new rc image go>
[09:08] <davmor2> sil2100: no idea
[09:09] <jibel> sil2100, it's okay, I re-ran most of the failures manually and it's good
[09:10] <sil2100> Ok then, so we're basically good to go
[09:11] <sil2100> Now the question is, should I publish..?
[09:12] <robru> sil2100: please publish something, it'll be the first since my rollout this morning, I need to see if it explodes before I can sleep
[09:15] <sil2100> There's nothing ready for publishing! Sadly
[09:25] <robru> sil2100: I don't anticipate any problems publishing, the changes to the publish job are minimal. In case of trouble you might need IGNORE_VERSIONDESTINATION, worst case just copy packages manually and the train will still notice & report migration anyway
[09:27] <robru> Mirv: let me know if the bot pings too much, it may make sense to prevent it pinging if there status contains "currently building" or something
[09:33] <Mirv> robru: it's ok, I'm doing stuff in the silo so it's just good.
[10:05] <morphis> Mirv: do you know what is wrong with https://ci-train.ubuntu.com/job/ubuntu-landing-052-1-build/80/console?
[10:05] <morphis> or sil2100, robru ?
[10:06] <morphis> its just a rebuild after I've updated the MP and there are no further changes in the :parent branch
[10:08] <sil2100> robru: the requests page basic filtering (Migrating etc.) doesn't work with the new statuses
[10:08] <popey> jibel,  New Music app is ready for testing https://requests.ci-train.ubuntu.com/#/ticket/679
[10:08] <sil2100> morphis: there's a ubuntu-system-settings in the proposed pocket right now that needs to be merged for you to re-build your packages
[10:08] <robru> sil2100: crap sorry will fix tomorrow, use searches for now
[10:08] <jibel> popey, okay, must it wait for the new bgplaylist support to land too?
[10:08] <popey> no
[10:08] <popey> this doesn't include that
[10:09] <morphis> sil2100: ah I see
[10:09] <sil2100> morphis: this error basically says: hey, there's a version of this package in the archive that's missing in trunk
[10:09] <popey> this is mostly uitk1.3
[10:09] <morphis> sil2100: when will that happen?
[10:09] <sil2100> morphis: and it's missing in trunk as the package didn't migrate yet so the changes weren't merged
[10:09] <robru> morphis: you can use force build to get around this for now but be aware that's just ignoring the issue, will require a rebuild after that other silo mergers
[10:09] <sil2100> robru: I wouldn't do that now
[10:09] <sil2100> Since I know that some migrations are blocked right now
[10:10] <robru> sil2100: right but presumably he wants to test his branch without being blocked by unrelated silos.
[10:11] <morphis> sil2100, robru: I pushed changes we need to land everything
[10:11] <sil2100> I see that the autopkgtests are in progress, so it's not blocked by the standard issues
[10:11] <sil2100> Ok, so maybe you can force-rebuild to get something testable, but you'll need to rebuild once again after this migrates
[10:11] <sil2100> So as you prefer
[10:14] <robru> morphis: yeah if you build now and then publish, it will effectively revert the package that's currently in proposed, that's why this check exists, it tries to prevent you from building a weird package. So you can override it if you want to, but just be aware you'll need to rebuild again to incorporate the other changes once the other silo lands. Train will
[10:14] <robru> notify you when the other one lands and its ready to rebuild
[10:15] <morphis> robru: thanks, how long will that take?
[10:16] <robru> morphis: unknown, there's a delay in autopkgtests right now due to some large backlog.
[10:18] <morphis> hm
[10:18] <morphis> robru: which would mean we could be blocked for days or hours on landing things?
[10:19] <robru> morphis: yep. If it's really urgent we can consider a force merge to move things along but that's a desperate measure
[10:19] <robru> morphis: you can follow along here: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-system-settings
[10:21] <morphis> ah, thanks
[10:22] <morphis> davmor2: ^^
[10:25] <davmor2> morphis: wompwompwomp.com
[10:26] <morphis> :(
[10:27] <Mirv> robru: let me just say aloud I love the fully automatic status updating
[10:30] <davmor2> morphis: ^ is that it built
[10:30] <davmor2> morphis: or is that a problem
[10:31] <morphis> davmor2: no that one is what is building now and should succeed
[10:31] <morphis> 1:6.0-0ubuntu9.7 is the version
[10:32] <pete-woods> ^ needs a packaging ack
[10:33] <pete-woods> https://ci-train.ubuntu.com/job/ubuntu-landing-022-2-publish/59/artifact/gmenuharness_packaging_changes.diff
[10:39] <morphis> davmor2: I forced a rebuild of settings-app now too
[10:39] <morphis> davmor2: so that we have something to test with
[10:39] <Mirv> pete-woods: could you use export QT_SELECT := qt5 instead of depending on qt5-default?
[10:40] <Mirv> pete-woods: mostly because Debian does not like the latter and may remove it at some point
[10:40] <pete-woods> Mirv: sure, do you put that in debian/rules
[10:40] <pete-woods> ?
[10:40] <Mirv> pete-woods: example http://anonscm.debian.org/cgit/pkg-kde/qt/qtdeclarative.git/tree/debian/rules?h=ubuntu
[10:40] <Mirv> pete-woods: yes
[10:41] <pete-woods> okay, rebuilding
[10:42] <bzoltan_> Mirv:  I would need a silo to fix this translation issue - https://requests.ci-train.ubuntu.com/#/ticket/680
[10:42] <Mirv> bzoltan_: oh right we're low on them. ok.
[10:42] <Mirv> bzoltan_: done
[10:42] <bzoltan_> Mirv:  thank you
[10:45] <bzoltan_> Mirv: seb128:Now I hav a problem - https://ci-train.ubuntu.com/job/ubuntu-landing-010-1-build/262/console This landing does not start because the previous is not landed yet...
[10:54] <robru> Mirv: Haha thanks
[10:57] <robru> bzoltan_: just force build to get past that
[10:59] <robru> Oh gad it's 3am. Night
[10:59] <Mirv> robru: night!
[11:05] <bzoltan_> robru:  Thanks, and good night
[11:54] <victorp> sil2100, hi
[11:54] <victorp> did you get my email?
[11:55] <jibel> victorp, he's away ATM and should be back after 1300
[11:55] <jibel> so soon-ish
[11:55] <victorp> jibel, np - I just saw that you replied. Just wanted to check you had it
[12:24] <pete-woods> Mirv: hi, I've fixed the qt default thing now ^
[12:33] <pete-woods> (new diff https://ci-train.ubuntu.com/job/ubuntu-landing-022-2-publish/60/artifact/gmenuharness_packaging_changes.diff)
[12:34] <sil2100> victorp: Im on lunch now, will check the email once I'm fully back
[12:34] <sil2100> victorp: do we have a final decision on the release?
[12:34] <sil2100> Are we good to go?
[12:39] <Mirv> pete-woods: it claims it unity MP has new commits, and the train is usually right about these things? someone has pushed something since the last build
[12:40] <Mirv> pete-woods: sorry, wrong silo
[12:40] <Mirv> pete-woods: just a moment!
[12:43] <Mirv> pete-woods: publish done, next xenial proposed migration
[12:48] <pete-woods> Mirv: thanks! you had me worried there for a second
[12:48] <pete-woods> thought I'd modified unity8 somehow
[12:49] <Mirv> pete-woods: :)
[12:56] <victorp> sil2100, check the email ;P
[14:23] <pmcgowan> sil2100, published?
[14:47] <mzanetti> cihelp: hey, we're still having issues that we can't access logs from our CI jobs. Can anyone help please?
[14:47] <mzanetti> for example: https://code.launchpad.net/~mzanetti/unity8/move-screenshots-to-tests/+merge/276798
[14:47] <mzanetti> https://code.launchpad.net/~mzanetti/unity8/move-screenshots-to-tests/+merge/276798/comments/703590
[14:47] <mzanetti> only the first 2 links are working, the rest gives a 404
[14:49] <fginther> mzanetti, hunh, I'm surprised any of them our working.  We've been fighting a problem with build publishing since the upgrade
[14:49] <mzanetti> fginther, ack, thanks. Just wanted to make sure it's not our instance alone that's broken while you guys think all is fine. If you're working on it, all is fine.
[14:49] <fginther> mzanetti, in all cases, you should be able to get the results by swapping "https://jenkins.qa.ubuntu.com" to "http://s-jenkins.ubuntu-ci:8080/" until the problem is fixed
[14:49] <mzanetti> tsdgeos, ^
[14:50] <tsdgeos> k
[14:57] <mardy> Mirv: hi! Is there something you can do to unfreeze https://requests.ci-train.ubuntu.com/#/ticket/591 ? I see that there's an autopcktest failure, but that's some dependency error out of my control
[15:21] <renatu> cihelp, could you create this silo? https://requests.ci-train.ubuntu.com/#/ticket/682, I am getting this message: ''ERROR Assignment failed: Low on silos: Ask a trainguard to assign.''
[15:21] <josepht> renatu: that's a request for trainguards
[15:22] <sil2100> renatu: yep, poke trainguards for this kind of thing - on it now
[15:23] <renatu> josepht, sil2100 , ok thanks
[15:23] <sil2100> renatu: done
[16:13] <rvr> mzanetti: Silo 60 approved
[16:14] <mzanetti> rvr, woot! thanks!
[16:42] <robru> alex-abreu: digging into this exception, gimme a minue
[16:43] <alex-abreu> robru, thx
[16:44] <oSoMoN> trainguards: can we get a silo for https://requests.ci-train.ubuntu.com/#/ticket/683 ?
[16:45] <robru> oSoMoN: 22:
[16:45] <robru> oSoMoN: https://ci-train.ubuntu.com/job/prepare-silo/6531/console
[16:45] <oSoMoN> robru, thanks
[16:46] <robru> oSoMoN: you're welcome
[16:49] <robru> alex-abreu: ok I have a fix in trunk, will hit production in ~30 min, try again then.
[16:50] <alex-abreu> robru, ok thx
[17:17] <bfiller> sil2100, robru: can you please add nerochiaro (lp name uriboni) to have access to citrain to create silos, etc?
[17:18] <robru> bfiller: on it
[17:18] <bfiller> robru: thanks
[17:19] <robru> bfiller: done. You're welcome
[17:20] <bfiller> nerochiaro: try logging out and back in, should be all set
[17:21] <nerochiaro> bfiller: looks like it's working. thanks. any document i should read to understand the process ? i don't want to annoy people with questions
[17:22] <bfiller> nerochiaro: not sure about that, but I can give you some quick tips. probably best when you want to create a new silo and can walk you through it
[17:23] <nerochiaro> bfiller: ok, let's do it that way
[17:23] <bfiller> nerochiaro: it's for the most part self-explanatory, but couple of things you should be aware of
[17:27] <robru> nerochiaro: https://wiki.ubuntu.com/citrain/LandingProcess don't hesitate to ask questions, I'd rather answer questions than fix mistakes
[17:28] <robru> nerochiaro: but there are very few mistakes that can't be fixed by a rebuild so don't be afraid to experiment
[17:32] <nerochiaro> robru: excellent, thanks
[17:32] <robru> nerochiaro: you're welcome!
[17:36] <pmcgowan> robru, why don't I see silo-009 on the citrain requests page
[17:37] <robru> pmcgowan: looks fine to me? https://requests.ci-train.ubuntu.com/#/silo/009 where are you looking?
[17:38] <pmcgowan> robru, https://requests.ci-train.ubuntu.com/#
[17:40] <robru> pmcgowan: second page
[17:40] <robru> pmcgowan: https://requests.ci-train.ubuntu.com/#?limit=50&page=2
[17:41] <sil2100> pmcgowan: the requests page is paged, you need to click the "... older ..." button at the bottom
[17:41] <sil2100> Or simply search by silo
[17:41] <pmcgowan> robru, oh, stupid me
[17:41] <pmcgowan> had no idea
[17:41] <robru> Looks like i need to do something about these device tarball requests, they don't go through Jenkins so they don't get marked as landed and cleared from the list
[17:42] <robru> pmcgowan: it's sorted by request number so if you're looking for a silo number it's easier to search than to browse the list
[17:43] <pmcgowan> robru, yeah I got used to just using search in page in the browser
[17:43] <robru> pmcgowan: yeah unfortunately the performance of the page suffers if more than 50 requests are shown so i had to paginate it
[17:43] <pmcgowan> robru, so how would I search for media-hub requests
[17:44] <pmcgowan> if i click the search options nothing happens
[17:44] <robru> pmcgowan: there's a search field in the right hand bar. Type media-hub and "search active silos" you can even bookmark your searches
[17:44] <robru> Search options?
[17:44] <pmcgowan> oh I see
[17:45] <pmcgowan> robru, thanks
[17:45] <robru> pmcgowan: you're welcome! Also "show silo #" is for directly jumping to a specific silo number if you know the number you want to see
[19:01] <rvr> mzanetti: ping
[19:18] <robru> alex-abreu: oh god it's still broken sorry
[19:27] <mterry> robru, love the status changes (new line and clearer text).  One thing I just noted.  I updated a unity8 branch but haven't built yet, and the status says it is dirty for xenial only but is fine for vivid
[19:28] <robru> mterry: yeah, that's expected, because the vivid package isn't built from MPs, it's built by copying the MP dir. so the vivid package has no way to know there's new commits because it is handled by a separate class that has no knowledge of commits. rest assured though it's not possible to build just the xenial bit, when you rebuild one you rebuild both.
[19:31]  * robru is thinking that I should probably hide the package list when all packages have the same status just like I did with the arch list.
[19:31] <boiko> robru: would you mind triggering a rebuild of dialer-app for ppc64el xenial in silo 25?
[19:32] <robru> boiko: done
[19:32] <boiko> robru: thanks!
[19:32] <robru> boiko: you're welcome!
[19:36] <robru> alex-abreu: ok I have another fix, more confidence in this one, just waiting for webops to get back from lunch to get it into production
[19:36] <alex-abreu> robru, ok :) ... same timeline ?
[19:37] <alex-abreu> robru, what causes the issue ? is it specific to this silo ?
[19:38] <robru> alex-abreu: this issue would be effecting anybody trying to build a package that doesn't exist in ubuntu archive. I made some changes recently and this regressed. last fix was a gamble, this fix is similar to reverting the change that caused the issue so it should be good.
[19:38] <alex-abreu> thx
[19:39] <robru> alex-abreu: cron will always roll out the fix at 17 minutes past the hour, but I need webops anyway for other stuff I'm doing so I'm trying to get them to roll everything out sooner, but the guy's on lunch
[19:39] <robru> alex-abreu: you're welcome. sorry for the hassle!
[19:39] <alex-abreu> np
[19:41] <mzanetti> rvr, pong
[19:47] <boiko> robru: is there still a "watch-only" build job or will silo 25 pick the new status (packages built) automatically at some point?
[19:47] <robru> alex-abreu: ok, got it. trying again: https://ci-train.ubuntu.com/job/ubuntu-landing-045-1-build/104/console
[19:47] <robru> boiko: I just eliminated watch-only because the train is now ALWAYS watching ;-)
[19:48] <alex-abreu> robru, thx
[19:48] <robru> alex-abreu: you're welcome
[19:48] <boiko> robru: ok, does it poll from time to time or the failed to build status there is a bug?
[19:49] <robru> boiko: it polls every 30 minutes.
[19:49] <boiko> robru: ok, thanks
[19:49] <robru> boiko: you're welcome. in fact it's starting a poll now: https://ci-train.ubuntu.com/job/check-publication-migration/27097/console should get to your silo in a few minutes
[19:50] <robru> it's on my TODO list to speed this up
[19:56] <robru> yay
[20:22] <robru> alex-abreu: oops, don't let that status fool you, packages are in PPA and building.
[20:23] <alex-abreu> robru,  :)
[21:52] <greyback_> trainguards: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#liburcu <- the amd64 test has been stuck a long time now, can it be kicked?
[21:58] <robru> greyback_: what's "a long time"? Last i heard there was a big backlog and you just have to wait. I don't have any power over autopkgtests
[21:59] <greyback_> robru: at least 3 hours since i last looked. Other tests appear to only take 5 mins, hence was curious
[22:03] <robru> greyback_: i got a mail from pitti yesterday saying there's a big backlog on amd64 due to a big KDE landing. Not sure if that's cleared up yet or not
[22:03] <greyback_> robru: perhaps that's it then. Sorry for the noise
[22:06] <robru> greyback_: no worries, from what i understand the infra is pretty strained. I don't think 3 hours is crazy long. I'd start being worried around 12 hours or something.
[22:06] <greyback_> robru: ok. See you in 9 hours ;)
[22:07] <robru> Heh
[22:56] <kenvandine> robru, check this out
[22:56] <kenvandine> 2015-11-19 21:15:35,091 ERROR Bileto says: 500 INTERNAL SERVER ERROR
[22:56] <robru> Ugh
[22:56] <kenvandine> https://requests.ci-train.ubuntu.com/#/ticket/443
[22:57] <kenvandine> it still says Beginning publication
[22:57] <kenvandine> but i'm pretty sure it's done publishing
[22:57] <kenvandine> robru, i was stress testing bileto... 33 packages :)
[22:57] <kenvandine> robru, gotta love webapps!
[23:00] <robru> kenvandine: huh, the audit log says release pocket, that implies it migrated, not sure why it would be updating the audit log but falling to set the status
[23:01] <kenvandine> robru, yeah... can i merge it?
[23:01] <kenvandine> or do you want to debug?
[23:02] <robru> kenvandine: you can merge it if you're blocked, looks like a db field length issue indeed, i thought i took all the length limits off already though...
[23:03] <kenvandine> robru, not blocked... just want it off my plate
[23:03] <kenvandine> but i don't mind leaving it for you to debug
[23:03] <kenvandine> just click merge when you're done :)
[23:05] <robru> kenvandine: k, leave it with me.
[23:05] <kenvandine> robru, i need to take off for the evening, thanks!
[23:05] <robru> kenvandine: you're welcome