14:00:33 #startmeeting fedora-qadevel 14:00:33 Meeting started Mon May 30 14:00:33 2016 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:33 The meeting name has been set to 'fedora-qadevel' 14:00:34 #meetingname fedora-qadevel 14:00:34 The meeting name has been set to 'fedora-qadevel' 14:00:34 #topic Roll Call 14:00:45 * mkrizek is here 14:00:49 Who all's around for the fun of a qadevel meeting? 14:01:44 * jskladan is here 14:02:07 welcome, welcome 14:03:23 is it just the 3 of us today? 14:03:32 * tflink knows that kamil won't be here 14:03:48 seems like it garretraziel said he'll come, but he's probably still on the way 14:04:58 ok 14:06:21 let's get started, I guess 14:06:37 this seems like an awful lot of process for just 3 of us, though :-/ 14:06:46 at least we'll have record of accomplishments :) 14:06:48 :D 14:06:58 #topic Announcements and Information 14:07:17 #info newest libtaskotron, resultsdb, task-abicheck, task-dockerautotest deployed to stg, prod - mkrizek 14:07:17 #info resultsdb_api package is in Fedora - mkrizek 14:07:17 #info task-libabigail renamed to task-abicheck 14:07:17 #info task-abicheck now reports a single result per item, not split by arch - kparal 14:07:17 #link https://github.com/sinnykumari/task-libabigail/pull/4 14:07:18 #info libtaskotron is now correctly updated on minion even when the cache is outdated and an older package is already installed - kparal 14:07:21 #link https://phab.qadevel.cloud.fedoraproject.org/T798 14:07:23 #info koji directive and koji utils can now exclude a specific arch from downloading (to be used by task-abicheck) - kparal 14:07:26 #link https://phab.qadevel.cloud.fedoraproject.org/D857 14:07:28 #info openQA: we have officially first test on ARM - initial-setup test - jsedlak 14:07:53 any questions, comments? 14:08:21 none here 14:08:24 not here 14:08:30 none 14:08:43 * garretraziel greets everyone 14:09:03 mkrizek: are you still working on that blog post about task-abicheck and task-dockerautotest? 14:09:22 tflink: yes, will post tomorrow 14:09:36 mkrizek: cool, just wanting to make sure something gets written 14:09:45 * tflink wonders if we should post to devel@ as well 14:09:58 not sure how many devel@ folks watch fedora planet 14:10:16 sounds like a good idea to me 14:10:43 I do, but quite irregularly, so +1 for posting to devel 14:11:12 mkrizek: you want an action for this or should I take it? 14:11:19 tflink: does just sending a link there work? 14:11:38 I would tailor it a bit more for a different audience 14:11:53 and write at least some of it out 14:12:13 ok, I can do it 14:13:20 mention that it's just informative right now, there are some packages which we aren't running due to memory and others due to human bandwidth, shoutout to the libabigail folks and ask for folks to report issues they find 14:13:23 etc. 14:13:31 not sure what you were planning to put in the blog post 14:14:10 #action mkrizek to write blog post and devel@ post about the new deployment changes from friday 14:14:20 which reminds me, I should chair folks 14:14:27 #chair mkrizek jskladan garretraziel 14:14:27 Current chairs: garretraziel jskladan mkrizek tflink 14:14:40 mkrizek: if you'll want to help with task-dockerautotest part, just say so 14:14:47 ok, any more questions, coments? 14:14:50 I was planning to keep it short, just a note that we run those checks and that the checks are more like informative, like you said 14:15:17 mkrizek: i think you can be a bit more expansive, this is a pretty big deal in my mind 14:15:29 abi checking has been on the wish list for how many years? 14:16:16 as long as I can remember :) 14:16:52 longer than I've been around, definitely 14:17:45 anyhow, if there are no more questions/comments, we can move on 14:18:02 * tflink looks at the remaining topics 14:18:27 jskladan: do you think that the base image question can be tabled for another week? 14:18:47 tflink: sure 14:19:19 that seems like a topic that kparal might want to participate in and may have some good input 14:19:56 docker testing is a little silly without lbrabec 14:20:04 which leaves us with 14:20:08 #topic Packaging 14:20:15 everyone's favorite pastime :) 14:20:30 I am planning to send taskotron-trigger and libtaskotron for review this week 14:20:35 cool 14:20:48 I am waiting for resultsdb_api to be pushed to stable before sending libtaskotron for review though 14:21:01 #info taskotron-trigger and libtaskotron will likely be submitted for review this week 14:21:15 #info testing, karma on resultsdb_api update is needed 14:21:38 note that the package is named 'python-resultsdb_api' 14:21:44 #undo 14:21:44 Removing item from minutes: INFO by tflink at 14:21:15 : testing, karma on resultsdb_api update is needed 14:21:51 #info testing, karma on python-resultsdb_api update is needed 14:21:54 * tflink forgot about that 14:22:22 i suspect that everything is going to have the python- prefix 14:22:41 hm, isn't it just for libraries? 14:22:55 or API's 14:23:03 not sure, it's been a little while since I was looking at the specifics of package naming 14:23:23 we'll see 14:23:44 on a barely related note, is there a ticket filed to make resultsdb_api python3 capable? 14:23:54 I don't think so 14:24:17 * tflink has been burned by that more than once, keeps forgetting that it's py2 only 14:25:29 mkrizek: is there anything you want/need help with? 14:25:45 * tflink saw the trigger review, planning to get to that after the meeting 14:25:58 just the review I guess 14:26:15 and then finding a package reviewer :) 14:27:09 that shouldn't be too bad, several people said that they'd be willing to help out with reviews 14:27:15 cool 14:27:21 otherwise we can do swap requests on devel@ 14:28:13 anything else here? 14:28:54 * tflink assumes not, moving on 14:28:57 #topic Tasking 14:29:02 is anyone in need of stuff to do? 14:29:33 * mkrizek has stuff to do 14:29:49 I will be, most probably, later this week. I've looked at plannig, and it seems like most of the tasks are infrastructure/packaging related 14:30:16 what's the best to focus on, right now? 14:33:14 jskladan: are you a packager? 14:33:22 tflink: not that I know 14:35:14 I would say documentation and getting some examples together for docker image checks and package specific checks 14:35:22 as fun as that is :) 14:35:52 OK, I'll get together with lbrabec, and we'll put together the docker examples 14:36:32 * tflink put "file more tickets on docker image testing, documentation" on his todo list 14:36:33 tflink: I had packaged some packages 14:36:46 so if you need review or something... 14:36:57 garretraziel: if you have the cycles, I suspect that mkrizek would appreciate the help :) 14:37:13 ok 14:37:31 there are two or three packages left to send for review 14:37:46 that being said, I'm gonna have to get reviews for phabricator at some point in the not-to-distant future 14:37:46 execdb, resultsdb and resultsdb_frontend 14:39:37 feel free to poke me if you're looking for a task, or just take something off of the "next tasks" list in https://phab.qadevel.cloud.fedoraproject.org/project/view/28/ 14:39:51 which brings us to 14:39:55 #topic Open Floor 14:40:05 any other topics to discuss? 14:40:44 not here 14:41:01 none 14:41:18 * tflink didn't think the meeting was going to take this long :-/ 14:41:32 at least we're ~ 20 minutes early and IIRC, no qa meeting today 14:41:49 * tflink lights a very short fuse 14:42:57 Thanks for coming, everyone 14:43:02 * tflink will send out minutes shortly 14:43:05 #endmeeting