15:01:31 #startmeeting Fedora QA meeting 15:01:31 Meeting started Mon May 4 15:01:31 2015 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:33 #meetingname fedora-qa 15:01:33 The meeting name has been set to 'fedora-qa' 15:01:35 #topic Roll call 15:01:37 ahoyhoy folks, who's around for the QA meeting? 15:01:39 * kparal is here 15:01:47 * danofsatx is actually here today 15:01:50 woot! 15:02:12 * satellit listening 15:02:25 * pwhalen is lurking 15:03:14 * jreznik is here, ahoyhoy 15:03:58 morning all 15:04:13 or rather, all 15:05:07 * tflink is around 15:05:10 #chair kparal pwhalen 15:05:10 Current chairs: adamw kparal pwhalen 15:05:16 #topic Previous meeting follow-up 15:05:17 Hi 15:05:21 (he says, before checking if there is any) 15:05:22 hi val! 15:05:50 ah, just the one: 15:06:12 #info "adamw to complete fedup Test Day page" - did that, the test day went off pretty well. 15:06:27 anything else before we move on? 15:06:49 no,i don't think 15:07:42 okely dokely 15:07:42 #topic Fedora 22 Final status 15:07:46 #info currently under test: 22 Final TC1 15:08:01 i don't think we have any real big surprises here, just a check-in topic 15:09:08 anything of note, or are we just rolling along? 15:09:09 wow...I've discovered that Logitech wireless devices don't work well in F22 Plasma. 15:09:27 danofsatx: when you say 'logitech wireless devices', what do you mean? 15:10:29 I just purchased a Wave keyboard and MX510 mouse that use the proprietary Logtiech "Unifying Receiver". The keyboard works ~90% of the time, the mouse ~20%. 15:11:00 it locks up and is jumpy - I'm looking at the current thread in the mail list about the slow mouse to see if they're related 15:11:09 danofsatx: is it plasma 5 only? but it doesn't sound like anything we have to worry for f22, especially when you say proprietary 15:11:10 the wired mouse is fine. 15:11:28 i had some problem with chrome but nothing special 15:11:49 Firefox all right 15:12:16 * pschindl is here. 15:12:24 * satellit learned to use f22 virtual machine manager gui finally....for testing f22 cinnamon spin is available now 15:12:39 * satellit live 15:12:49 danofsatx: well, i'd say it could take more investigation than that to make any conclusions, but useful to know 15:13:04 oh, and I can't declare Plasma "go" with a good concious. There are still too many discrepancies in the interface between the desktop and the video drivers. 15:13:42 again, what does that mean? 15:14:04 for example, I sat down to this machine this morning after a weekend of no activity. I had to restart sssd to even log in, since it was failing with "error 17". 15:14:21 not bad password, but kcheckpass wasn't talking to sssd_pam 15:15:21 when I finally got logged in, the mouse was unresponsive, and the keyboard was producing artifacts - registering repeat keys while typing at a normal pace. 15:15:46 When I finally rebooted the darned thing after the latest kernel update, kscreen forgot the display configuration again. 15:15:52 that sounds a lot like excess system load 15:16:07 has anyone else who's been using plasma been seeing anything like this? I haven't in tests, but i only run the tests for as hort time 15:16:18 .bug 1217337 15:16:21 danofsatx: Bug 1217337 REGRESSION: kscreen breaks muti-screen management - https://bugzilla.redhat.com/1217337 15:16:54 Sorry guys but i had a crash 15:17:12 there was no load - the only resource usage that wasn't normal was plasmashell had 2.7GB of RAM under it's control 15:17:52 even now, I still can't use the wireless mouse. 15:18:21 well, it sounds like we should have other people trying out plasma if possible. 15:18:44 but it's hard to block releases without specifically identified bugs. 15:18:46 Yes, the problems with Plasma don't show up in a test. It needs long term testing. 15:19:56 There are bugs for the video driver issues, the trouble is that KDE keeps assigning them to kernel and driver devs, which then in turn reassign them back to KDE. Someone needs to step up and fix the problem. 15:20:13 * danofsatx looks for the bugs 15:20:21 danofsatx: could you post the bug numbers to the list or fedora-qa or something? 15:21:45 thanks for noting this 15:22:17 now i think of it, there's another thing to note: the saga of crashes in non-English live installs 15:23:04 which is due to very boring and detailed Technical Stuff, but the QA upshot is, either we're going to have to do a lot of testing of all different parts of the installer to find the crashes, or there's going to be one kinda ugly hack in anaconda soon which should in theory fix all of them 15:23:24 in which case we need to run through at least a few different installs just to make sure it didn't cause anything unexpected 15:23:46 the ugly-hack PR is https://github.com/rhinstaller/anaconda/pull/93 , if you want to track the progress on that 15:24:05 #info danofsatx notes problems with long-term use of Plasma, he will post some related bugs to #fedora-qa or the mailing list 15:24:42 #info A hack to try and fix the various unicode encoding bugs in live anaconda may land sometime soon: https://github.com/rhinstaller/anaconda/pull/93 15:24:55 any other concerns? 15:24:55 * satellit I will leave a plasma f22 0503 install (branched) running for a long time test... 15:25:06 thanks satellit\ 15:25:11 probably helps if you use it 'properly' too 15:25:39 * adamw takes a quick look at test coverage 15:25:40 * satellit it does a daily auto update 15:25:48 we need to test Xen and FCoE - who was it had FCoE hardware? 15:25:54 (i can do xen) 15:26:37 other than that coverage isn't looking too bad 15:26:52 no FCoE here. I might be able to find *someone* that has FCoE. 15:27:09 sorry i only have iSCSi 15:28:53 * adamw checks 21 15:29:08 oh, no-one did it there either. 15:29:25 maybe we have some within the bowels of the beast (red hat) or something, i'll have to see 15:29:36 #action adamw to see if he can scare up some FCoE testing from anywhere inside RH 15:29:45 #info 22 test coverage looks pretty good, only a few missing tests 15:29:55 * satellit I need to know is yumex now automatically switched to yumex-dnf? 15:30:27 satellit: i haven't tried myself, but from what juliux was saying, no. the 'old' yumex is still the default (and still works). 15:30:52 so if I use it in Plasma I have to caches? 15:31:01 to /2 15:31:44 probably, yeah. 15:31:49 ugh 15:31:52 metadata and caching is just kinda ugly in general atm 15:32:03 yum, dnf, and the GNOME Software stuff all use different ones 15:32:10 anyhow 15:32:17 not really meeting stuff, so...let's move along 15:33:15 #topic Council meeting representative 15:33:28 let me find the reference here.. 15:34:07 #info mattdm asked us to send a representative to report on QA to the Fedora Council: https://lists.fedoraproject.org/pipermail/test/2015-April/125966.html 15:34:13 So i don't think we have big problem in this release 15:34:18 on June 8th 15:34:35 he also provided a list of what he'd like us to report: 15:34:39 - the current state of the subproject 15:34:39 - future plans 15:34:39 - things the team needs from the rest of the project 15:34:39 - any blockers we can help unblock 15:34:42 - big resource requests? 15:36:12 so, is anyone interested in doing that? 15:36:20 i can certainly do it if no-one else wants to, but if someone wanted to do it... 15:37:30 I would love to, but I don't think I can commit due to $DAYJOB requirements :( 15:37:34 rgr 15:38:43 welp, guess it's me then :) 15:38:51 #action adamw to report to Council 15:39:11 so i'll send out a thread asking for thoughts on what to report, but does anyone have any ideas now? 15:39:19 especially in terms of 'help from the rest of the project' 15:39:32 Really i don't know 15:39:44 i was thinking particularly in terms of the taskotron area there 15:40:30 I don't have a specific list right at the moment 15:40:40 tflink: kparal: any thoughts? any useful help or input or anything we could get from, say, packagers in terms of the info we're trying to provide them? designers or people experienced with web UIs for the taskotron results stuff? 15:41:30 we do want to unify our web front-ends at some point 15:42:20 * satellit bring back muli-DVD ? 15:42:27 multi* 15:42:46 we publish our qa-devel meeting minutes, but I'm not sure how useful that would be, without rewriting it into a more digestable format for people from outside QA 15:43:09 kparal: yeah, i think that's kinda the idea, to distil everything into a single digestible summary 15:43:28 * adamw waits a cotton-pickin' minute 15:44:15 hmmm, so this idea may need some re-thinking, as i think i'm going to be on a plane on june 8th. :) 15:45:34 well, bug reports about taskotron output/issues always help. but we're painfully aware of some current deficiencies, so it's not like we had no idea what to improve in that area :) 15:46:09 yeah, i was wondering if it's feasible to take actual help in improving it, rather than just reports about what's wrong 15:46:16 e.g. today I saw someone asking questions about upgradepath output on the irc, I plan to improve the messages to be clearer based on that feedback 15:47:16 hmm, that's a tough question. if there's someone interested in doing so, we can certainly walk the person through some "papercuts" issues to get familiar with it 15:47:29 but it's not easy to start working on these things 15:48:08 * kparal links papercuts: https://phab.qadevel.cloud.fedoraproject.org/project/view/12/ 15:48:37 OK 15:49:02 well, i guess we can follow up further on list - either someone will have to volunteer or we can ask the council to move it out a week so i can do it 15:49:24 we've got some initial thoughts now, and some time to work up more. 15:49:28 #topic Open floor 15:49:32 so, any other business, folks? 15:50:03 wait, is this a one-time report to the council? 15:50:19 * danofsatx thought it was a weekly appointment 15:50:23 danofsatx: not weekly, no 15:50:28 danofsatx: they go around all the subprojects 15:50:36 so it'll happen again, but not for a few months 15:51:15 ahh....ok. In that case, let me review my calendar. QA is scheduled for the 8th? 15:52:12 at present - they didn't sound super-tied to that date though 15:52:23 oh, and yeah, you'd only be volunteering to do it this one time, it's not a regular commitment 15:52:57 ok, pencil me in this time around. I'd love to get my foot even further in th door ;) 15:53:19 * danofsatx will take the day off work if he has to ;) 15:54:13 cool, sounds good 15:54:27 #action scratch adamw: danofsatx to report to Council on June 8th 15:54:42 * adamw feels like he thought of something else and then completely forgot about...whatever it was 15:54:49 can't have been that important, i guess! 15:54:54 hmm...when you put it that way, it sounds like I'm in trouble 15:55:16 danofsatx: did I not mention the laser shark pool? 15:55:35 no, I'm fairly certain you skipped over that point 15:55:56 * danofsatx double checks his life insurance policy 15:56:06 what an inexplicable omission on my part! 15:56:15 nope, laser sharks aren't explicitly excluded. I'm good. 15:56:15 alrighty, sounds like we're about done 15:56:26 danofsatx: man, your insurance company's really sleeping on the job. 15:56:36 blocker review in #fedora-blocker-review in 3 minutes, folks 15:56:42 thanks a lot for coming out everyone 15:56:57 * danofsatx notes adamw's clock is fast 15:57:26 close enough 15:58:21 #endmeeting