[QA] Release Meeting 2012-04-06

Fri Apr 6 09:54:49 UTC 2012

== Precise Testing ==

* Precise automated installation testing
   * Desktop: PASS all week
   * Alternate: PASS all week
   * Server: PASS all week

* Precise automated upgrade testing:
  * NO RED BALL \o/
  * Oneiric Upgrade Server and Desktop are GREEN
  * Everything else is YELLOW (system upgraded successfully but 
post-upgrade test failed)

This is the 1rst time that all upgrade tests pass. Congrats everyone!

* Lucid Desktop
  * gvfs crash during upgrade
  * obsolete config files left after upgrade (with latest version of the 
test)

* Lucid Main
  * gnome-settings-daemon crash during upgrade
  * cron crash durin upgrade
  * lwregd crash during upgrade (likewise-open)
  * drbd8-source failed to build with kernel 3.2 (which is expected 
since drbd8-source is not available in Precise but package should 
probably be uninstalled on upgrade)
  * prompt to update unmodified config file eap.conf (freeradius)
  * prompt to update unmodified config file mailman.conf (mailman)
  * More obsolete config files:

https://jenkins.qa.ubuntu.com/job/precise-upgrade-lucid-main/ARCH=amd64,LTS=lts,PROFILE=main-all,label=upgrade-test/78/artifact/lts-main-all-amd64/obsolete_conffiles.log

* Lucid Server
  * 1 obsolete config file
  [Bug 955824] Re: lucid upgrade leaves obsolete file: 
/etc/apt/apt.conf.d/01ubuntu

* Lucid Universe
  * colord crash during upgrade
  * pcscd crash during upgrade
  * Prompt to update unmodified config file: /etc/lyricue/access.conf
  * Prompt to update unmodified config file: /etc/mediatomb/config.xml
  * More obsolete config files:

http://jenkins.qa.ubuntu.com/job/precise-upgrade-lucid-universe/lastSuccessfulBuild/ARCH=amd64,LTS=lts,PROFILE=universe,label=upgrade-test/artifact/lts-universe-amd64/obsolete_conffiles.log
  * python module failed to import: ccm

* Oneiric Main
  * cron crash during upgrade
  * prompt to update unmodified config file mailman.conf (mailman)
  * X failed to start after upgrade (most probably a false positive, it 
takes time to start X on main and universe due to the number of services 
started on boot, the QA team will check)

* Oneiric Universe
  * Prompt to update unmodified config file: /etc/lyricue/access.conf
  * Prompt to update unmodified config file: /etc/codeaster/asrun 
(package: code-aster-run)
  * The following python modules failed to import after upgrade:
     bicyclerepair: /usr/share/pyshared/bikeemacs.py
     gnome-dvb-client: /usr/lib/python2.7/dist-packages/gnomedvb
     jobs-admin: /usr/lib/python2.7/dist-packages/JobsAdmin
     libhocr-python: /usr/share/pyshared/hocr.py
     python-edje: /usr/lib/python2.7/dist-packages/edje
     python-evas: /usr/lib/python2.7/dist-packages/evas
     python-keybinder: /usr/lib/python2.7/dist-packages/keybinder
     python-mdp: /usr/lib/python2.7/dist-packages/bimdp
     python-mdp: /usr/lib/python2.7/dist-packages/mdp
     python-visual: /usr/lib/python2.7/dist-packages/cvisualmodule.so.3.0.0
     tryton-client: /usr/lib/python2.7/dist-packages/tryton

Bug reporting in progress...

=== Boot speed Testing ===
http://reports.qa.ubuntu.com/reports/boot-speed/

1 run yesterday on AMD64 took 12 seconds more than the average to boot
http://reports.qa.ubuntu.com/reports/boot-speed/acer-veriton-01/2012-04-05_14-14-20/bootchart.png

The same occurred on i386 on Mar. 31 (54.66s) and Apr. 01 (49.83s)
http://reports.qa.ubuntu.com/reports/boot-speed/acer-veriton-01/2012-03-31_11-57-21/bootchart.png
http://reports.qa.ubuntu.com/reports/boot-speed/acer-veriton-02/2012-03-31_14-25-29/bootchart.png
http://reports.qa.ubuntu.com/reports/boot-speed/acer-veriton-01/2012-04-01_19-37-05/bootchart.png
http://reports.qa.ubuntu.com/reports/boot-speed/acer-veriton-02/2012-04-01_15-13-56/bootchart.png

== What was done engineering wise? ==
First version of "Auto Package Test" in production
It was a deliverable of UDS-P Blueprint 
https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upload-intermediary

* The tool checks changes in the archive
* If a dependency of a package with a dep8 [1] control file changed (new 
dependency or new version of an existing dependency) or the package 
itself changed (new version of the source package) the test is triggered.
* The test itself starts a clean VM and uses autopkgtest to run the 
tests. The tests supplied in the source package and described in the 
control file are run on the package as installed on the testbed system.

Results:
https://jenkins.qa.ubuntu.com/view/Precise%20AutoPkgTest/

Documentation:
https://wiki.ubuntu.com/QATeam/AutomatedTesting/AutoPackageTesting

Packages currently tested:
* apport
* jockey
* postgresql-common
* ubiquity
* udisks
* upower

The list is static at the moment. If you want to add a package to this 
list, then add a dep8 control file to your source package and ping me.

[1] http://dep.debian.net/deps/dep8/

== What's about to land that might impact the other teams? ==
None.

=== Release Notes ===
None.

== Summary of bugs working on by team ==
  * http://reports.qa.ubuntu.com/reports/qa/qa-open-bugs.html
  * http://iso.qa.ubuntu.com/qatracker/reports/defects/opened
There are lot of untouched from Precise ISO testing (Latest Beta and 
previous milestone) Please review this list.

== Dependencies on other teams, blocking items ==
None.

== Issues? ==
None.

== Blueprints and Status ==
  * Work Item Status for Precise: 
http://status.ubuntu.com/ubuntu-precise/canonical-platform-qa.html

-- 
Jean-Baptiste
irc: jibel