Test group release notes/2009 and earlier

From OLPC
Jump to navigation Jump to search

NOTE: Entering issues on this page does not count as reporting them.

Purpose of Test Group Release Notes
If you are thinking of loading a new image; come to this page first and see if the build you are going to load has any major problems. If it can't even pass the Smoke Test, you probably don't want to use it.

If you don't see anything here on the latest release, please add your notes on smoke test and/or basic functionality to help the next guy.
- Kim

Use Trac to file bugs.

Regression/Smoke Test

General smoke and regression tests:

Full-build smoke test

This set of test cases represents a quick smoke test that the build should pass. See the smoke tests for a particular release for more details.

  1. Boot into sugar
  2. Check the OS, OFW, kernel from developer's console
  3. Check wireless firmware version: from virtual terminal type ethtool -i eth0.
  4. Connect to a local mesh and see other XOs (this needs to be in a location with no school server or infrastructure AP)
  5. Run 3 collaborative activities concurrently (AbiWord, Connect4, or Chat) with 2 other XOs
  6. Run Browse and ensure that library navigation sidebar and index page loads; successfully browse the internet.
  7. Ensure that the journal loads properly at start and is able to resume an activity.
  8. Connect to an AP (and/or school mesh) and browse the web

Smoke tests for particular releases

List of SmokeTest test cases

The following queries for smoke tests in the wiki. Some tests are out-of-date, despite claiming "Any" {{#ask: Test category::SmokeTest 

 | ?Short name
 | ?Test objective
 | ?Build stream=For builds
 | default=No articles found in Category:Test cases with Property:Test category of SmokeTest?!

}}

Build release notes

Please add build release notes below and provide info as to whether the build passed the smoke test.

Build 573

Changelog 573

Smoke Test

  • Boots into sugar successfully
  • Sees other XO's on the same mesh network (meshes are numbered)
  • Shared activity works over mesh network
  • Browse works over mesh network
  • Journal resumes activities
  • Connects to AP
  • Can browse over AP

Noted Differences

  • In mesh view, XOs are gathered around shared activities they are using

Build 572

Changelog 572

Smoke Test

  • Boots into sugar successfully
  • Sees other XO's on Mesh network
  • Browse works on the Mesh network
  • Collaborative activity works over mesh network
  • Journal works

Noted differences:

  • Mesh networks are numbered

Build 571

  • Journal not open.

Build 570

Changelog 570

Smoke Test

  • Boots into sugar
  • Browse on mesh network - works fine
  • Journal resumes activities
  • Interactive activity (chat) worked over mesh network
  • Browse using AP - works fine


- Alex

Build 568

Changelog 568


Smoke Test

  • Boots into sugar
  • Mesh view - can see others
  • Browse on Mesh network works (still no sidebar)
  • Interactive Activity worked
  • Journal - successfully resumed an activity
  • AP - connected and browsed the web

- Alex

Build 567

Changelog 567


---On a B2-1, q2c25

  • Writes image successfully
  • Boot & Activated Sugar
  • Camera - don't work, I expected this to work on a B2-1
  • Browser - cannot browse, very slow
  • Mesh view - can see others - good
  • ctrl+alt+f2 still showing debug info - good for development

--- wenmi

Build 566

Changelog 566


  • Browser and Write are broken. Don't waste time on this build. (-Tomeu)

I was wrong, looks like a good build to test. (-Tomeu)

Build 564

ChangeLog 564

Many bugs with this build. It doesn't pass basic regression.

- Kim


--- On a B2-1, q2c25, Build564

  • Journal shows activities
  • Cannot continue activity very well
  • slow
  • camera shows no frame at all, not even an image can be loaded
  • shows other xo on network view - good
  • ctrl+alt+f2 shows debug messages - good
  • resume - good
  • browser can't load at all
  • tooltip text on icon fading is very slow

~User:Wenmi01 ---

Build 561

Don't use this build... too many serious regressions.

on B4 and C

C.Y.

  • The same errors happen to me in a B4 RafaelOrtiz 17:00, 30 August 2007 (EDT)

- Kim

Build 557

Changelog 557

on a B4

Smoke Test Results

  1. Boots into sugar; can see other XOs on school server mesh, can get to internet.but the mesh and battery icon aren't correct#3001. The battery icon is white, and the mesh icon remains gray even with a good network connection.
  2. Camera works

on a B2-1

  • Camera runs
  • Journal entries are restored from backup
  • It can resume the activity
  • Quite slow on resuming activity
  • Activity don't run most of the time
  • The activity donut also changes the space for activity icon irregularly
  • Browse activity hangs and disappear in the donut.
  • Pdf reader is not included here
  • RandR is working (Rotate Screen)
  • Cannot suspend, slow on suspend.
  • The mesh is still seeing other developers but it is nice to see that the mesh function well
  • Cannot use the console on ctrl+alt+f2 (this is good for seeing messages about Sugar)
  • Activity closes suddenly

by wenmi / Rowen OLPCPH

ChangeLog

Build 556

ChangeLog 556

  • On a B2-1
 - very slow and cannot load almost even an activity
 - memory pressure is very noticeable
 - camera is still broken, 1 frame appeared and never refreshed 
 - still I can't see the ctrl+alt+f2 console
               - wenmi OLPCPH

Smoke results - overall pretty good. Compared to 542 (current shipping build), this one scans only channels 1, 6, and 11, which means you get more reliable connectivity for collaboration in an RF noisy environment:

  1. Boots into sugar; can see other XOs on school server mesh, can get to internet but the mesh and battery icon aren't correct#3001. The battery icon is white, and the mesh icon remains grey even with a good network connection.
  2. I opened and shared an AbiWord doc. Sharing worked pretty well, a little bit of trouble adding images into docs. Two new bugs were filed: Can't use CTL-C, CTL-V to copy and paste an image#3002, and some .jpg images dragged successfully onto the clipboard and some do not#3003.
  3. I tried to share a url through browser sharing#3004 and the other XOs that see a Browse icon get a new browser window, not the one that I was trying to share. It IS possible to share a url by opening a chat window and using cut&paste to put the link in the chat window.
  4. The browse activity did NOT provide the sidebar links to the library; only a google search window.
  5. I was able to resume activities from the journal; but I don't see the activity I was most recently working on unless I search for the activity type (like 'write').

NOTES:

  • Camera is still broken; only get one frame at start up and nothing else.
  • Paint#3007 requires that you choose colors by using the eyedropper; and when you paint with a brush or use the paint fill feature, the next mouse click makes the last item disappear.
  • Paint doesn't share#3007
  • There are some activities that are not opening probably related to memory problems.

Build 553

On a B2-1

- Luya Tshimbalanga

On a B4: Activities: The following activities do not start (doesn't seem to be low memory, but the problem is undiagnosed):

  • Tamtam
  • Paint
  • Connect
  • Calculate

The following activities start but do not function:

  • Record (camera)
  • Browser (IP connectivity, yet all pages time out)

Other points:

  • Presence service seems to work
  • Frame can sometimes disappear and be hard to get back
  • Journal seems to have a fairly large memory leak

Hello1024 06:08, 23 August 2007 (EDT)

Build 551

On a B2-1

  • Camera stops
  • Activities are very slow
  • 2nd console ctrl+alt+f2 - no console (only error messages)

-Rowen/wenmi OLPCPH

- Zack

Build 547

On a B2-1

  • Camera stops
  • Browse starts (starting..) but never opened
  • 2nd console (Ctrl+alt+f2) - Xwindow error

-wenmi / Rowen OLPCPH

  • Can't open Paint activity.

Build 545

On a B2-1

  • GX fix worked on camera
  • OS Image loaded successfuly
  • Very slow due to little memory, we need to enhance memory usage.
  • Tamtam Mini has no sound
  • Able to resume activity on Journal.

-wenmi OLPCPH

Build 542, Trial-2 Release

Smoke Test (Some issues with connecting to an AP):

  1. Sugar boots up
  2. Connected properly to mesh, saw others via link local
  3. Shared Abiword, chat, camera successfully
  4. Journal was able to resume from an abiword doc successfully
  5. I'm currently having trouble connecting to an external AP from within 1CC. This worked at home.
  6. Need to test item 6 in a different environment.

Other Notes:

  • I had to remove the battery and power adapter for a few seconds after upgrading in order to boot up properly.
  • To boot with backup edit the olpc.fth file to change 'false' to 'true' in line 11. This will save the activation key as well as user data (including the nickname and color of the XO). If you have never upgraded to code base with activation keys, you will need a different process. (I will try this soon)
  • It is not very difficult to 'hang' the mesh and require a reboot to start again. Not sure of exact steps to repeat -- Walter saw it; I've seen it.


Some Notes for the formal Software Release Notes:

  • If you are running Tamtam or another activity that uses the speakers, close the activity before suspending the laptop. You can suspend the laptop by closing the lid or pushing the suspend/resume button. If Tamtam or another sound activity is still running, when the laptop resumes from suspend, it will squeal very loudly. To recover, shut down the laptop by holding the suspend button for >5 seconds or remove the battery and adapter for a few seconds.
  • Now that we have made the power button suspend; to shutdown completely, hover over the XO in the home view and click on 'Shutdown'.
  • To turn on various activity logs:
  1. edit ~/.xinitrc and uncomment the line that imports .sugar.debug
  2. in ~/.sugar.debug, add lines like export JOURNAL_DEBUG=yes
  • Backup to School Server: To register with a school server and backup data (for build 542):
  1. Open a developer's console
  2. View the config file to see that you are not registered with any school server; and to get your Serial Number (SN)
  3. SSH into the school server (for 1CC this is schoolserver.laptop.org); type 'yes' to accept keys
  4. Type 'olpc-register' to register with the server
  5. Reboot for this config file to take affect.
  6. From the Journal, click on the 'Backup' tab, and then the 'Backup' icon.


Old Release Notes

Old Release Notes

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Test_group_release_notes/2009_and_earlier&oldid=64282"