Hi All, Autotesting is back-up and running.
The code looks, IMHO, a bit better this time, the set-up the details are easier and there is even a man/README file. http://git.debian.org/?p=debian-live/autotesting.git;a=tree; http://git.debian.org/?p=debian-live/autotesting.git;a=blob;f=README.setup; http://git.debian.org/?p=debian-live/autotesting.git;a=blob;f=README; So I have set autotesting up and running on a server. Today all Debian-live-5.01 images were tested, 24 tests in total.. The results are available at:- http://autotesting.livecd.org/autotesting/current/debian-live/5.01/ e.g. http://autotesting.livecd.org/autotesting/current/debian-live/5.01/i386/usb-hdd/kde-desktop/ Or by date:- http://autotesting.livecd.org/autotesting/debian-live/5.01/ e.g. http://autotesting.livecd.org/autotesting/debian-live/5.01/amd64/iso-cd/lxde-desktop/2009-07-08/ Mostly normal results for example:- http://autotesting.livecd.org/autotesting/current/debian-live/5.01/i386/iso-cd/xfce-desktop/final-screenshot.png http://autotesting.livecd.org/autotesting/current/debian-live/5.01/i386/iso-cd/xfce-desktop/montage-of-video-frames.png http://autotesting.livecd.org/autotesting/current/debian-live/5.01/i386/iso-cd/xfce-desktop/autotesting.ogv [19M] Some interesting tests are below. I need to see if this is qemu, download errors or a problem with the image. :- http://autotesting.livecd.org/autotesting/current/debian-live/5.01/amd64/iso-cd/gnome-desktop/final-screenshot.png http://autotesting.livecd.org/autotesting/current/debian-live/5.01/amd64/usb-hdd/gnome-desktop/final-screenshot.png http://autotesting.livecd.org/autotesting/current/debian-live/5.01/amd64/iso-cd/xfce-desktop/final-screenshot.png http://autotesting.livecd.org/autotesting/current/debian-live/5.01/amd64/usb-hdd/xfce-desktop/final-screenshot.png All I need is some 5.0.2 images and maybe some auto-built images to test. :) To Do: Complete a md5sum check of each download. Feedback welcome. Regards, Brendan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
