20090622

The Ubuntu Testing day is a special day where the Ubuntu Community comes together with a shared goal of testing a specific set of ISO images (Alpha, Beta, RC, Gold or Point releases), a specific feature or some bugs needing verification. Taking the idea from the UbuntuBugDay, we want to apply the same concepts to ISO testing.

Join the Testing Day

Who can join the Testing Day? Everyone. You don't need to be a developer. You don't need to know how to code. Everyone is welcome. If you don't know how to help, then just stop on by and we'll explain everything to you. In fact, one of the objectives of the Testing Day is to help people willing to start testing Ubuntu to make it better.

Where to join the Testing Day? Come to #ubuntu-testing on freenode IRC. Normal testing activity takes place in #ubuntu-testing at other times also.

What is the focus for this testing day?

With the upcoming release of the 8.04.3 point release, this testing day will focus on verifying proposed Stable Release Updates (SRUs) for hardy.

The process for verifying an SRU is straightforward:

  1. Set up an appropriate test environment (with VirtualBox or KVM if necessary)

  2. Reproduce the bug
  3. Enable the -proposed repository

  4. Install the proposed version of the package
  5. Verify that the bug is solved in the -proposed package.
  6. Look for regressions introduced by the proposed update
  7. Put your name in the last column. This will let people know that the bug in that row has been tested.
  8. If the bug is still present in the -proposed package:
    • Set the bug report Status: In Progress.
    • Describe why the fix was rejected in a comment to the bug report.
    • Modify the verification-needed tag to a verification-failed tag on the bug report.
    • Set the row's background to red by adding red in the first cell of the column after rowbgcolor=.
  9. If the fix was good and the bug is no longer in the -proposed package:
    • Modify the verification-needed tag to a verification-done tag on the bug report.
    • Describe the general steps taken to verify the package, any special difficulties, and the recommended upload date.
    • Set the row's background to green by adding lightgreen in the first cell of the column after rowbgcolor=.

If you do find any new regressions, please file bugs in launchpad and tag them with regression-proposed as well as mentioning them in your follow-up comment on the original bug report.

See PerformingSRUVerification for more details on the SRU verification steps.

List of bugs

Bug

Subject

Package

-proposed

Tester

306293

Mod_ssl randomly causes apache threads to use 100% of CPU

apache2

225735

Releases files does not contain "LTS" tag

base-files

219192

[hardy] livecd: keyword "persistent" results in busybox and (initramfs)

casper

305264

gnutls regression: failure in certificate chain validation

gnutls13

292604

Internal error in memory allocation

gnutls13

216104

Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons

gvfs

209483

2.6.24 reports invalid storage size in /sys [Sony Walkman NWZ-S618F doesn't mount in Hardy]

hal

337276

/var/log/installer/initial-status.gz is empty on server installs

installation-report

359447

kvm segfaults

kvm

212485

kernel bug rpc nfs client

linux

213988

control key "stuck" after resume on Dell 1420n

linux

227501

id of apple aluminum wireless keyboard changed??

linux

247889

SiS 190/191 on ASUS P5SD2-VM dont detect link status / dont send traffic

linux

253004

Oops in sunrpc:rpc_shutdown_client

linux

292619

Kernel panic on boot if SMP (ASUS M3A-H/HDMI)

linux

295091

kernel crashes at boot on a dell inspiron 531.

linux

330885

ALPS touchpad not recognized in Dell Latitude E6400 - reopened ?

linux

355057

Non-ASCII characters get corrupted in framebuffer console

linux

372425

[Broadcom] Upgrade 'wl' to latest version: 5.10.91.9

linux-restricted-modules-2.6.24

292450

Broadcom STA/wl driver causes random kernel panics

linux-restricted-modules

324275

Kernel 2.6.24-23-rt locks up hard under heavy rt load

linux-rt

370066

LSB 4.0 support

lsb

214860

I see a Spelling Mistake when shutting down/restarting

network-manager

361602

network manager 0.6 should use 9 or 8 seconds as a scan timeout to workaround driver bugs

network-manager

227848

boot order wrong for iscsi

open-iscsi

222126

Partition Table is cleared during install on Intel Macs

parted

336992

UUIDs of existing swap partitions are changed

partman-basicfilesystems

290399

After ran the command fence_tool dump, the fenced process will take 100% CPU usage

redhat-cluster

328874

getent group crashes winbindd on domain controller

samba

128554

[apport] ubiquity crashed with UnicodeEncodeError in partman_edit_dialog()

ubiquity

247993

Criação de partição de swap

ubiquity

218195

[SRU] sources.list is missing security-lines

ubuntu-vm-builder

221231

[SRU] ubuntu-vm-builder should set up a locale, timezone, etc

ubuntu-vm-builder

228268

[SRU] "--templates" option mis-handled when using kvm or qemu

ubuntu-vm-builder

228744

[SRU] Fails to generate valid image if /tmp is mounted nosuid,nodev & -t is not specified

ubuntu-vm-builder

230299

[SRU] IPv6 not enabled in host file

ubuntu-vm-builder

230312

[SRU] "letters" variable not initialized properly

ubuntu-vm-builder

230319

[SRU] -v / --verbose options are not parsed correctly

ubuntu-vm-builder

230323

[SRU] ARCH is not computed properly

ubuntu-vm-builder

230334

[SRU] ubuntu-vm-builder does not use ubuntu-keyring in debootstrap

ubuntu-vm-builder

232361

[SRU] Option --net fails (other than for Class C)

ubuntu-vm-builder

254966

The --ssh-key changed behavior between hardy-updates and hardy-proposed

ubuntu-vm-builder

206280

[hardy] Error opening config file: /etc/sensors.conf

xsensors

Testing/UbuntuTestingDay/20090622 (last edited 2009-07-14 15:22:46 by astatine)