[00:45] <robru> renatu: ok we're back online if you need to build anything now
[00:47] <renatu> robru, thanks
[00:48] <robru> renatu: you're welcome
[01:19] <robru> AlbertA: hi, thanks for being among the first to try out the new train ;-) looks like there's a couple firewall issues stopping things from working, I've notified IS, hopefully will be resolved within an hour
[01:21] <AlbertA> robru: no prob. new site looks great!
[01:21] <robru> AlbertA: thanks!
[01:43] <bregma> robru, is there any change to landing a silo once the testing has passed?
[01:44] <robru> bregma: nope that part is the same for now. you need QA to approve (sometimes) and then you need me to hit publish
[01:44] <bregma> robru, ok, just making sure
[01:45] <robru> bregma: yeah the goal is to make it so that people can publish their own stuff too, but that's a ways off still
[05:16] <robru> AlbertA: ok wow, apologies on that horrible delay! retrying your build now, should be working: https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/329/console
[06:32] <robru> michi: sorry about that dput failure, retried for you, should be working now: https://ci-train.ubuntu.com/job/ubuntu-landing-051-1-build/14/console
[06:33] <michi> robru: Hey, no problem! Thanks for picking it up on it. I figured that, with everything in flux, I’d just wait a while for things to settle down :)
[06:33] <michi> There was little point in shouting at you guys, I thought :)
[06:33] <robru> michi: yeah that was a scary 8 hours of downtime that should only have been 2 hours of downtime. but as far as I know everything is perfect now, so have at it ;-)
[06:34] <michi> The new stuff looks nice.
[06:34] <michi> I haven’t gone through the process of starting a new landing yet.
[06:34] <robru> michi: thanks! please email me with any improvement ideas you may have. I'm going to try to focus on papercuts over the next week or so
[06:34] <michi> But it sure looks easier than the spreadsheet.
[06:34] <michi> Will do, if I come across something that isn’t obvious.
[06:34] <robru> yeah
[06:34] <robru> michi: alright, 11:30 here, goodnight ;-0
[06:35] <michi> Well-deserved sleep coming up. Enjoy it! :)
[07:30] <jibel> robru, hey, just to confirm, the data from the spreadsheet won't be migrated to bileto?
[07:30] <robru> jibel: correct
[07:31] <robru> jibel: well maybe some of it, by hand, but generally no, they will coexist for a while
[07:32] <jibel> robru, that's fine, it's just to know where we should approve landing requests for cards already created.
[07:33] <robru> jibel: good luck! Email me if you have any questions about the api
[07:34] <jibel> robru, it should be all right, the API is easy to use and clear. Much simpler than scanning a spreadsheet :)
[07:35] <robru> jibel: hehe yeah.
[07:35] <robru> jibel: OK I'm just winding down, goodnight!
[07:36] <jibel> good night
[07:58] <jamesh> sil2100: fyi, we came up with a workaround for the thumbnailer gstreamer issues, so should be able to do a trunk landing with the gcc 5 fixes soon.
[07:59] <sil2100> jamesh: excellent, would like that ASAP
[08:00] <jamesh> cihelp: I got this error from the generic-land portion of an autolanding job: http://s-jenkins.ubuntu-ci:8080/job/generic-land/27514/console
[08:00] <psivaa> jamesh: let me take a look
[08:01] <seb128> jamesh, hey, is there a bug about that gstreamer issue?
[08:01] <jamesh> psivaa: everything built fine on the arch specific subjobs that preceded that bit
[08:02] <jamesh> seb128: I haven't yet.  I believe the bug is tied to the fdsrc element though, which has given us problems in the past
[08:02] <jamesh> seb128: I changed the thumbnailer to not depend on that element any more.
[08:02] <seb128> jamesh, would be nice to have a bug, forwarded upstream if possible
[08:02] <seb128> k
[08:03] <jamesh> seb128: right.  I've done that for a number of fdsrc bugs in the past, but hadn't narrowed this one down.
[08:06] <jamesh> psivaa: if it helps, the MP for that landing is merging a copy of lp:thumbnailer to lp:thumbnailer/devel.  I wonder if this is some edge case for branch stacking, since there are no revisions in lp:/~jamesh/thumbnailer/devel-sync-20150725 that are not in the development focus branch
[08:08] <psivaa> jamesh: that could be a possibility, i have seen this error once and trying to remember/dig for that information
[08:12] <oSoMoN> jibel, hey, I marked silo 6 ready for QA validation a while ago, and it hasn’t appeared in the trello board yet, known issue?
[08:13] <jibel> oSoMoN, I disabled the bot last night while robru was migrating the spreadsheet, just in case.
[08:13] <jibel> Let me run it
[08:14] <oSoMoN> thanks
[08:15] <jibel> ah, and robru moved the dashboard so now it crashes because it cannot find it
[08:15] <jibel> I'll fix that
[08:16] <robru> jibel: new dashboard is a bit different
[08:17] <jibel> robru, where is the raw data?
[08:17] <davmor2> robru: grrrrrrr changing all the urls ;)
[08:17] <robru> jibel: requests.ci-train.ubuntu.com/static/json/index.txt lists assigned silos
[08:19] <jibel> oSoMoN, it'll take a moment
[08:19] <jibel> looks like we'll create cards manually this morning
[08:19] <oSoMoN> jibel, that’s alright, that one’s not super urgent
[08:19] <psivaa> jamesh: would there be any possibility that there was a rev manually pushed to the devel branch
[08:19] <psivaa> ?
[08:20] <jamesh> psivaa: no.
[08:20] <robru> jibel: the filenames listed in index.txt can then be accessed relative to that url for the raw json statuses
[08:20] <jibel> oSoMoN, thanks, it'll be fixed soon. I didn't plan to make the bot work with the spreadsheet and bileto at the same time :)
[08:22] <jibel> oSoMoN, BTW, on the dashboard the state is 'Package Built' not 'Ready for QA'
[08:23] <jibel> it'll be a quiet day, nothing is ready for QA
[08:23] <jibel> robru, ^
[08:23] <oSoMoN> jibel, then there’s an issue with the dashboard. robru: I marked silo 6 ready for QA validation in the spreadsheet earlier this morning, and apparently the dashboard didn’t pick it up
[08:24] <sil2100> The dashboard doesn't seem to fetch statuses from the spreadsheet at all now
[08:24] <jamesh> psivaa: the revision ci-train-bot@canonical.com-20150715020328-bq2ohz4ufnerale2 it says is a ghost is the head revision of lp:thumbnailer (and also of the devel-sync branch that is the source of the merge)
[08:24] <robru> oSoMoN: the dashboard no longer cares about the spreadsheet
[08:24] <jibel> robru, so how do we track statuses during the transition?
[08:24] <robru> jibel: you'd have to look at the spreadsheet directly
[08:25] <jibel> robru, of course
[08:25] <jibel> lol
[08:25] <robru> :-P
[08:25] <robru> jibel: sil2100: yes the transition may be a little bit rougher than i anticipated, to many moving pieces
[08:26] <robru> jibel: the trick is that the spreadsheet won't automatically update statuses either, so manual poking will be necessary to make it actually say "ready for qa"
[08:27] <pete-woods> so the spreadsheet lives on?
[08:27] <jibel> it's like picking up your phone every 10 minutes just in case someone calls you because the ring is broken
[08:27] <pete-woods> but behind the scenes now?
[08:27] <jibel> no way we scan the spreadsheet manually
[08:33] <psivaa> jamesh: i see a similar issue in this lp bug, https://bugs.launchpad.net/bzr/+bug/1161018/comments/4
[08:33] <psivaa> would you mind trying the workaround in comment #4
[08:34] <pete-woods> ah right, okay just transitional :)
[08:34] <robru> jibel: we may need to tell people to just irc ping each other until the spreadsheet fully dies
[08:35] <jamesh> psivaa: sure.
[08:37] <jamesh> psivaa: If I have any trouble after retrying the landing, I'll ask again.  Thanks.
[08:37] <psivaa> jamesh: sure, i tried it after copying your branch and it works.
[08:38] <psivaa> jamesh: to test,  'bzr revno lp:~jamesh/thumbnailer/devel-sync-20150725' command should just work
[08:40] <jamesh> psivaa: pushed an empty commit, and "bzr revno" works, so hopefully Jenkins will be happy.
[08:43] <psivaa> jamesh: http://s-jenkins.ubuntu-ci:8080/job/generic-land/27517/console was happy :)
[08:50] <jibel> robru, yeah, there is no other choice anyway
[08:50] <jamesh> psivaa: thanks for your help.
[08:50] <psivaa> jamesh: np
[08:54] <jibel> sil2100, robru don't you think that silos on the spreadsheet that must be rebuilt or reconfigured should be moved to bileto instead?
[08:54] <sil2100> jibel: that's one proposition, yes
[08:54] <jibel> sil2100, and every team is responsible of moving their records
[08:54] <sil2100> We'll probably doing that, but currently it requires some manual work...
[08:55] <jibel> sil2100, otherwise the spreadshhet will stay there forever
[08:55] <sil2100> Manual work not really suited for normal team members
[08:55] <jibel> sil2100, checking lines manually also requires manual work
[08:57] <sil2100> I know, just saying it's not something normal landers can do, we'll be migrating entries slowly ourselves
[09:02] <sil2100> I didn't expect we'd have to be doing that as a priority, thought that the dashboard would support both during the grace period
[09:05] <jibel> sil2100, if a line is copied from the spreadsheet does it mean the silo will have to go through the whole process again, merge, build, ...
[09:05] <jibel> ?
[09:05] <sil2100> No, it won't have to be reassigned, just needs to be hm, hacked into the Bileto ;)
[09:06] <sil2100> I'll probably create a jenkins job for migrating entries, give me a few minutes
[09:06] <sil2100> Then it should be cool
[09:08] <jibel> sil2100, you can export the spreadshhet and recreate the request with the API
[09:14] <sil2100> Anyway, I'll get to it in a minute, just need to finish something up real quick first
[09:23] <sil2100> jibel: ok, on it
[09:45] <sil2100> hmmm
[09:46] <sil2100> jibel: looks like it won't be as easy
[09:58] <greyback> trainguards: does the new dashboard show if silo ready for QA signoff? My silo11 should be in that state, but the dash doesn't show it
[10:08] <jibel> greyback, it doesn't
[10:09] <jibel> greyback, your request is in the old spreadsheet?
[10:09] <greyback> jibel: ah, that's still alive? Let me see
[10:10] <jibel> greyback, status in the dashboard are not updated for request still in the spreadsheet
[10:10] <greyback> jibel: yep, ok spreadsheet reports it's ready for QA. Thanks!
[10:11] <jibel> sil2100, ^ data have to be migrated, we'll lose things otherwise
[10:15] <sil2100> jibel: yeah, I know, I tried migrating an entry as per robru's instructions but it doesn't work
[10:16] <sil2100> I'll try something
[10:17] <sil2100> ANyway, I have no idea why we couldn't have just left the spreadsheet working for the grace period
[10:17] <sil2100> Yeah, so it will be a bit more painful, the migration that is
[10:17] <sil2100> A watch-only rebuild is required
[10:18] <sil2100> (or actually any other operation)
[10:37] <jibel> sil2100, do you know how I differentiate deb package landings from tarball and clicks?
[10:37] <jibel> how to*
[10:38] <sil2100> jibel: I think the only difference is if it has Manual Download Urls defined or not
[10:38] <jibel> okay, thanks
[10:44] <jibel> sil2100, where can I find the list of sources packages for a request? For example in https://requests.ci-train.ubuntu.com/v1/tickets?qa_signoff=Ready 'sources' is empty but it filled on the dashboard.
[10:44] <jibel> sorry for all the questions
[10:46] <jibel> sil2100, nm, found it
[10:48] <sil2100> jibel: k, no worries, just remember only robru knows the system well
[10:49] <sil2100> I'm a consumer here as well
[10:49] <jibel> sil2100, I know but he's sleeping and it helps asking questions. Look I found the answer ;)
[10:49] <sil2100> I'm a bit surprised with a few things, since after the public deployment so many things unexpectively changed
[10:49] <sil2100> jibel: btw. do you know if we still have HTTP access to the config files that were exported to lillypilly before?
[10:50] <jibel> sil2100, yeah it's related to my previous question
[10:50] <jibel> sil2100, https://requests.ci-train.ubuntu.com/static/json/index.txt will give you a list of the data available
[10:51] <sil2100> index.txt? No wonder https://requests.ci-train.ubuntu.com/static/json/ didn't work when I tried that
[10:51] <jibel> sil2100, then for the data itself about a silo replace index.txt by the silo you want
[10:51] <jibel> sil2100, https://requests.ci-train.ubuntu.com/static/json/ubuntu/landing-002 for example
[10:51] <sil2100> Yeah, got it
[10:52] <jibel> sil2100, fixing the bot is a bit more work than I expected TBH
[10:53] <jibel> sil2100, but now it should work for deb package landing, I need to validate click and tarballs now
[10:54] <jibel> but it's a post-lunch task
[10:56] <sil2100> jibel: btw. migration might be really really painful to do
[10:57] <sil2100> Eh, now I feel bad I didn't have enough time to test bileto before deployment
[10:57] <sil2100> There's so many things I'd need to see fixed
[11:00] <sil2100> jibel: anyway, since one can't write a script that just migrates entries straight away as it requires 3 different isolated steps, I'm actually thinking of at least enabling the spreadsheet status updates
[11:04] <sil2100> hmmmm
[11:04] <sil2100> Bileto silo assignment doesn't seem to work?
[11:08] <sil2100> robru: the assignment URL has some bad urlencoded signs, you can't assign any silos
[11:08] <sil2100> greyback_: hey! Could you try assigning your newly filled request?
[11:09] <sil2100> greyback_: I want to know if you also get the wrong urlencoded urls in the prepare job
[11:09] <greyback_> sil2100: ok
[11:10] <sil2100> Need to know if it's b0rken in overall, or just for me
[11:10] <greyback_> sil2100: looks broken: https://ci-train.ubuntu.com/job/prepare-silo/5561/
[11:11] <sil2100> greyback_: yeah, same here
[11:11] <sil2100> https://code.launchpad.net/~dandrader/unity8/app-state-handling/+merge/258653
[11:11] <sil2100> It copy-pastes correctly, but in reality it's wrong
[11:11] <sil2100> %253A
[11:11] <sil2100> https%253A//code.launchpad.net <- things like these are in the request
[11:12] <greyback_> yeah, someone not urldecoding
[11:12] <sil2100> The funny thing is, I don't have access to hot-fix it
[11:12] <greyback_> funny ha ha?
[11:12] <greyback_> :)
[11:12] <sil2100> Very funny ;) I love having everything under IS control
[11:12] <greyback_> well there's no hurry with that silo, I need to wait until silo11 lands
[11:13] <greyback_> but can't say I'm impressed
[11:13] <sil2100> We can assign it by urldecoding by hand
[11:13] <sil2100> ;p
[11:18] <greyback_> hah
[11:18] <sil2100> I'll try looking into fixing that
[11:20] <davmor2> jibel, sil2100: I'm trying to test silo 51 unfortunately I can't make it actually install anything it looks like there are just -dev and -doc files or am I missing something?
[11:22] <jibel> davmor2, I don't even know which line of the spreadsheet it was
[11:22] <davmor2> jibel: 60
[11:23] <jibel> davmor2, and the commit log is not helpful either "Initial revision for landing."
[11:24] <mzanetti> jibel, hey, is there something wrong with silo 35?
[11:24] <mzanetti> I see lots of other silos coming in after that but getting tested beforehand
[11:24] <davmor2> jibel, sil2100: http://paste.ubuntu.com/11965973/
[11:25] <davmor2> jibel: citrain didn't pull anything in, I can't see a default package to actually install and apt refuse to do anything :)
[11:25] <jibel> davmor2, no idea, ask michi for clarification
[11:25] <davmor2> jibel: will do
[11:26] <jibel> davmor2, oSoMoN said silo 6 is ready but there is no card due to the death of the spreadsheet.
[11:45] <bzoltan_> sil2100: would you be able to help me with the silo assignement, please? I have just entered a new line to the new interface
[11:46] <sil2100> bzoltan_: as per e-mail, assignment is a bit broken right now - let me assign it for you with manual intervention
[11:46] <sil2100> I'm looking into fixing that, but I don't know robru's bileto code, so it'll take a while
[11:46] <bzoltan_> sil2100:  Yes, i have read the mail :)
[11:46] <sil2100> In the meantime I can manually help ;p
[11:46] <bzoltan_> sil2100: thank you
[11:48] <sil2100> greyback_: I'll assign your silo in a moment too, if you don't mind I'll use it shortly as test-bed
[11:48] <greyback_> sil2100: no prob, that's what I kept it there for
[11:53] <sil2100> greyback_: thanks
[12:06] <sil2100> Strange, it looks like suddenly our CI Train jenkins simply stopped urldecoding the GET requests
[12:13] <jibel> sil2100, new bot updated and in production
[12:13] <jibel> ubuntu-qa ^
[12:23] <sil2100> jibel: sweet
[12:23] <sil2100> Ok, I still didn't find the reason why jenkins doesn't suddenly not urldecode
[12:29]  * sil2100 goes of to lunch
[12:32] <Laney> sil2100: can we have a redirect for the dashboard please?
[12:33] <Laney> robru: ^ I guess :)
[12:34] <jibel> robru, and also fix the link 'RAW' on the dashboard
[12:39] <davmor2> jibel: why are there 2 ticket for silo2
[12:40] <jibel> davmor2, the request ids in the spreadsheet and its replacement don't match
[12:40] <jibel> davmor2, you can delete the second card
[12:41] <davmor2> jibel: they are breeding
[12:48] <jibel> davmor2, it is just that the testing request exists in the spreadsheet and bileto. It has been created yesterday from the spreadsheet, then today I ported the bot to bileto which discovered this request. Since the request ids are different between the 2 systems it thought it was new and added a ticket
[12:49] <jibel> davmor2, it will happen again if people create requests that already existed in the spreadsheet.
[12:50] <davmor2> jibel: it's the fact we are upto 3 that is concerning, it's like each time the import happens it creates a new ticket
[12:50] <jibel> davmor2, yeah, I think I just fixed that
[12:50] <pmcgowan> davmor2, with click package updates in the custom tarball, do you know how these get applied during the update? is it via click install or is it via the image diff?
[12:54] <davmor2> pmcgowan: iirc the image pulls in the updates from trunk/store and then creates the tarball, then I believe it just uses image diff to install on the device, cwayne might be able to give you more clarity though
[12:56] <cwayne> the ones in the custom tarball are via image diff i *think*
[12:56] <jibel> pmcgowan, it's a diff, everything is already unpacked in the tarball
[13:01] <pmcgowan> jibel, thats what I thought thanks, so there is no way a single click could fail to update
[13:02] <bzoltan_> sil2100: Do you know what should be the cure for the "error pushing:" failure of the ubuntu-device-flash?
[13:05] <pmcgowan> bzoltan_, is that arale? probably the flaky usb
[13:06] <bzoltan_> pmcgowan: no, it is both krillin and mako. Bootstrapping works fine, but simple flash fails
[13:06] <pmcgowan> hmm
[13:07] <pmcgowan> bzoltan_, latest u-d-f from the PPA?
[13:08] <bzoltan_> pmcgowan: it should be up to date.. I check the versions
[13:09] <pmcgowan> I have  0.20-0ubuntu1
[13:09] <pmcgowan> fwiw
[13:12] <bzoltan_> pmcgowan: I have 1.1+15.10.20150519-0~341~ubuntu15.04.1 from the recipe .. that is newer then any release
[13:13] <bzoltan_> pmcgowan: hmm... now it works... it could be USB flakiness
[13:20] <bzoltan_> pmcgowan:  it is random... "error pushing: error: protocol fault (no status)" and never finishes with the flashing :(
[13:21] <infinity> jibel: Who was your new victim for dkms testing issues?
[13:21] <infinity> jibel: Looks like the current builds have been running for 27 hours. :P
[13:21] <jibel> infinity, still me
[13:22] <pmcgowan> bzoltan_, that weird maybe your laptop
[13:22] <infinity> jibel: Oh.  Well, hi you.  Iz broke.
[13:22] <bzoltan_> pmcgowan:  it happens on both my laptops... checking the third one
[13:23] <pmcgowan> bzoltan_, I am not sure where you got that version
[13:23] <pmcgowan> I don't see that in the ppa
[13:23] <bzoltan_> pmcgowan: from here -> https://code.launchpad.net/~bzoltan/+recipe/sdk-tools-dev
[13:24] <pmcgowan> bzoltan_, why not the one in the ppa?
[13:24] <jibel> infinity, the execution node is down again
[13:24] <jibel> infinity, I'll restart it
[13:25] <bzoltan_> pmcgowan:  :) somebody need to test the release candidate of the phablet-tools.
[13:25] <bzoltan_> pmcgowan:  but i will  downgrade now and see... if it works then the phablet-tools trunk is broken
[13:25] <infinity> jibel: Is that same node used by autopkgtests, cause they seem a bit backed up too.
[13:28] <jibel> infinity, yeah but adt jobs are distributed, it shouldn't be a problem
[13:28] <jibel> infinity, let me restart whatI can
[13:34] <jibel> infinity, dkms node is back
[13:34] <infinity> jibel: Will the jobs need a kick, or should they wake up?
[13:34] <jibel> infinity, they'll wake up
[13:34] <infinity> jibel: Ta.
[13:35] <jibel> cihelp: ^ can you monitor wazn-adt, it's the second time it crashes in 2 weeks and no one notice
[13:38] <fginther> jibel, it's just the 'wazn-adt' slave right. not the node itself or the two other slaves running there?
[13:38] <jibel> fginther, yes, the jenkins-slave process dies and doesn't respawn
[13:41] <boiko> sil2100: does the dashboard still show the silos as marked as tested and ready for QA?
[13:42] <fginther> jibel, I'm a little curious as to what's going on here. initctl reports 'auto-package-testing-jenkins-slave stop/waiting', but the slave is running. Do you know how it was restarted?
[13:42] <sil2100> boiko: yes, but not from the spreadsheet... sadly Robert removed support for the spreadsheet completely
[13:43] <boiko> sil2100: so, yesterday I marked some silos as tested on the spreadsheet, was that migrated or do I need to mark them as tested again?
[13:43] <sil2100> boiko: no, all is fine
[13:43] <boiko> sil2100: I just don't see them marked as so in the dashboard
[13:44] <sil2100> boiko: yes, since as I said, the dashboard doesn't understand the spreadsheet anymore, and there was no migration to bileto yet
[13:44] <sil2100> So it's just marked on the spreadsheet, QA is aware of those
[13:44] <boiko> sil2100: ok, good, just checking, thanks for the info :)
[13:45] <sil2100> This switch to bileto is a bit faulty
[13:46] <fginther> jibel, Oh, I think I see now. Looks like you manually started it.
[13:51] <sil2100> fginther: hey! Did you have an issue with jenkins and the parambuild plugin before that suddenly it wasn't urldecoding the parameters from the URL?
[13:52] <fginther> sil2100, no, I can't say I've seen that
[13:54] <jibel> fginther, sorry was otp. I restarted it
[13:54] <fginther> jibel, thanks for clarifying
[13:56] <infinity> jibel: I question the efficacy of your restart.  Or your claim that the jobs would unstick themselves. :)
[13:56] <infinity> jibel: All of them still seem to be in the "building for over a day" state, I'd have expected a few to be done by now.
[13:57] <cyphermox> hi, could I please have a silo for line 44, or should I open a bileto ticket now instead of using the spreadsheet (line was already there, been sitting in the queue for over a week)?
[13:57] <sil2100> cyphermox: please open a bileto ticket :)
[13:57] <cyphermox> sil2100: thanks!
[14:01] <greyback_> jibel: hey did the current silo11 slip through the cracks? I don't see it in the QA testing board
[14:01] <cyphermox> sil2100: am I also the person supposed to hit assign?
[14:02] <sil2100> cyphermox: yes, but it's broken a bit right now, let me assign it for you
[14:02] <cyphermox> ah ok
[14:02] <cyphermox> just wanted to know if it was all self-serve ;P
[14:02] <cyphermox> awe_: ^^
[14:02] <cyphermox> next time, you'll be able to do it all yourself
[14:02] <awe_> k
[14:03] <cyphermox> morphis: ^ I guess this is relevant for you too
[14:03] <sil2100> Aaah, I see the issue
[14:06] <sil2100> Not sure why suddenly firefox decides to urlencode already urlencoded strings
[14:08] <jibel> infinity, jenkins is slowly digesting the queue. The UI is a bit confusing but if you scroll down to a node called wazn-adt, you'll see that all the builds with a number in front of them are recent.
[14:09] <jibel> infinity, the jobs without number are virtual jobs that jenkins create to keep track of its upcoming tasks
[14:09] <rvr> boiko: ping
[14:10] <rvr> sil2100: To approve a silo, is the spreadsheet still working?
[14:10] <sil2100> Looks like an apache misconfiguration
[14:10] <sil2100> rvr: yeah, for approving yes - since those are simple formulas
[14:10] <infinity> jibel: Ahh, check.  I'll attempt more patience.
[14:11] <jibel> greyback_, it probably slipped through the cracks
[14:11] <rvr> sil2100: Ok
[14:11] <greyback_> jibel: shall I add a card?
[14:12] <jibel> greyback_, which line of the spreadsheet is it?
[14:12] <boiko> rvr: pong
[14:12] <greyback_> jibel: 59
[14:13] <greyback_> jibel: thank you
[14:13] <jibel> greyback_, added
[14:13] <rvr> boiko: Silo 8
[14:14] <boiko> rvr: yep
[14:14] <rvr> boiko: Does the bug has any manual test?
[14:14] <rvr> boiko: Skip network checks on always dispatchable accounts
[14:15] <boiko> rvr: ah yes, let me check the testplan, salem_ said something about addind that to the testplan, let me double check
[14:15] <boiko> rvr: the manual test is: disable data connections (both wifi and mobile data) and reboot the device
[14:16] <boiko> rvr: the dialer needs to show the carrier name, if it doesn't, that's the bug
[14:16] <salem_> rvr, yes, just ensure there are not network (wifi/data) connections active after a reboot and try making/receive calls/messages.
[14:16] <salem_> s/not/no/
[14:17] <rvr> salem_: Ok, I'll check that. Please update the test plan.
[14:17] <salem_> rvr, will do, thanks.
[14:26] <sil2100> robru: I see that you're double urlencoding all your requests - it was done like this in the spreadsheet as well
[14:27] <sil2100> robru: now apache seems confused by this and triple-urlencodes everything
[14:27] <sil2100> robru: is there any reason we have to urlencode urlencoded strings?
[14:31] <davmor2> sil2100: silo006 is good to go
[14:33] <sil2100> Publishing
[14:37] <salem_> rvr, just updated telepathy-ofono testplan.
[14:40] <rvr> salem_: Hmmm
[14:41] <rvr> Something weird
[14:41] <rvr> I'm in a call, but dialer app doesn't show any call
[14:41] <bzoltan_> sil2100:  how in an automatic test environment can I unlock the screen?  Once I have adb connection :) I could unlock it with a gdbus call... but there is no adb when the screen is locked
[14:41] <salem_> rvr, is the green call indicator at the top?
[14:41] <rvr> salem_: Nope
[14:42] <salem_> rvr, incoming call?
[14:42] <rvr> salem_: Yes
[14:42] <rvr> salem_: Second try seems good
[14:43] <salem_> rvr, do you have wifi/data connection?
[14:43] <rvr> salem_: Nope, deactivated them
[14:43] <salem_> rvr, ok, but it was like this when you got the incoming call, right?
[14:44] <pmcgowan> hey udf is tellig me --revision is unknown flag, what am I doing wrong
[14:44] <rvr> salem_: Yes. call was established but then the UI reverted to the offline state, even when the call was active. I could talk, etc.
[14:45] <salem_> rvr, that's really weird, but I would say that's a separate bug.
[14:45] <sil2100> Damn, this bug is a waste of time
[14:46] <sil2100> robru: anyway, found how it's happening that it's broken, but I need you to understand why it's happening
[14:47] <sil2100> bzoltan_: I think once developer mode is enabled then the screen doesn't need to be unlocked to get adb access
[14:47] <sil2100> bzoltan_: at least that's how my device is working ;)
[14:47] <salem_> rvr, the original bug would prevent you from receiving the call in first place.
[14:47] <pmcgowan> popey, davmor2 ?  hey udf is tellig me --revision is unknown flag, what am I doing wrong
[14:48] <bzoltan_> sil2100: makor or krillin? I have flashed with --developer-mode --password=${PASSWORD}
[14:48] <sil2100> bzoltan_: I'm using arale here with developer mode, but I also switched the switch in system-settings
[14:48] <davmor2> pmcgowan: --revision has to go before touch in the command
[14:49] <davmor2> pmcgowan: should be u-d-f --revision x touch --channel whatever/channel
[14:49] <pmcgowan> omg
[14:49] <popey> hehe
[14:49] <pmcgowan> davmor2, thanks so lame
[14:49] <popey> i love u-d-f
[14:49] <jibel> what's the logic to have this option before touch
[14:49] <popey> I have to re-learn it every time
[14:49] <jibel> every one try after
[14:49] <bzoltan_> sil2100:  I hve developer mode enabled and the adb gets closed when the lock screen comes up ... on mako with vivid overlay
[14:49] <pmcgowan> yeah there is even an open bug
[14:50] <sil2100> bzoltan_: hmm, that's strange - could you poke cihelp about that? They might know more since they use devices in the lab for testing
[14:50] <sil2100> So they should know how to properly unlock it
[14:52] <jibel> but u-d-f does everything, creates images, flash them, query the server...
[14:52] <pmcgowan> it just needs to parse arguments now
[14:54] <jibel> ah right, it's a detail
[14:55] <fginther> bzoltan_, sil2100, the krillins and arales require a special recovery image to be used during u-d-f flashing
[14:55] <fginther> which enables adb while the screen is locked
[14:55] <bzoltan_> fginther:  I amnot sure if I understand that
[14:55] <bzoltan_> fginther:  I am on mako this time ..
[14:55] <fginther> bzoltan_, oh, mako doesn't require it
[14:56] <davmor2> pmcgowan: run u-d-f --help and it lists the order of arguments and options as you build up the command
[14:56] <fginther> unless things have changed very recently
[14:56] <bzoltan_> fginther:  my mako with the latest vivid image it does
[14:57] <bzoltan_> fginther:  I see in the --help it says about the --recovery-image= so, where can i get that?
[14:57] <jibel> davmor2, RTFM is not a good answer :) when a user does the same mistake each time he uses a tool, it supposes something is wrong with the tool
[14:57] <rvr> salem_: boiko: Silo 8 approved
[14:58] <fginther> bzoltan_, http://people.canonical.com/~plars/touch
[14:58] <salem_> rvr, awesome, thanks
[14:58] <bzoltan_> fginther:  Thank you ... I will ask plars to make a mako version too >(
[14:59] <davmor2> jibel: no that was a genuine piece of advice,  just append --help and it fills you in on the options available after each step not saying that it is a good thing just a helpful one :)
[14:59] <fginther> bzoltan_, these were not made by plars, that was just the only easily place we had to store them
[15:00] <pmcgowan> davmor2, write a qml front end to it please :)
[15:00] <fginther> bzoltan_, let me see if I can dig up who made them, but if mako now needs them :-(
[15:00] <plars> bzoltan_: oh, we need one for mako now also? I just grabbed those from an older image because there was no official place at the time, there may be some official place now though
[15:00] <plars> bzoltan_: maybe sil2100 knows?
[15:00] <davmor2> pmcgowan: if you see  the code I write you wouldn't even joke about that ;)  There are way more competent coders in the room ;)
[15:01] <bzoltan_> plars: Yes, I was strugling my way thru the tools today to figure it out
[15:01] <pmcgowan> heh
[15:03] <fginther> bzoltan_, FWIW, I can see version 202 from ubuntu-touch/rc-proposed/ubuntu channel being flashed on mako with no need for a recovery image
[15:09] <robru> sil2100: as a workaround for right now, it works if you s/%2520/ /g on the text field and leave the URLs doubly encoded: https://ci-train.ubuntu.com/job/prepare-silo/5565/console
[15:18] <jibel> robru, sil2100 when I log into https://requests.ci-train.ubuntu.com/ I just get the header and no request
[15:18] <jibel> I checked "ci-train-users" on the sso page
[15:19] <robru> jibel: yeah I was getting an error as well, it seems intermittent, try reloading a few times
[15:19] <sil2100> Same here
[15:19] <sil2100> Yeah, after a few reloads it works now
[15:19] <jibel> ah it is just terribly slow
[15:20] <jibel> robru, you didn't have to reimplement everything from the spreadsheet :P
[15:20] <robru> jibel: no no, what's happening is that it's doing an ajax request in the background that silently fails, it retries every few minutes. it's fast when it works
[15:21] <robru> jibel: and of course I can't access the log, will need IS to poke at it, sigh
[15:22] <jibel> robru, where should I file bugs? when I edit then cancel it logs me out
[15:22] <robru> jibel: yeah file bugs against lp:bileto, but again this is the same issue, ajax request is failing intermittently
[15:23] <jibel> I'll be patient until you get the logs then
[15:24] <boiko> rvr: thanks
[16:07] <Laney> I just put a redirect in place for the old dashboard URL
[16:11] <robru_> sil2100: jibel: ok sorry my IRC client has picked the perfect time to explode
[16:12] <robru_> sil2100: I'm in webops trying to get things sorted out, apparently the problem is logrotate misconfigured and then bileto can't log properly and gets angry
[16:12] <robru_> sil2100: jibel: it should be temporarily ok now, but I'm working on a permanent fix
[16:13] <Laney> is the spreadsheet still around enough to let me reconfigure a silo?
[16:15] <robru_> Laney: yes
[16:15] <robru_> Laney: the spreadsheet won't update status but it can reconfigure an existing silo
[16:16] <Laney> OK, thanks!
[16:29] <Laney> robru_: do I need to worry about the messed up urlencoding in MERGE_PROPOSALS and SOURCES?
[16:31] <robru_> Laney: yeah, you should manually s/%2520/ /g to make it work (the urls can stay double encoded but you need real spaces between the urls)
[16:35] <Laney> ty
[16:48] <dobey> that's an odd set of packages in a silo
[16:55] <robru> sil2100: what were you saying about SSO redirecting through http? I'm not seeing that
[16:55] <sil2100> robru: let me check if it's still doing that
[16:56] <sil2100> robru: yeah, still does that, let me PM you with details
[17:42] <robru> cihelp: can I get CI configured for lp:bileto the same way it already is for lp:cupstream2distro? thanks
[17:44] <psivaa> robru: looking into it
[17:45] <robru> psivaa: thanks
[17:49] <jibel> robru, when I can the API, I frequently get an 'Internal Server error'
[17:49] <jibel> I call*
[17:50] <robru> jibel: hmmm I thought I fixed that
[17:50] <jibel> robru, this is what I call: https://requests.ci-train.ubuntu.com/v1/tickets?qa_signoff=Ready
[17:50] <jibel> robru, actually I get it more often than the valid output
[17:51] <robru> jibel: yeah I'm seeing that too, even without the query
[17:52] <kgunn> jibel: hey since you're on :)
[17:52] <robru> jibel: oh well this time I'm finally seeing a traceback in the logs
[17:52] <kgunn> https://trello.com/c/9ujHpNLB/2096-ubuntu-landing-035-unity-api-unity8-mzanetti
[17:52] <kgunn> that one can be unblocked now
[17:52] <robru> jibel: ok I don't know when I can fix this by but at least I have something to go on now
[17:52] <kgunn> and that was our goof, sorry
[17:53] <jibel> kgunn, done
[17:54] <jibel> robru, ok
[17:54] <kgunn> ta
[17:56] <boiko> jibel: hi, in the spreadsheet I had silos 15 and 40 marked as ready for QA to test, but I don't see it in the QA spreadsheet, could you please just check why they are not there?
[17:57] <boiko> robru: quick question: rvr has tested and approved silo 8, do I need to do anything for it to get published?
[17:57] <robru> boiko: pinging me is a good start
[17:58] <boiko> robru: still getting familiar with the new UI, glad we got rid of the spreadsheet :)
[17:59] <robru> boiko: yeah things are exploding right now, sorry this transition is going to be a little rough
[18:01] <boiko> robru: no worries,I will just be pinging you more often but no worries regarding transition problems, that's fine
[18:03] <AlbertA> cihelp: ^ this is powerd so it will fail boottest due to the package install failing to update config-default.xml being in a seperate ro partition
[18:04] <jibel> boiko, they are not there because the spreadsheet doesn't update the statuses in the dashboard anymore because of the migration to the new system.
[18:05] <jibel> boiko, we'll add the cards
[18:07] <jhodapp> robru, is the second to last line about Bileto going to be fatal or just ignore? https://ci-train.ubuntu.com/job/ubuntu-landing-038-1-build/42/console
[18:07] <robru> jhodapp: this is a spreadsheet landing right? if so it's fine, it's just trying to push the status to bileto and bileto doesn't recognize the id number. not fatal
[18:08] <robru> jhodapp: if that's a request from bileto though then that's a problem (still not fatal but not good)
[18:08] <jhodapp> robru, yeah it was a spreadsheet landing
[18:08] <robru> jhodapp: yeah no worries then
[18:08] <jhodapp> excellent, thanks!
[18:08] <robru> jhodapp: you're welcome
[18:09] <jhodapp> looking forward to using your work in bileto
[18:11] <jibel> boiko, what are the lines for silos 15 and 40?
[18:13] <boiko> jibel: let me look, just a sec
[18:13] <jibel> boiko, nm, found it
[18:13] <boiko> jibel: ok
[18:13] <jibel> robru, no pressure, but hurry up, I won't create cards manually for a long time :)
[18:15] <robru> jibel: yeah sorry. I will migrate the spreadsheet later today, just putting out fires right now
[18:22] <fginther> AlbertA, thanks for the heads up. Looks like it hasn't hit proposed just yet as it isn't in the excuses report
[18:48] <psivaa> robru: http://s-jenkins.ubuntu-ci:8080/job/bileto-ci has been added but http://s-jenkins.ubuntu-ci:8080/job/bileto-ci/1/console sees some failures. If you'd please take a look and let us know what are the dependencies, we'd be able to fulfill
[18:49] <robru> psivaa: oh thanks
[18:49] <robru> psivaa: one sec
[18:49] <robru> psivaa: the dependencies are here: http://bazaar.launchpad.net/~cupstream2distro-maintainers/bileto/charm/view/head:/hooks/install#L19
[18:50] <robru> psivaa: of which some are only accessible in trusty-cat-ue archive
[18:51] <robru> psivaa: you'll need to add "deb http://archive.admin.canonical.com/ubuntu trusty-cat-ue main" archive to get all the deps
[18:51] <psivaa> robru: ack, will take a look at adding them
[18:52] <kgunn> robru: hey, so i just tried to reconfig silo 0 via the old sheet....is that doable ?
[18:52] <kgunn> e.g. for old silos, do we still go thru the sheet?
[18:52] <robru> kgunn: yes the spreadsheet should be usable for reconfiguring, what are you seeing?
[18:52] <kgunn> robru: it could very well be me
[18:52] <kgunn> https://ci-train.ubuntu.com/job/prepare-silo/5573/console
[18:52] <robru> kgunn: yes for this moment we go through the old sheet for reconfiguring existing silos. I'm working on migrating the data but it's not ready yet
[18:53] <robru> kgunn: yeah, it's you: https://code.launchpad.net/~mir-team/mir/silo0/+merge/264015 404
[18:54] <kgunn> robru: nvmd (sheepishly)
[18:54] <kgunn> robru: helps if you actually paste the link you want in the cell....
[18:54] <kgunn> gaahhh!
[18:54] <robru> kgunn: lol no worries. I should clean up those tracebacks and make the errors more readable
[18:56] <robru> psivaa: certain failures are expected at this point, if you get a CI run that looks like this: https://pastebin.canonical.com/136541/ then you know all the deps are available and everything is working
[19:10] <kenvandine> trainguards: silo 2 is marked as QA granted, but the status on the dashboard doesn't say it's ready to publish
[19:10] <robru> kenvandine: yeah sorry it's a mess, thanks for pinging me
[19:11] <kenvandine> robru, no worries, just want to make sure nothing's holding it up :)
[19:11]  * kenvandine really wants to see passing CI again :)
[19:11] <robru> kenvandine: well, no statuses are being reported anywhere, so that's holding it up
[19:11] <robru> kenvandine: if you see it has QA granted (in the trello board?) you can publish it
[19:11] <kenvandine> cool
[19:11] <kenvandine> i'll do that :)
[19:11] <kenvandine> robru, just making sure
[19:11] <kenvandine> thanks!
[19:11] <robru> kenvandine: dashboard won't report qa statuses for spreadsheet stuff
[19:11] <robru> kenvandine: you're welcome
[19:12] <jibel> robru, brendand marked is qa granted in bileto
[19:12] <jibel> it*
[19:12] <kenvandine> yeah, that's where i saw it
[19:12] <kenvandine> not the spreadsheet
[19:13] <kenvandine> ugh... should i be concerned with this?
[19:13] <kenvandine> 2015-07-30 19:12:49,226 ERROR Bileto says: 400 BAD REQUEST
[19:13] <kenvandine> but it finished with SUCCESS
[19:13] <davmor2> robru, sil2100: silo51 is good to go
[19:13] <robru> davmor2: thanks
[19:21] <AlbertA> fginther: powerd is listed in excuses now.
[19:24] <kenvandine> robru, i think something blew up there publishing to wily, silo 2
[19:24] <kenvandine> i see it in the overlay ppa for vivid, but no change mail yet for wily
[19:25] <kenvandine> that 400 error makes me think something didn't happen
[19:25] <robru> kenvandine: no that's fine
[19:25] <robru> kenvandine: the 400 error is just bileto saying "I don't know this requestid"
[19:25] <kenvandine> it's been over 10 minutes and no wily change mail
[19:25] <kenvandine> ok...
[19:26] <kenvandine> it's usually quicker than this
[19:26] <robru> kenvandine: log?
[19:26] <kenvandine> https://ci-train.ubuntu.com/job/ubuntu-landing-002-2-publish/116/console
[19:27] <boiko> robru: silo 34 was saying address-book-service is outdated, so I tried rebuilding it, but it failed with the error seen on the dashboard
[19:27] <kenvandine> robru, maybe it will work... just i got worried :)
[19:27] <robru> kenvandine: that log is fine but indeed cicopy is broken
[19:27] <boiko> robru: there was actually no landing in there, but the changelog shows an entry from the citrain: https://launchpad.net/ubuntu/wily/+source/address-book-service/+changelog
[19:27] <robru> boiko: ok just wait a moment
[19:28] <kenvandine> robru, ok, so you'll handle it?
[19:28] <boiko> robru: no hurry, just letting you know
[19:28] <robru> kenvandine: yeah
[19:28] <kenvandine> robru, thx
[19:33] <robru> kenvandine: ok it should be fixed, but the cicopy thing only runs every 5 minutes, so you should see that within 5 minutes or so. I gotta eat, brb
[19:36] <robru> kenvandine: ok looks good
[19:37] <robru> boiko: yeah so address-book-service is in -proposed, I'm assuming another silo already published and hasn't merged yet. that's why you're getting that error.
[19:37] <robru> boiko: in fact silo 28 needs to migrate before you can rebuild
[19:38] <boiko> robru: ah ok, found it, silo 28
[19:38] <boiko> robru: ok, thanks
[19:38] <robru> boiko: you're welcome
[19:41] <kenvandine> robru, thx!
[19:42] <kgunn> robru: can you help me with a game of what-am-i-doing-wrong
[19:42] <robru> kgunn: in a sec, i have some food on the stove
[19:43] <kgunn> robru: nw, i'll type here, just when you get a chance
[19:44] <kgunn> so in silo42, it gave me an error about changelog versioning, so i bumped it
[19:45] <kgunn> it's just a demo silo, so i changed the deb version string from 2015 to 2016, thinking that should make it not complain for a while
[19:46] <kgunn> but what's weird is in the output
[19:46] <kgunn> https://ci-train.ubuntu.com/job/ubuntu-landing-042-1-build/21/console
[19:47] <kgunn> don't know how why it's comparing to another deb string containing 2016 (as in the year)
[19:54] <robru> kgunn: your using a branch that has been released to wily but your silo targets vivid. If you read the error not closely it says 15.04 is less than 15.10.
[19:54] <robru> kgunn: you need to either do a dual silo or change your changelog to say 15.04
[19:54] <kgunn> ah ok
[19:55] <kgunn> thanks
[19:55] <robru> kgunn: your welcome
[20:02] <kgunn> robru: when specifying dual, do we also need to specify destination ppa (stable phone) ?
[20:02] <robru> kgunn: no don't do that
[20:03] <robru> kgunn: dual is always overlay. If you set the overlay that means you want wily packages in the overlay
[20:03] <kgunn> ah
[20:03] <kgunn> i didn't do that...i saw others by convention, just confirming
[20:04] <robru> kgunn: i may have put in a check to stop that from happening but i can't remember if I just dreamed it
[20:05] <kgunn> i think it was always the same in the old sheet too
[20:05] <kgunn> e.g. possible, but no one used it
[20:05] <fginther> AlbertA, powerd should be unblocked shortly
[20:05] <robru> kgunn: dual silo is just a wily silo with a vivid overlay tumor, all the options control the wily half, vivid half is all hard coded
[20:08] <kgunn> robru: ^ just a little bug, i switched to dual, then hit "assign" and i thot huh, why does it say vivid....then it failed ^, second time it says "dual" like i expected
[20:13] <AlbertA> fginther: ack
[20:14] <robru> kgunn: maybe your clicked assign before the edit saved?
[20:14] <robru> kgunn: there's an ajax roundtrip after clicking save, should be fast but maybe it was slow that time or something
[20:14] <kgunn> robru: i don't think so...but i do feel like i'm getting logged out incessantly
[20:15] <robru> kgunn: yeah the log out thing is just the backend being crap, I'm working on it
[20:15] <kgunn> k
[20:15] <kgunn> that was prolly it
[20:15] <kgunn> just raced out
[20:27] <AlbertA> robru: how do I sync packages from wily to vivid+overlay now? Do I put ubuntu,wily in Sync source? and package names in "Manual Source Packages" box?
[20:37] <robru> AlbertA: yeah
[20:37] <robru> AlbertA: hover over the fields should explain a bit, please email me if anything is unclear and i can expand it.
[20:38] <AlbertA> robru: thanks yeah they were self-explaining...just wanted to confirm :)
[20:38] <AlbertA> robru: could we have a ubuntu,wily option in the dropdown in Sync source?
[20:39] <robru> AlbertA: also if you double click on the sync field it suggests some common options
[20:39] <robru> AlbertA: Hmmmmmmm if that not in there already?
[20:44] <AlbertA> robru: I don't see it in the dropdown
[20:44] <robru> AlbertA: ah I see it's just ubuntu,vivid. Ok I can add that but I won't be able to roll it out until later
[20:45] <AlbertA> robru: also can I delete duplicate entries...I got logged out  while saving one clicked again.
[20:45] <robru> AlbertA: you can't delete them but just set the status to 'Abandoned' and it'll disappear
[20:45] <AlbertA> robru: cool thanks
[20:45] <robru> AlbertA: you're welcome
[21:11] <charles> is anyone else having trouble staying logged into https://requests.ci-train.ubuntu.com/ ?
[21:13] <dobey> i can't log in at all on it; it just always has the "Log in with Ubuntu SSO" button
[21:13] <dobey> trainguards: ^^
[21:14] <robru> dobey: charles: yes there are some known issues unfortunately, keep trying
[21:14] <robru> charles: dobey: if you get logged out, don't actually try to log in again, just reload the page.
[21:15] <charles> robru, ack
[21:15] <charles> thanks for that; I've been re-logging in several times
[21:15] <dobey> oh now there's some content
[21:15] <charles> ya, same here
[21:15] <robru> charles: dobey: yeah sorry I need to make it give a real error message, right now unfortunately it just appears logged out without actually being logged out
[21:15] <dobey> well i can't see how to actually create a new request
[21:16] <robru> dobey: you need to log in to get the new request form
[21:16] <charles> robru, no worries, rollouts are never perfect. I appreciate the tip
[21:16] <robru> dobey: but if it's not showing any requests at all, that's a backend issue, requests should be visible even if logged out
[21:16] <dobey> i thought i was logged in
[21:16] <robru> dobey: if you can see the requests but still the login button then you're definitely not logged in
[21:17] <robru> dobey: if you can't see the requests but see the login button, that's an error state that's indeterminate.
[21:17] <dobey> robru: i mean, i clicked on log in and performed that loop about 20 times
[21:17] <robru> dobey: what are you seeing?
[21:17] <dobey> well now i can see the request form
[21:17] <dobey> so apparently i wasn't logged in
[21:18] <charles> dobey, that's what I was seeing as well. I'm not sure what changed s.t. I finally got logged in
[21:18] <robru> dobey: it's possible. I don't know what the hell is happening, stuff that worked fine in staging is exploding in production.
[21:18] <dobey> but seems backend issues make it difficult to know whether i am actually logged in or not
[21:18] <dobey> robru: that's the problem; you put it in production :)
[21:18] <robru> charles: dobey: a good way to troubleshoot is to visit https://requests.ci-train.ubuntu.com/v1/tickets. If you get a 500 error, the backend is broked, try reloading. if you get a json blob then it's all good
[21:21] <dobey> could use some "responsive design" improvements; i like small fonts, but with these colors, it's a bit too small to fit in a single window without horizontal scrolling on my crazy 4k monitor :)
[21:21] <dobey> ah well
[21:21] <robru> dobey: what? I have a 1080p that doesn't horizontally scroll
[21:22] <dobey> robru: doesn't horizontally scroll with a full screen/maximized browser you mean?
[21:22] <robru> dobey: yeah, maximized
[21:23] <dobey> yeah, i use windows
[21:23] <robru> dobey: well, considering the spreadsheet would scroll horizontally through three screenfuls I think this is a win. if you can't maximize your screen then I can't help you :-P
[21:24] <dobey> but my browser is 1266px wide
[21:24] <robru> dobey: why is it even horizontally scrolling? shouldn't the longer cells be wrapped?
[21:24] <dobey> robru: eh, i hated the spreadsheet horizontal scrolling too. but it's a spreadsheet, and it's google's, so not much we can do about that
[21:24] <robru> dobey: somebody already complained about horizontal scrolling and I already fixed it
[21:24] <dobey> some are wrapped
[21:25] <dobey> but the new request block at the top isn't wrapping all the text entries
[21:25] <robru> dobey: it's a free form text field, why would it wrap?
[21:26] <dobey> robru: why do i need four of them in the same row? why can't they stack?
[21:26] <robru> dobey: they correspond to the displayed rows beneath. it's like a row header.
[21:28] <dobey> so why can't the stuff below wrap at the same places too?
[21:28] <robru> dobey: because it's tabular data inspired by the spreadsheet. I basically took one huge google row and broke it into two manageable rows.
[21:32] <charles> robru, it doesn't stop work from getting done, but minor bug report: Status for the pay-service req I'm on now is listed as "Silo ready to build" but it started building 7 minutes ago
[21:32] <robru> charles: yeah that's probably related to the 500s in the backend
[21:58] <robru> AlbertA: 11 is ready for qa?
[21:59] <AlbertA> robru: silo 8 yes...
[21:59] <michi> robru: Can you help with this? https://ci-train.ubuntu.com/job/ubuntu-landing-051-2-publish/6/console
[21:59] <robru> michi: one sec
[21:59] <michi> Sure!
[22:00] <robru> michi: you need an archive admin, please ask in #ubuntu-release. I already pinged there and got no response
[22:01] <michi> Ah, I see. Thanks, will try!
[22:05] <charles> robru, so if I don't need QA signoff and am ready to publish, I would do that by editing the signoff status, yes?
[22:05] <robru> charles: yes you can set that to 'Publish without QA'
[22:05] <charles> robru, thanks
[22:31] <AlbertA> trainguards: I don't see a card entry in the QA trello board, for silo 8, which is ready for QA... do I just need to wait?
[22:32] <robru> AlbertA: no you need to ping qa if it's a spreadsheet landing, everything is broken I'm afraid.
[22:32] <AlbertA> robru: it's an entry in the new one
[22:33] <robru> AlbertA: what number?
[22:33] <AlbertA> 11
[22:33] <robru> AlbertA: ok, bileto is literally on fire, so qa bot probably can't access the API to know that it's ready. ping some qa person to get it on the queue
[22:34] <AlbertA> robru: ack thanks
[22:34] <thomi> robru: umm "literally on fire"
[22:34] <robru> thomi: LITERALLY
[22:34] <thomi> ...pics, or it didn't happen :P
[22:35] <robru> thomi: http://images.rapgenius.com/4jh2iqo0mlekbviwkr97w46m6.450x600x1.gif
[23:40] <AlbertA> robru: looks like duplicate entries to the QA trello board are being added periodically...I saw 3 about 15mins later 4, about another 15 mins later 5...https://trello.com/b/AE3swczu/
[23:40] <AlbertA> robru: ooh now 6....
[23:40] <robru> AlbertA: that would be qa's job to fix, I don't make those
[23:41] <AlbertA> robru: ack
[23:41] <robru> AlbertA: most likely jibel's bot has a bug