Testing summary - Auckland New Zealand, 4 September 2010<br><br>Who: Fabiana, Nevyn, Tom, Tabitha, Abhishek, Dave, Robin<br><br>We did one test with Dextrose os373pyg:<br>Tested journal send to ... in Dextrose os373pyg on XO-1.0s and XO-1.5s -- it didn't work <a href="http://bugs.sugarlabs.org/ticket/2281" target="_blank">http://bugs.sugarlabs.org/ticket/2281</a><br>
<br>Then we switched to 10.1.2 os852 on XO-1.0s and XO-1.5s<br><br>In the Speak-18 "ABC" menu, you can choose a variety of languages, but only 'spanish' and 'english' are available in the 'answer a question' mode. If you choose "English" or "Spanish", the robot works as expected. If you choose any other language in the 'ABC' mode and then go to have the robot answer questions, the robot says it cannot speak that language and defaults to english, however it speaks english with the accent of the language that was selected on 'ABC'. For example, chose "Spanish latin america" from the abc menu, switch to Robot and it says it can't speak Spanish latin america so let's speak English instead, however it speaks english with a spanish accent.<br>
<br>Tried collaborative Write on access point networking, no jabber server with Write-63 between 3 XOs, worked for a short time then collapsed. Took screenshots of divergent documents. We didn't see any errors or warnings in the UI that collaboration had stopped. Tried again with 5 XOs and a different initiator. Results were very inconsistent, some laptops could see all participants in the frame, some could not. Some laptops saw most of the writing, some saw none of it. Many arguments resulted about what might have been the cause, but I suspect that we are seeing patterns where they don't exist. One theory is that the XO-1.0s break everything.<br>
<br>Collaboration problems seem to be a theme. Does anyone want us to file a bug with logs and screenshots?<br>
<br>Tried collaborative record, with inconsistent results and no consensus on why it wasn't working properly.<br><br>Tried a virtualbox sugar on a stick using bridged networking and no collaboration server thing. This sort-of worked. On the virtualbox machine, I can see other XO's, but they cannot see me. Virtualbox joined a collaborative write, but didn't see any updates from other XO participants and they didn't see mine. The virtualbox worked in other respects.<br>
<br>This virtualbox was created with the appliance from <a href="http://wiki.sugarlabs.org/go/Talk:VirtualBox#Virtualbox_Appliance_of_SoaS_Mirabelle" target="_blank">http://wiki.sugarlabs.org/go/Talk:VirtualBox#Virtualbox_Appliance_of_SoaS_Mirabelle</a> and a bunch of painful steps. I couldn't work out how to become root, so I broke in with system rescue cd. I adjusted gdm to auto login and I had great trouble installing the virtualbox guest additions, it turns out you need to install the updated kernel, as yum will happily install it's headers without installing the kernel itself (wtf??). The virtualbox guest build script doesn't tell you why it fails, so it took a bit of sluething to see the version msismatch and realise I had to upgrade the new kernel. I didn't do the full yum upgrade because I was borrowing someone's internet and the upgrade was large.<br>
<br>Write on one of the XO-1.0 went into an infinite loop (100% cpu usage and no updates to the display), <a href="http://bugs.sugarlabs.org/ticket/2284">http://bugs.sugarlabs.org/ticket/2284</a> how do we diagnose this? If it was java I would use jstack, but it isn't so I'm a little stuck. I tried strace and there wasn't much interesting. I tried gdb, but the native stack trace isn't all that comprehensible. I caught a core file and attached it to the ticket.<br>
<br>Memorize on XO-1.0 - fine<br>Browse on XO-1.0 - fine<br>Maze on XO-1.0 - when rotates on XO-1.0 does not resize so on 90 degree or 270 degree angle you cannot see the whole Maze.<br>Implode on XO-1.0 - froze while playing but eventually came back (while trying to reset touchpad). <br>
Moon on XO-1.0 - fine, wish it could do more stuff<br>Record on XO-1.0 - picture, video and audio fine but mic pick up was low (maybe the XO settings), there is a resolution option but you can't change it<br>
<br><br>