[04:47] ogra_: I'm not available for the evening meetings myself [04:51] Mirv: ogra_: cancel ALL the meetings! [05:22] hmm, I'll ask about dbart's 052 when he's around in a couple of hours [06:18] michi: I was thinking, could you actually come up with for example a simple QML file that does the same accessible() test you're looking for at bug #1470700? that way it wouldn't need you to test the fixed version. but now there's the latest version at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-032/+packages again [06:18] bug 1470700 in qtbase-opensource-src (Ubuntu) "QNetworkAccessManager hangs when in flight mode" [High,Confirmed] https://launchpad.net/bugs/1470700 [06:21] Mirv: Looking. I didn’t make it into the office today, but the Mako is there, so I can’t test with the phone until tomorrow morning. [06:23] michi: ok. if you know the piece of code in the scopes, maybe it's possible to come up with a test case anyway. but otherwise, until tomorrow. [06:24] Mirv, James attached a stand-alone test to bug 1470700. [06:24] bug 1470700 in qtbase-opensource-src (Ubuntu) "QNetworkAccessManager hangs when in flight mode" [High,Confirmed] https://launchpad.net/bugs/1470700 [06:24] Scopes are not affected. [06:24] This was a problem for the thumbnailer. [06:24] But we added a work-around, so thumbnailer is no longer affected even if this stays broken. [06:27] michi: oh, sorry, my mistake, too many projects flying around in my mind :) [06:27] Yeah :) [06:27] Anyway, could you test with James’s test case, or shall I do that tomorrow on the phone? [06:27] michi: but that test case from James was AFAIK for the QNAM hang problem, not the accessible() problem you then later mentioned? [06:27] Ah, I see. [06:28] michi: I've tested the James' test case and it does get fixes with the patch, but the two other patches are what could affect this accessible() one [06:28] Well, I can drop some trace into our code tomorrow to see what it says now when flight mode is on. [06:28] I see. [06:28] OK, I can test that tomorrow and find out. [06:28] michi: ok, thanks! and good evening/night. [06:28] Must be very late for you. [06:28] It’s late afternoon here... [06:29] no, early for me :) I was estimating a bit wrongly your TZ [06:29] Ah :) [06:29] Where are you? [06:29] Finland, ie UTC+3 at the moment [06:29] Ah, I see. [06:29] Good morning then :) [06:29] thank you :) === chihchun_afk is now known as chihchun [07:24] Mirv, do you know if wily is working now on any phone? I flashed krillin and after a while it starts rebooting in a loop [07:38] abeato: it was on my mako the last time I checked maybe a week ago [07:39] Mirv, ok, thanks [07:41] Mirv, could you publish silo 57 for me (wily)? I don't have permissions [07:54] hmm... did the abandon button disappear in bileto? [07:55] meh [08:00] abeato: it's not marked as ready for publishing. you should set it to "Publish without QA" [08:01] Mirv, ok, let me try that [08:01] mzanetti: yes. if you free a silo (via a trainguard), the landing will be abandoned. it's also possible to set up the status manually. [08:02] Mirv, do I need to reconfigure after changing that? [08:02] Mirv, I had one of those accidentally double-clicked assigned entries in bileto which I wanted to abandon. but no prob, I'll just edit it and use it for the next landing [08:02] because I still do not have permissions to publish [08:04] abeato: publishing is a trainguard thing. You don't need to reconfigure after setting the qa status. [08:04] abeato: setting the qa status just makes it show up in the place where we notice to publish it. [08:05] robru, got it, thx [08:05] abeato: you're welcome [08:05] abeato: no, you just set it, then we know to publish it (it shows up) [08:06] Mirv: got some good news buddy, i have working db migrations for the first time so you'll soon be able to specify all the packages you need in your silos [08:07] robru: sounds good! [08:08] Mirv: goodnight! [08:10] robru: nights! [08:20] dbarth: see the question regarding landing-052 in bileto [08:21] dbarth: is it mistakenly reconfigured to wily only or something? I can fix that to dual + publish if needed [10:28] abeato: top approval missing https://code.launchpad.net/~alfonsosanchezbeato/media-hub/bump-version/+merge/269718 [10:34] Mirv, MP just approved [10:44] abeato: thanks, trying again! [10:45] Mirv, cool, thanks [11:27] psivaa, hey, did you get any further with https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-vivid/916/console ? [11:27] psivaa, the others still build fine... just that vm doesn't [11:28] for example this one installs libunity-api-dev >= 7.100 just fine: https://jenkins.qa.ubuntu.com/job/unity8-overlay-vivid-amd64-ci/15/consoleFull [11:31] mzanetti: not particularly, I could not figure out the right way here, enabling overlay ppa with VM's (experimentally) did not help. [11:32] mzanetti: i am planning to talk to fginther today about it [11:32] psivaa, ok. thanks === chihchun is now known as chihchun_afk === alan_g is now known as alan_g|lunch === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === alan_g|lunch is now known as alan_g [13:14] robru: FYI for your shift I didn't get a reply from dbarth regarding the silo 052 [13:38] morphis: Approving silo 9 [13:38] morphis: Hmm... I also have silo 59, which seems similar [13:39] morphis: Same merge proposal? [13:40] rvr: I uploaded 59 along 9 but both are fine to land independent of each other [13:41] morphis: But they both link to this merge proposal https://code.launchpad.net/~morphis/ubuntu-system-settings/fix-device-actions/+merge/269188 [13:41] morphis: So, what's the difference? [13:41] Mirv, any idea what's going on here? https://ci-train.ubuntu.com/job/ubuntu-landing-055-1-build/12/console [13:42] jhodapp: I approved silo 48 some hours ago [13:42] rvr: no they don't [13:42] morphis: https://trello.com/c/zIJZF0d8/2231-270-ubuntu-landing-059-bluez-morphis [13:42] morphis: https://trello.com/c/iU9Akwg2/2230-271-ubuntu-landing-009-ubuntu-system-settings-morphis [13:42] morphis: fix-device-actions [13:43] the card is wrong then, see https://requests.ci-train.ubuntu.com/#/tickets?search=HID [13:43] I remember I put both into the same silo first but was then reminded that this doesn't work [13:43] maybe the card wasn't updated correctly then by the system [13:43] but the MP is for sure not part of silo 59 [13:44] it only has an updated bluez package in it, see https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-059 [13:44] morphis: Merges: https://launchpad.net/~morphis/ubuntu-system-settings/fix-device-actions/+merge/269188 [13:45] jhodapp: hmm, sorry, no, I don't find anything wrong with the request and the branch + MP URL:s load up fine in browser when copy-pasted. as you've seemingly tried it multiple times already, show it to robert when he's online. [13:46] morphis, you have to click assign again after changing that to reconfigure [13:46] maybe you only saved [13:46] it's not all that intuitive [13:46] kenvandine: I did that last week when you reminded me :) [13:46] ok [13:46] rvr: I think we can simply drop the link from https://trello.com/c/zIJZF0d8/2231-270-ubuntu-landing-059-bluez-morphis, right? [13:47] morphis: In the description of the PPA (not in trello) you link to fix-device-actions [13:47] morphis: What's the correct branch? [13:48] narf, looks like the "assign" did stripped that out of the ppa description [13:48] s/did/didn't/ [13:49] trainguards: Hi, I've created a new project https://code.launchpad.net/~indicator-applet-developers/gmenuharness/trunk and would like to include it for building on vivid and wily [13:49] morphis: Also, on the CI train dashboard, there is no merge proposal linked [13:49] trainguards: is the first time I create a project from scratch, so I don't know if there's any documentation I should read first [13:49] Mirv, ok will do, thanks [13:49] rvr: ok, to get this right: 009 is correct, it's linked to https://launchpad.net/~morphis/ubuntu-system-settings/fix-device-actions/+merge/269188 [13:49] morphis, i published 9 :) [13:50] 059 should just land one manual upload of bluez [13:51] rvr: does that look better: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-059? [13:51] kenvandine: thanks! [13:52] morphis, silo 59 needs a watch only build now [13:52] then i guess that should be good [13:52] ok [13:53] rvr, kenvandine: done [13:54] morphis: Ok, so, how can I test silo 9? Is there any manual test case? [13:55] rvr: we don't have any other test cases written down other than the settings ones [13:55] however, do you have a bt keyboard available? [13:57] morphis: Nope [13:57] sigh [13:57] rvr: ok, then normal settings bt tests are all we have [14:00] morphis: When duties allow, alesage will test silo 59, he has a bluetooth keyboard [14:01] sounds good [14:01] alesage: please ping me when you're going to test that silo [14:01] morphis, ok [14:02] I can give you some further test steps then [14:10] alesage: quick writeup of what is worth to test with HID reconnect: https://docs.google.com/document/d/1MIb0oIYTpuii6ptex64pMDnwATyYMtBD-0CFKHg667w/edit# [14:10] that will end up later in a better written form as a test case [14:10] remember that davmor2_HOLS wanted to write some [15:42] mzanetti: http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-vivid/922/console has continued on the build, but has some test failures, [15:43] mzanetti: thanks to fginther, the overlay ppa was added to the right place. [15:43] psivaa, test failures are good. that's what we're after :) [15:45] psivaa, so the next push to a branch should put those results to LP too? [15:46] * mzanetti tries [15:46] mzanetti: right, that should happen [15:46] psivaa, ok, I'll watch it. That log looks good! Thanks a lot! [15:51] mzanetti: glad to hear. thanks to fginther :) === alan_g is now known as alan_g|EOD [17:15] popey: There is a problem with the gallery-app in Spanish. Along the month, it says "AAA". I think someone translated the year code as "AAA". [17:15] popey: e.g. "AGO. AAA 23" [17:16] rvr: → bfiller [17:16] bfiller: ^ [17:16] popey: Right, is not a community app, sorry [17:17] https://translations.launchpad.net/gallery-app/trunk/+pots/gallery-app/es/+translate?batch=10&show=all&search=AAA [17:17] There it is [17:18] robru, are the urls of the form https://requests.ci-train.ubuntu.com/static/json/ gone? [17:19] jibel: yes [17:19] jibel: that's part of the dashboard which I announced was going away [17:20] jibel: you should now rely exclusively on /v1/ URLs [17:21] robru, ah, I didn't know it was part of the dashboard [17:21] jibel: ah sorry that wasn't clear. let me know if there's any information that you can't get from /v1/ and I'll add it [17:22] robru, there was a nice dict for the MPs which doesn't seem to be in the /v1/ URLs [17:23] rvr: np [17:24] jibel: true, the MPs in /v1/ are the "raw" form as entered by the user. the /static/ ones were processed by jenkins and had that dict. I won't be able to bring that back immediately unfortunately but that's something I'm working on [17:25] robru, okay, I'll parse the merge_proposals entry but it is error prone [17:26] jibel: how error prone can it be? that's how the train does it to generate the dict you want ;-) [17:26] jibel: what do you need? just the source package names? you can query the PPA for that. [17:26] robru, the job was already done, I assumed it was right :) [17:27] robru, don't worry, I'll find a way. [17:27] jibel: sorry for the hassle. things should be settling down now. /v1/ is stable now that /static/ is gone. [17:29] jibel: what you need to do depends on if you want to know lp project names or ubuntu source package names. project names can be parsed from the URL, package names will require lplib to load the resource and query [17:29] robru, sure, at least until next roll out ;) [17:30] jibel: I roll out at least twice a day, it only causes problems very rarely :-P [17:30] robru, that's find I'll query LP. I need something meaningful to write in the description of the ticket [17:30] fine* [17:35] mzanetti: Approving silo 19 [18:07] robru, can you tell me what's going on here? https://ci-train.ubuntu.com/job/ubuntu-landing-055-1-build/12/console [18:07] jhodapp: exactly what it says: 404. that MP does not exist. [18:07] jhodapp: it looks like somebody put a new MP in the request and then didn't reconfigure. [18:08] hmm, let me try another reconfigure [18:09] robru, that error isn't very clear [18:09] jhodapp: according to the ppa description, the last reconfigure had https://launchpad.net/~phablet-team/media-hub/enable-mpris-controls/+merge/269106 which is clearly a 404, so the job failing is no surprise. [18:09] robru, yeah I probably forgot to reconfig [18:10] robru, still seem to be getting it: https://ci-train.ubuntu.com/job/ubuntu-landing-055-1-build/13/console [18:11] jhodapp: according to the bot you just assigned a new request in silo 60, you don't seem to have done anything to silo 55. [18:11] jhodapp: when in doubt, check the PPA description: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-055 it still lists the 404'ing MP [18:12] robru, ugg, that's the second time something like that's happened...the floating controls sometimes the wrong silo controls appear but they're close enough to visually feel like the correct ones [18:12] jhodapp: I'm not sure how I can make that any clearer. the active row highlights in orange and the hover controls hug the edge of it perfectly [18:14] robru, yeah not sure either, but I've repeatedly made this UX error [18:15] jhodapp: assuming you were looking at this page: https://requests.ci-train.ubuntu.com/#/user/jhodapp the hover controls for silo 60 would have obscured most of the row for silo 55. [18:15] robru, it's very clear when being very intentional, but when doing things a little more reactively it happens [18:15] jhodapp: I mean I could dim the rest of the page when one request is hovered but that would get distracting with the page constantly dimming and undimming. [18:16] robru, I wonder if it would make a difference just being on the right side of the table [18:16] robru, also, if that orange bar spanned the entire table width [18:17] jhodapp: I'm not sure that that's possible (or at least I'm not good enough at CSS to know how to do that). it's not as simple as "align: right" or whatever, because it's positioned absolutely. [18:17] robru, can you do the entire width? [18:17] jhodapp: hmmm let me see [18:19] jhodapp: bah! If I set it to "width: 100%" it goes by screen width, not the width of the parent element. and because the left isn't aligned to the left of the screen it makes the right end go off the end of the page and cause horizontal scrolling. css is rubbish [18:20] lol [18:20] agreed, it frustrates me as well [18:21] jhodapp: I can make it be like "width: 75%" and then it's wider [18:21] jhodapp: sure looks funny having all the links on the left though and then this giant empty bar to the right [18:22] robru, oh I know what you could do... [18:23] robru, put a noticable border around the current cell that is hovered over that joins with the orange toolbar [18:23] jhodapp: lol I was literally JUST doing that ;-) [18:23] that will draw the eye to connect the cell and the toolbar better [18:23] robru, awesome, thinking alike :) [18:32] jhodapp: ok I pushed it to trunk, will roll out later with some other stuff. [18:33] robru, awesome, thanks you sir [18:33] jhodapp: you're welcome [18:33] jhodapp: silo 55 looks like it's configured correctly now if you want to build it [18:33] robru, yeah thanks, forgot to kick off the build :) [18:35] brb, lunch [20:19] cihelp, what is the process for getting CI set up for a new project? [20:22] bregma, one moment... [20:25] bregma, please send an email to canonical-ci-engineering@lists.launchpad.net with the branch name and what type of builds are needed. Often this can be answered by just saying, "build lp:foo just like lp:bar" [20:26] fginther, thanks [21:51] robru: hey, what's the process for deleting a silo attempt? [21:59] robru: actually nvm, I'll change the MP etc. so that I can reuse the same line [22:41] thomi: I started the subunit go: https://github.com/elopio/subunit [22:42] elopio: you should tell lifeless in #subunit [22:42] there are still things I don't get, like routing. But I think we will have a decent writter soon. [22:42] * elopio goes to tell people... [22:43] elopio: good work though - I look forward to seeing it in use! [22:43] elopio: nice! :-) [22:45] hey veebers. [22:50] hey elopio o/ how goes things [22:51] veebers: going good. I've just barely survived two weeks while Federico was on holidays. Luckily that's over. [22:51] veebers: how are you? [22:56] elopio: hah, glad to hear you survived :-) I'm well thanks, had a week off myself to go up and see a comedy show and sort some wedding stuff out [23:06] trainguards anyone around who might be able to double check something for me, silo 54 [23:06] alberta is vacation now, but he set it up for sync:mir [23:06] but the silo itself only seems to have qtmir in it (it was claiming dirty earlier) [23:07] and no u-s-c [23:07] what's the right way to get all the packages to show up ? [23:07] build again with "mir qtmir u-s-c" in the list ? [23:07] unsure of the "sync" procedure here [23:17] i tried...but then i got that ^ [23:17] mir is invalid ? [23:17] bbl [23:51] robru: heh, not sure which one of those 3 options I want, perhaps force_rebuild? (I've once again changed the MP for this silo and want to build the packages from that)