18:05:39 #startmeeting 18:05:39 Meeting started Mon Feb 11 18:05:39 2013 UTC. The chair is Holgi. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:05:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:05:46 * wstephenson was pushed ;) 18:06:08 Whatever it takes!! 18:06:09 #topic 12.3 RC1 testing 18:06:31 I installed RC1 on my test machine and the work station 18:06:51 problem I had was that netwaork installation was not working for me# 18:07:03 and I was not able to compile the nvidia drivers 18:07:48 I wanted to double check if the network installation is the same as in SLES 11 SP3 where NFS installation is not working 18:07:57 but did not havae the time for it so far 18:08:12 any other RC1 reports ? 18:08:14 Was that due to the lack of network, or the nvidia not building under kernel 3.7? 18:08:32 network issue was different from nvidia 18:08:47 system hangs when fetching DHCP information# 18:08:50 Holgi: i spent 2 days last week testing RC1, mainly install and upgrade 18:09:14 Holgi: background is, Agustin asked me to do QA on 12.3 until release 18:09:21 bille: did you install with install=nfs://xx.xx.xx.xx/... ? 18:09:40 the aim is to avoid reproducible failure like the Apper situation in 12.2 18:10:03 Holgi: nope, i was using usb media 18:10:04 bille: glad to hear - welcome to the testing team! :-) 18:10:24 so i tested 12.1 and 12.2 upgrade, vanilla, +KDE 4.9 18:10:31 straight install 18:10:33 NET install 18:10:40 Live CD boot and install, kde and gnome 18:10:57 then a few hardware things that openQA can't test 18:11:17 wifi, fingerprint, webcam, tablet, bluetooth, sound 18:11:24 ok, sounds you were quite busy then 18:11:40 are there any issues you found that are worth to be reported here? 18:11:42 well, when you have the whole work day to throw at it 18:11:53 netconfig is totally hosed 18:11:59 as you mentioned, dhcp hangs 18:12:06 resolv.conf not getting written 18:12:11 default route not set 18:12:27 ntp hanging during boot, on an upgraded system 18:12:48 bille: is there a fix in place already for the netconfig stuff? 18:14:06 no :( 18:14:12 too bad 18:14:14 it's all in the most annoying bugs page i set up 18:14:23 yes, I saw this 18:14:29 Me too. 18:14:33 hopefully werner and reinhard will be joining us as of today to fix stuff 18:15:01 other things, virtualbox needs an upgrade to boot rc1 18:15:23 and there are still too many apper bugs around EULA and ordering of notifications during updates 18:15:30 What VB? I did not see that. 18:15:42 12.2 VB 18:15:47 ok, any plans to have a 2nd RC then if we have so much issues in RC1? 18:16:25 or what ever we call it (if not RC)?! 18:16:29 Holgi: 28 Feb 18:16:37 I'm running VB 4.2.6 downloaded from Oracle - seems OK. 18:17:03 also kde crashes on login if a given applet is added - that's a stinker 18:17:05 anyway 18:17:21 i wanted to ask you guys professional opinion how to setup a QA plan 18:17:28 apart from random self-interested testing 18:17:57 i asked SUSE for official help, but enterprise stuff has the team fully loaded 18:18:03 so i'm asking on the down low. 18:18:42 bille: my problem is SP3 :-/ 18:18:54 As I try to carry on local work during release testing, I concentrate on the self-interest. 18:19:00 that's the boyo ;) 18:19:41 here's my sketch: 18:19:58 is your focus on tests or exit criteria? 18:20:03 http://paste.opensuse.org/48354601 18:20:32 Holgi: i am not well informed about formal testing methods 18:20:57 my aim is to reduce the number of critical defects that escape to GM 18:21:08 whatever you'd call that ;) 18:21:30 so how does this team do it? 18:21:35 Do you read the Beta forum? 18:21:45 ok, if it is about man-power: I would suggest to ask for help of trainees 18:21:51 i've been reading the 12.3 comments forum, same thing? 18:22:03 LWFinger: ? https://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/483056-12-3rc1-comment-thread-3.html 18:22:24 Yes, that is the one. 18:22:26 trainees = Azubis 18:22:40 Holgi: also about a test plan to use whatever resources i can find in house and in the community effectively 18:23:11 so far i've just been asking opensuse team members with different hardware (intel, nvidia, amd, uefi, etc) to test things out 18:23:16 in past time we focused on: installation & update testing 18:23:21 feature testing 18:23:32 running our automated test suites 18:23:35 Holgi: more structured version of that paste that only you can read: https://wiki.innerweb.novell.com/index.php/OpenSUSE_123_QA_Plan 18:23:48 same info, just with bullets. 18:24:31 if we had more time/resources we had a bunch of manual test cases, but I guess most of theme are outdated today 18:24:47 if you have the list, i can probably update them to their equivalents 18:25:33 I do relatively complete wifi testing. If you have any other specific tasks you want tested, let me know. 18:25:34 I need to look in testopia, can you send me a reminder via e-mail please, I will check tomorrow 18:26:32 Want my experiences? 18:26:43 LWFinger: great. i am not sure i have time to get my wrt54g up and running again 18:26:56 LWFinger: briefly - i guess real problems are reported? 18:28:15 I ran into th rtkit bug with a zypper dup from 12.3 Beta1. Aborted upgrade and recovered Bug 80525 18:28:45 missing digit? 18:29:01 Grub2 install missed a Fedora 17 installation - known problem, not sure of bug # 18:29:17 802525. 18:29:38 LWFinger: multiple boots another area worth investigating 18:29:58 i got a second drive for my laptop and grub2's detection of other systems is patchy 18:30:08 esp on firstboot. not sure if there is a special mode there 18:30:43 Machine 2: uninstalled rtkit and upgrade from 12.3 beta1 to rc1 was OK. No non-openSUSE systems there, grub2 OK. 18:31:26 we also tested windows shrink and dualboot, no problems there 18:31:33 I use special /etc/resolv.conf as my ISP has lousy servers. That was overwritten. 18:31:50 hmph. most of the time nothing gets overwritten, even when supposed to :( 18:32:00 The new one was also wrong. 18:32:24 we have a real dark zone around anything bigger than a laptop though 18:32:36 Perhaps due to bug #800365. 18:32:55 What dark zone? 18:33:02 LWFinger: lack of test coverage. 18:33:16 we should for sure have an eye on the network stuff - that part really need to work in GM 18:33:25 LWFinger: i'm not testing on servers, raid or lvm yet 18:33:33 and only did basic crypted fs testing 18:33:43 otherwise we will get a lot of bad credits and people might not be able to install updates as well 18:33:55 it's cynical, but i'm testing on the kind of hardware reviewers will use :P 18:34:22 Holgi: yeah, nothing is shipping with this netconfig problem as it stands 18:34:31 Yes, GM has to work for noobs. 18:35:13 i've also found a few visual bugs around the new kde theme and colour palettes 18:35:30 since i expect ppl to try us out due to those 18:36:01 Holgi: any specialised strategies to split testing among team members? 18:36:21 assuming a set of equally motivated and flexible volunteers... 18:36:21 KDE 4.10 corrected the worst theme problem 18:36:21 what team members? the three of us? 18:36:33 the checkbox in networkmanager 18:36:46 well, say i get 10 half days from other opensuse team members between now and RC2 18:36:55 poorboywilly: bug#? 18:37:04 networkmanager is full of checkboxes. 18:37:16 the plasmoid checkboxes 18:37:27 if we are able to come up with a test plan, then everybody can just "select" his tests 18:38:34 poorboywilly: not reflecting actual NM state/hardware state? 18:38:41 The closest thing I have to a server is off limits for testing. I'm limited to laptop mode. 18:38:53 poorboywilly: or were they not themed properly? 18:39:24 wstephenson: the "enable networking" and "enable wifi" checkboxes, there was a bug of some sort in plasma where it wasn't using the proper theme colors 18:39:44 now it is using the plasma theme colors 18:39:52 they always showed correct state, it was just almost impossible to read 18:39:52 poorboywilly: ah ok. the problems i am finding are black text on dark dark grey backgrounds 18:40:28 wstephenson: can you say what areas off the top of your head? I've been digging around a lot in plasma for a few of these theme problems 18:40:41 poorboywilly: not just plasma but apps 18:40:59 if they don't use KColorScheme, but QPalette directly, they don't theme properly 18:41:10 poorboywilly: do you know CheckColorRoles? 18:41:55 http://kde-look.org/content/show.php?action=content&content=90034 18:42:13 wstephenson: I do not, but I am looking at it now 18:43:11 it makes your desktop look like a cocktail party in 1978, but it works. 18:43:36 What do you do with that file? 18:43:46 LWFinger: import it in kde's colour config module 18:44:12 LWFinger: then screenshot any cases where text and background do not match 18:44:20 eg lightgreen/darkgreen, 18:44:28 blue, yellow, purple etc 18:44:36 sorry, that's not very clear 18:44:47 dark green text on light green background is correct 18:45:07 dark purple on yellow signals a programming error 18:45:13 (for example) 18:45:25 think of it as being like dentist's disclosing mouthwash. 18:45:30 or if there is white or black text, then something is hard-coded? 18:46:04 poorboywilly: yup 18:47:37 any feedback on the partial plan i posted? 18:47:57 i need to move on to reading bedtime stories shortly. 18:48:01 you mean: https://wiki.innerweb.novell.com/index.php/OpenSUSE_123_QA_Plan ? 18:48:07 wstephenson: is it that paste with 29 things? 18:48:13 yes and yes 18:48:41 it's a long list and not everything is clear to me 18:49:06 maybe we should spend some time tomorrow face2face 18:49:41 Holgi: whenever you like :) 18:50:00 after yoga 18:50:17 that's until 1300? 18:50:25 i know i should have registered for that course 18:50:27 ~13:30 18:52:12 no. 17 is hilarious is about all the feedback I can present :) 18:52:56 bille: is topic 1.1 already covered or should I call it now? 18:54:13 Holgicalled 18:54:18 Holgi: call it 18:54:31 #topic Presenting myself as an extra testing resource (Will Stephenson) 18:54:56 ok bille, go ahead 18:55:16 Holgi: ah, i thought was already in that topic 18:55:19 ok, for the records: 18:55:34 opensuse team wants 12.3 to be A Good Release 18:55:54 7.2, 11.3, 9.1, whatever your cherished past release was. 18:56:12 so i'll be doing QA on it full time until it's released 18:56:37 i'm a developer not a professional QA, but i'll do my best 18:56:56 as I said before: that's good news 18:57:07 next topic 18:57:13 hear hear 18:57:20 #topic Next Meeting 18:57:25 (to the good news part) 18:57:37 according to the schedule, RC2 is on Feb, 28th 18:57:59 so have the next meeting on Mar 4th? 18:58:35 any opinions? 18:58:57 sounds reasonable 18:59:01 any objections? 18:59:05 if you're not having more frequent meetings during the release laready, would that be a possibility? 18:59:13 to keep the tempo up? 18:59:36 I'm open if there is anything to discuss 18:59:38 that's dependent on drumming up more testers, or we'll all be exhausted 18:59:45 I got some new updates today. Will they be continuing? 19:00:01 problem in times like this is the long time without a new build 19:00:14 so is the usual format of testing meetings to present problems as we have been doing today? 19:00:56 there is not usual meeting, meetings are happening like participants contribute 19:01:09 ok 19:01:27 you are a member now and can "steer" the meeting 19:01:52 atm i'm an enthusiastic amateur with a lot of time 19:02:04 If we met in 1 week, what would that accomplish? 19:02:08 i'd like to learn from your experience 19:02:17 nobody had to prove that he is a real QA guy here 19:02:35 not sure, that's why i'm asking how things usually work around here 19:02:41 LWFinger: one thing it might do 19:03:00 my guess is: members are open if it makes sense 19:03:02 is if i get a bunch more enthusiastic amateurs, is to point them at the test plan, answer any worries, get them on the right track. 19:03:09 if you can convince us to meet earlier 19:03:12 no problem 19:03:15 ok 19:03:21 yes I don't recall ever claiming I'm providing any useful service here personally :) 19:03:32 you're just here for the tea and biscuits? ;) 19:03:48 Virtual, at that. 19:04:16 ok. then i'm going to dash and put my kids to bed now 19:04:19 will check in later. 19:04:36 good luck! 19:05:29 #agreed next meeting 2013-03-04 19:05:36 OK 19:05:51 #topic open discussion 19:05:56 so we are done with the regular topics 19:05:59 anything more? 19:06:09 Meeting at 18:00 UTC 19:06:32 larry: yes, as usual 19:06:52 anything more? 19:07:19 ok, then let's call it a day 19:07:27 OK. 19:07:43 #endmeeting