Thanks for the initiative, this is a great project idea! I'm not an
xorg expert, but some comments below ...
On Fri, 2009-02-13 at 01:38 +0100, FD Cami wrote:
> Running test cases only requires having the missing hardware, some
> free
> time, and being able to use bugzilla.
> Possible test cases are basic 2D tests, for instance x11perf and full
> screen movies ; 3D tests, like glxgears and mesa-demos, then GL
> regression testing with using piglit.
> Desktop effects using Compiz/KDE would be next, then to 3D
> applications
> like Blender, ending with 3D games like GL-117 and FlightGear for
> instance.
In my experience ... diagnosing, debugging and fixing Xorg issues is
fairly difficult to do remotely. Especially when the system
hangs/crashes/freezes. Is there a set of basic information we should
provide the developers to ensure that have all they need to "process"
the defect?
* What system configuration is under test (smolt profile)
* What test is being executed (links to wiki tests or piglit
info)?
* Any config or log files captured during testing (messages,
Xorg.0.log, dmesg)?
* Instructions or script to setup kdump for capturing kernel
crashes (http://fedoraproject.org/wiki/Kernel/kdump)?
* An optional Xorg debug package or something that enables verbose
debugging output (if requested by development)?
Thanks,
James
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
