12:00:14 #startmeeting Mer QA meeting 31/5/2012 12:00:14 Meeting started Thu May 31 12:00:14 2012 UTC. The chair is E-P. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 12:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:00:15 o/ 12:00:55 o/ 12:01:14 welcome 12:01:23 #topic Current status 12:01:28 I can start 12:01:34 hi 12:01:44 o/ 12:01:48 #info first draft of test-execution-planner: http://gitorious.org/~esmietti/test-execution-tools/esmiettis-test-execution-planner 12:01:58 #info QA Tools and tests packaging started 12:02:15 cool 12:02:16 #info https://build.pub.meego.com/project/subprojects?project=home%3Aesmietti 12:02:32 nothing else from me 12:03:04 lbt: have you created the Mer:QA project to obs? 12:03:08 nothing to add from me (still busy with other things) 12:03:55 ok 12:04:25 nothing to add, hoping to have time at some point to do something 12:04:58 the test-execution-planner is kind of p-o-c still 12:05:35 mainly for me to learn yaml structure 12:05:59 iekku: perhaps we could do bug metrics as an item eventually 12:06:20 that would be very good 12:06:21 err, no - sorry, thought I'd done that 12:06:24 good idea 12:07:25 phaeron: welcome, http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-05-31-12.00.log.txt 12:07:54 lbt or phaeron, do you have anything to add to current status? 12:08:22 I've been away for a few days so not much 12:08:47 I will be getting back to OBS/IMG work over the next days 12:08:59 :nod: 12:09:56 not really , been blocked by various things 12:10:14 ok, let's move on then 12:10:14 wish to test the server side of things soo 12:10:16 n 12:10:44 o/ 12:11:19 #topic Image for test automation 12:11:46 I was planning to use nemo virtual image for setting up some automation 12:12:00 we have eat in place, but couple of other things are missing 12:12:40 the first is setting up static ip for the device (eth0 in this case) 12:13:02 and the boot up without user interaction 12:13:28 couldn't we just add a hacky 'ifconfig ... eth0 up' to the ks? 12:13:35 yes, i'm not sure why ifconfig eth0 up doesn't come up in the first plae 12:13:37 place 12:14:08 think it's bizarre connman behaviour 12:14:14 it used to come up 12:14:43 I think that by default connman is in flight mode thus all connections are off 12:15:45 and that can be changed via connman-test scripts? 12:16:04 or is there some easier way to do that? 12:17:18 does this highlight an issue of supporting configuration discretely in an image? 12:17:54 it comes up when making variations of a device with different pre-configured defaults (eg localisation) 12:18:24 in this case we may want an image with a config that has connman defaulting to 'online mode' 12:19:14 STBs would want that too 12:19:42 why does wired connection matter for flight mode 12:19:51 that's a bug imho 12:19:53 don't know, but it does 12:20:51 may be due to old connman version 12:20:58 anyway, that's for sure a QA blocker 12:21:23 for now we could create some start-up script that sets the connman to online and configures IP for eth0 12:21:45 the eat-device package had such a script/service 12:22:00 but usually for usbnet 12:22:31 was it the "usb-networking" script? 12:22:34 we could look at that and see if it can be made configurable, or made to bring up available interfaces 12:22:37 E-P: yes 12:23:05 phaeron: yes, something like that we could do 12:23:25 if you install eat-device you expect the script to do whatever is necessary 12:23:45 to make the device accessible on some know interfaces on known ip 12:24:25 or an user can in the ks file define the interface and ip 12:25:54 anyway the eat-device sounds good place for those scripts 12:26:32 for autoQA at least 12:26:40 the network setup should be done with connman not with ifconfig scripts. As then there is always the risk that connman overrides the settings when some app touches the api. 12:27:24 :nod: 12:27:28 dbus-send-ish maybe 12:27:43 yes 12:27:45 "whatever is needed" includes connman-test and dbus 12:27:50 yep, I have to look the connman-tests, there are examples for that 12:28:10 the usb-networking script we had long time ago used ifconfig to setup things. 12:29:05 so we can change it 12:29:57 how about the boot menu in nemo virtual image, any idea how to set the default timeout? 12:31:05 you may want to boot kernel + (maybe initrd) directly instead of depending on bootloader ? 12:31:24 can't boot directly in virtualbox at least 12:31:26 in kvm maybe 12:31:34 E-P: there's a section in .ks file that adjusts that 12:31:37 bootloader options 12:32:04 depends on if we consider the bootloader part of testing. 12:32:57 phaeron: I was just thinking to change the nemo virtual image to boot up, so I can make semi-automatic testing 12:33:45 Stskeeps: ok, so basically changing the timeout to something else than 0 12:33:49 yeah 12:34:52 I can try that later in the evening 12:36:08 * lbt notes that the test system has a pre-requisite of "automatically boots to a testable state" :) .... sounds obvious but it's worth having in the Mer HA kernel section IMHO 12:36:10 why is it 0 .. 12:36:42 once we have working setup for virtual image, it should be easy to copy to other devices 12:37:21 also many of these problems are Nemo specific - which is fine but also needs to be noted 12:38:17 yes, mainly HA specific stuff 12:39:16 we just need an example how to do that and vendors can modify that to their devices 12:39:51 sorry, need to go now 12:39:57 exactly 12:40:01 seeya 12:40:04 o/ 12:40:04 iekku: thanks, bye 12:40:31 #info connman might be by default in flight mode 12:40:42 #info extending the eat-device package to include scripts for setting up a connection 12:40:48 #info connman should be used for setting the IP 12:41:02 #info connman-tests package has examples for how to setup IP 12:41:09 #info ks file has bootloader option, change the timeout to something else than 0 12:41:46 #info add to Mer HA kernel section that for testing the device should boot to a testable state 12:41:58 anything to add? 12:42:27 need to define testable state 12:43:08 #info define testable state 12:43:09 :) 12:43:35 I will be the next two weeks travelling 12:43:53 i'll be gone next week too 12:44:43 does someone want to organize QA meetings or should we skip them? 12:45:44 perhaps timoph or iekku has time? 12:45:50 always good to sync 12:46:43 i will ask from iekku later 12:46:58 k 12:47:44 alright, we can end the meeting then 12:47:51 thanks for coming 12:47:57 thanks for hosting 12:48:07 #endmeeting