[Fedora QA] #260: Cover USB-written images better in installation validation testing
by fedora-badges
#260: Cover USB-written images better in installation validation testing
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
It became clear in the Fedora 16 cycle that use of Fedora images (both
live and non-live) written to USB sticks is now extensive, and our current
installation validation tests don't really test this method very
comprehensively. We should extend the installation validation matrix to
cover at least boot and installation in the following situations:
* Live image written to USB stick using livecd-iso-to-disk
* Live image written to USB stick using liveusb-creator
* Live image written to USB stick using dd
* Non-live image written to USB stick using livecd-iso-to-disk
* Non-live image written to USB stick using dd
We may want to consider different l-i-t-d parameters also (especially the
use or non-use of --format could be significant). We could also cover use
of unetbootin as an _informational_ (non-blocking) test, but I'm not super
sure about that.
Part of this ticket is deciding on the best way to represent this -
whether it's by simply creating new test cases and adding them into the
matrix, or somehow re-rendering the matrix to cover these cases as
'variants' of existing test cases, or some other method.
The changes from this ticket and https://fedorahosted.org/fedora-
qa/ticket/256 should be co-ordinated (possibly handled by the same person
or group) as they both involve similar questions of how to revise the
matrix to cover more situations.
This should be completed by Fedora 17 Alpha TC1.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/260>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 9 months
GNOME shell broken after suspend and resume for driver r300_dri
by Christoph Frieben
Can anybody report success for the suspend and resume cycle triggered
from within the GNOME shell when the graphics card is based on some
R300/R400 variant? In my case, the shell is still broken after resume.
The video device is some ATI Radeon X800 card which is using the R420
chip. Only a black desktop, a mouse pointer and the GNOME panel are
visible after resume. The desktop is not completely frozen since I am
still able to move the mouse pointer. It is also possible to switch to
a VT in order to reboot the system. Thanks, ~C
PS: The F15 development cycle is nearing completion, and in my
opinion, this is a major usability issue.
11 years, 12 months
F16 Alpha GRUB install failure
by Michael Schwendt
Between TC1 and release of F16 Alpha, something must have changed to the
worse with regard to installing GRUB to a partition's primary sector.
Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3.
Anaconda now reports failure to install, and I've found this on virtual
console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a
partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be
installed in this setup using blocklists. However, blocklists are
UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
12 years, 1 month
[Fedora QA] #258: Create EC2 test cases and integrate into validation matrices
by fedora-badges
#258: Create EC2 test cases and integrate into validation matrices
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: critical | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
tflink highlighted the need for better EC2 testing in the F16 QA
retrospective. We should create test cases for install (or direct
deployment via image) of Fedora onto EC2 and validating basic
functionality. This might go into the Base matrix rather than the
installation matrix.
Assigning to tflink and dgilmore as they're the most plugged into EC2, it
seems.
Should be complete ideally by F17 Alpha TC1, definitely by Final TC1.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/258>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 2 months
retracing server issues
by Michael Cronenworth
Every time I use the retrace server for the past few weeks I fail to get
a backtrace. The log shows this:
Initializing virtual root
<snipping out 50 repeating lines>
Initializing virtual root
Saving crash statistics
Retrace job finished successfully
Backtrace parsing failed for .
1:0: No frame and no thread found.
Is this a known issue?
12 years, 2 months
[Fedora QA] #257: Create and maintain F17 install test plan
by fedora-badges
#257: Create and maintain F17 install test plan
-----------------------------------------+----------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
We need an installation test plan for Fedora 17, can be modelled on
previous ones:
* https://fedoraproject.org/wiki/QA:Fedora_16_Install_Test_Plan
* https://fedoraproject.org/wiki/QA:Fedora_15_Install_Test_Plan
etc. Note that some of the copypasta on that page dates back to well
before the current matrices and blocker process were in operation and
could probably be revised.
The main benefit of the test plan should be to plan for major changes to
the installation process caused by F17 features. The anaconda UI rewrite
is an obvious one, but there may be others. For F16, for instance, we
could have used this document to better handle the grub2 and GPT changes.
So for F17 we should take advantage of the opportunity.
This needs to be in place ahead of F17 Alpha TC1.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/257>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 2 months
xorg broken dependencies in Rawhide
by Andre Robatino
For over a month now, there have been a large number of broken xorg
dependencies in Rawhide. I've tried using yum --skip-broken with
distro-sync, update, and upgrade. X starts but the login prompt never
appears, forcing me to use text (multiuser) mode. Is there a simple fix
(say manually removing or downgrading some package)?
[root@localhost ~]# yum --skip-broken distro-sync xorg\*
Loaded plugins: langpacks, presto, refresh-packagekit, security
Setting up Distribution Synchronization Process
Resolving Dependencies
--> Running transaction check
---> Package xorg-x11-drv-apm.x86_64 0:1.2.3-8.fc17 will be updated
---> Package xorg-x11-drv-apm.x86_64 0:1.2.3-11.fc17 will be an update
---> Package xorg-x11-drv-ast.x86_64 0:0.93.9-1.fc17 will be updated
---> Package xorg-x11-drv-ast.x86_64 0:0.93.9-2.fc17 will be an update
---> Package xorg-x11-drv-ati.x86_64 0:6.14.3-1.fc17 will be updated
---> Package xorg-x11-drv-ati.x86_64
0:6.14.3-4.20111125git534fb6e41.fc17 will
be an update
---> Package xorg-x11-drv-cirrus.x86_64 0:1.3.2-11.fc17 will be updated
---> Package xorg-x11-drv-cirrus.x86_64 0:1.3.2-14.fc17 will be an update
---> Package xorg-x11-drv-dummy.x86_64 0:0.3.4-8.fc17 will be updated
---> Package xorg-x11-drv-dummy.x86_64 0:0.3.4-10.fc17 will be an update
---> Package xorg-x11-drv-evdev.x86_64
0:2.6.99-3.20111110gita9cdb6590.fc17 will
be updated
---> Package xorg-x11-drv-evdev.x86_64
0:2.6.99-4.20111110gita9cdb6590.fc17 will
be an update
---> Package xorg-x11-drv-fbdev.x86_64 0:0.4.2-3.fc17 will be updated
---> Package xorg-x11-drv-fbdev.x86_64 0:0.4.2-4.fc17 will be an update
---> Package xorg-x11-drv-glint.x86_64 0:1.2.6-2.fc17 will be updated
---> Package xorg-x11-drv-glint.x86_64 0:1.2.6-4.fc17 will be an update
---> Package xorg-x11-drv-i128.x86_64 0:1.3.4-11.fc17 will be updated
---> Package xorg-x11-drv-i128.x86_64 0:1.3.4-13.fc17 will be an update
---> Package xorg-x11-drv-i740.x86_64 0:1.3.2-10.fc17 will be updated
---> Package xorg-x11-drv-i740.x86_64 0:1.3.2-12.fc17 will be an update
---> Package xorg-x11-drv-intel.x86_64 0:2.16.901-1.fc17 will be updated
---> Package xorg-x11-drv-intel.x86_64 0:2.17.0-5.fc17 will be an update
--> Processing Dependency: libxcb-util.so.0()(64bit) for package:
xorg-x11-drv-intel-2.17.0-5.fc17.x86_64
---> Package xorg-x11-drv-keyboard.x86_64 0:1.6.0-3.fc17 will be updated
---> Package xorg-x11-drv-keyboard.x86_64 0:1.6.0-4.fc17 will be an update
---> Package xorg-x11-drv-mach64.x86_64 0:6.9.0-3.fc17 will be updated
---> Package xorg-x11-drv-mach64.x86_64 0:6.9.0-5.fc17 will be an update
---> Package xorg-x11-drv-mga.x86_64 0:1.4.13-10.fc17 will be updated
---> Package xorg-x11-drv-mga.x86_64 0:1.4.13-11.fc17 will be an update
---> Package xorg-x11-drv-mouse.x86_64 0:1.7.1-3.fc17 will be updated
---> Package xorg-x11-drv-mouse.x86_64 0:1.7.1-4.fc17 will be an update
---> Package xorg-x11-drv-nouveau.x86_64 1:0.0.16-28.20110720gitb806e3f.fc17
will be updated
---> Package xorg-x11-drv-nouveau.x86_64 1:0.0.16-30.20110720gitb806e3f.fc17
will be an update
---> Package xorg-x11-drv-nv.x86_64 0:2.1.18-9.fc17 will be updated
---> Package xorg-x11-drv-nv.x86_64 0:2.1.18-11.fc17 will be an update
---> Package xorg-x11-drv-openchrome.x86_64 0:0.2.904-16.fc17 will be
updated
---> Package xorg-x11-drv-openchrome.x86_64 0:0.2.904-18.fc17 will be an
update
---> Package xorg-x11-drv-qxl.x86_64 0:0.0.21-9.fc17 will be updated
---> Package xorg-x11-drv-qxl.x86_64 0:0.0.21-11.fc17 will be an update
---> Package xorg-x11-drv-r128.x86_64 0:6.8.1-12.fc17 will be updated
---> Package xorg-x11-drv-r128.x86_64 0:6.8.1-13.fc17 will be an update
---> Package xorg-x11-drv-rendition.x86_64 0:4.2.4-8.fc17 will be updated
---> Package xorg-x11-drv-rendition.x86_64 0:4.2.4-10.fc17 will be an update
---> Package xorg-x11-drv-s3virge.x86_64 0:1.10.4-9.fc17 will be updated
---> Package xorg-x11-drv-s3virge.x86_64 0:1.10.4-11.fc17 will be an update
---> Package xorg-x11-drv-savage.x86_64 0:2.3.3-2.fc17 will be updated
---> Package xorg-x11-drv-savage.x86_64 0:2.3.3-3.fc17 will be an update
---> Package xorg-x11-drv-siliconmotion.x86_64 0:1.7.5-2.fc17 will be
updated
---> Package xorg-x11-drv-siliconmotion.x86_64 0:1.7.5-5.fc17 will be an
update
---> Package xorg-x11-drv-sis.x86_64 0:0.10.3-8.fc17 will be updated
---> Package xorg-x11-drv-sis.x86_64 0:0.10.3-9.fc17 will be an update
---> Package xorg-x11-drv-sisusb.x86_64 0:0.9.4-8.fc17 will be updated
---> Package xorg-x11-drv-sisusb.x86_64 0:0.9.4-9.fc17 will be an update
---> Package xorg-x11-drv-synaptics.x86_64 0:1.5.99-1.20111110.fc17 will
be updated
---> Package xorg-x11-drv-synaptics.x86_64 0:1.5.99-2.20111110.fc17 will
be an
update
---> Package xorg-x11-drv-tdfx.x86_64 0:1.4.3-9.fc17 will be updated
---> Package xorg-x11-drv-tdfx.x86_64 0:1.4.3-11.fc17 will be an update
---> Package xorg-x11-drv-trident.x86_64 0:1.3.4-8.fc17 will be updated
---> Package xorg-x11-drv-trident.x86_64 0:1.3.4-10.fc17 will be an update
---> Package xorg-x11-drv-v4l.x86_64 0:0.2.0-15.fc17 will be updated
---> Package xorg-x11-drv-v4l.x86_64 0:0.2.0-16.fc17 will be an update
---> Package xorg-x11-drv-vesa.x86_64 0:2.3.0-10.fc17 will be updated
---> Package xorg-x11-drv-vesa.x86_64 0:2.3.0-11.fc17 will be an update
---> Package xorg-x11-drv-vmmouse.x86_64 0:12.7.0-4.fc17 will be updated
---> Package xorg-x11-drv-vmmouse.x86_64 0:12.7.0-5.fc17 will be an update
---> Package xorg-x11-drv-vmware.x86_64 0:11.0.3-6.fc17 will be updated
---> Package xorg-x11-drv-vmware.x86_64 0:11.0.3-9.fc17 will be an update
---> Package xorg-x11-drv-void.x86_64 0:1.4.0-3.fc17 will be updated
---> Package xorg-x11-drv-void.x86_64 0:1.4.0-4.fc17 will be an update
---> Package xorg-x11-drv-voodoo.x86_64 0:1.2.4-8.fc17 will be updated
---> Package xorg-x11-drv-voodoo.x86_64 0:1.2.4-10.fc17 will be an update
---> Package xorg-x11-drv-wacom.x86_64 0:0.11.99.1-5.20111110.fc17 will
be updated
---> Package xorg-x11-drv-wacom.x86_64 0:0.12.0-1.fc17 will be an update
---> Package xorg-x11-server-Xorg.x86_64 0:1.11.1-2.fc17 will be updated
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-fpit-1.4.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-elographics-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-hyperpen-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-penmount-1.5.0-3.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-acecad-1.5.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-mutouch-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-aiptek-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-fpit-1.4.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-elographics-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-hyperpen-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-penmount-1.5.0-3.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-acecad-1.5.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-mutouch-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-aiptek-1.4.1-2.fc17.x86_64
---> Package xorg-x11-server-Xorg.x86_64 0:1.11.99.1-11.20111109.fc17
will be an
update
--> Running transaction check
---> Package xcb-util.x86_64 0:0.3.6-2.fc15 will be updated
--> Processing Dependency: libxcb-aux.so.0()(64bit) for package:
startup-notification-0.12-1.fc16.x86_64
---> Package xcb-util.x86_64 0:0.3.8-1.fc17 will be an update
---> Package xorg-x11-server-Xorg.x86_64 0:1.11.1-2.fc17 will be updated
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-fpit-1.4.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-elographics-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-hyperpen-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-penmount-1.5.0-3.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-acecad-1.5.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-mutouch-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-aiptek-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-fpit-1.4.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-elographics-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-hyperpen-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-penmount-1.5.0-3.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-acecad-1.5.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-mutouch-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-aiptek-1.4.1-2.fc17.x86_64
--> Running transaction check
---> Package startup-notification.x86_64 0:0.12-1.fc16 will be updated
---> Package startup-notification.x86_64 0:0.12-2.fc17 will be an update
---> Package xorg-x11-server-Xorg.x86_64 0:1.11.1-2.fc17 will be updated
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-fpit-1.4.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-elographics-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-hyperpen-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-penmount-1.5.0-3.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-acecad-1.5.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-mutouch-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-0) >= 4 for package:
xorg-x11-drv-aiptek-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-fpit-1.4.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-elographics-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-hyperpen-1.4.1-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-penmount-1.5.0-3.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-acecad-1.5.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-mutouch-1.3.0-2.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-13) >= 0 for package:
xorg-x11-drv-aiptek-1.4.1-2.fc17.x86_64
--> Running transaction check
---> Package xorg-x11-server-Xorg.x86_64 0:1.11.1-2.fc17 will be updated
---> Package xorg-x11-server-Xorg.x86_64 0:1.11.99.1-11.20111109.fc17
will be an
update
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-vmmouse-12.7.0-5.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-mouse-1.7.1-4.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-evdev-2.6.99-4.20111110gita9cdb6590.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-synaptics-1.5.99-2.20111110.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-keyboard-1.6.0-4.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-wacom-0.12.0-1.fc17.x86_64
--> Processing Dependency: xserver-abi(xinput-20111109) >= 0 for package:
xorg-x11-drv-void-1.4.0-4.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-mga-1.4.13-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-nv-2.1.18-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-voodoo-1.2.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-savage-2.3.3-3.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-s3virge-1.10.4-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-sisusb-0.9.4-9.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-glint-1.2.6-4.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-i128-1.3.4-13.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-ast-0.93.9-2.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-vesa-2.3.0-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-cirrus-1.3.2-14.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
1:xorg-x11-drv-nouveau-0.0.16-30.20110720gitb806e3f.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-vmware-11.0.3-9.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-intel-2.17.0-5.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-i740-1.3.2-12.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-mach64-6.9.0-5.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-rendition-4.2.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-ati-6.14.3-4.20111125git534fb6e41.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-tdfx-1.4.3-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-openchrome-0.2.904-18.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-fbdev-0.4.2-4.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-qxl-0.0.21-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-apm-1.2.3-11.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-r128-6.8.1-13.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-siliconmotion-1.7.5-5.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-v4l-0.2.0-16.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-sis-0.10.3-9.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-trident-1.3.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(videodrv-20111109) >= 0 for package:
xorg-x11-drv-dummy-0.3.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-nv-2.1.18-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-savage-2.3.3-3.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-s3virge-1.10.4-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-sisusb-0.9.4-9.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-evdev-2.6.99-4.20111110gita9cdb6590.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-glint-1.2.6-4.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-i128-1.3.4-13.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-ast-0.93.9-2.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-cirrus-1.3.2-14.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
1:xorg-x11-drv-nouveau-0.0.16-30.20110720gitb806e3f.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-intel-2.17.0-5.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-wacom-0.12.0-1.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-tdfx-1.4.3-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-qxl-0.0.21-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-siliconmotion-1.7.5-5.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-v4l-0.2.0-16.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-dummy-0.3.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-vmmouse-12.7.0-5.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-keyboard-1.6.0-4.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-mga-1.4.13-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-voodoo-1.2.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-mach64-6.9.0-5.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-vesa-2.3.0-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-vmware-11.0.3-9.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-i740-1.3.2-12.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-synaptics-1.5.99-2.20111110.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-rendition-4.2.4-10.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-ati-6.14.3-4.20111125git534fb6e41.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-openchrome-0.2.904-18.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-mouse-1.7.1-4.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-fbdev-0.4.2-4.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-apm-1.2.3-11.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-r128-6.8.1-13.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-void-1.4.0-4.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-sis-0.10.3-9.fc17.x86_64
--> Processing Dependency: xserver-abi(ansic-20111109) >= 0 for package:
xorg-x11-drv-trident-1.3.4-10.fc17.x86_64
--> Running transaction check
---> Package startup-notification.x86_64 0:0.12-1.fc16 will be updated
---> Package startup-notification.x86_64 0:0.12-2.fc17 will be an update
--> Processing Dependency: libxcb-util.so.0()(64bit) for package:
startup-notification-0.12-2.fc17.x86_64
Packages skipped because of dependency problems:
startup-notification-0.12-2.fc17.x86_64 from rawhide
xcb-util-0.3.8-1.fc17.x86_64 from rawhide
xorg-x11-drv-apm-1.2.3-11.fc17.x86_64 from rawhide
xorg-x11-drv-ast-0.93.9-2.fc17.x86_64 from rawhide
xorg-x11-drv-ati-6.14.3-4.20111125git534fb6e41.fc17.x86_64 from rawhide
xorg-x11-drv-cirrus-1.3.2-14.fc17.x86_64 from rawhide
xorg-x11-drv-dummy-0.3.4-10.fc17.x86_64 from rawhide
xorg-x11-drv-evdev-2.6.99-4.20111110gita9cdb6590.fc17.x86_64 from
rawhide
xorg-x11-drv-fbdev-0.4.2-4.fc17.x86_64 from rawhide
xorg-x11-drv-glint-1.2.6-4.fc17.x86_64 from rawhide
xorg-x11-drv-i128-1.3.4-13.fc17.x86_64 from rawhide
xorg-x11-drv-i740-1.3.2-12.fc17.x86_64 from rawhide
xorg-x11-drv-intel-2.17.0-5.fc17.x86_64 from rawhide
xorg-x11-drv-keyboard-1.6.0-4.fc17.x86_64 from rawhide
xorg-x11-drv-mach64-6.9.0-5.fc17.x86_64 from rawhide
xorg-x11-drv-mga-1.4.13-11.fc17.x86_64 from rawhide
xorg-x11-drv-mouse-1.7.1-4.fc17.x86_64 from rawhide
1:xorg-x11-drv-nouveau-0.0.16-30.20110720gitb806e3f.fc17.x86_64 from
rawhide
xorg-x11-drv-nv-2.1.18-11.fc17.x86_64 from rawhide
xorg-x11-drv-openchrome-0.2.904-18.fc17.x86_64 from rawhide
xorg-x11-drv-qxl-0.0.21-11.fc17.x86_64 from rawhide
xorg-x11-drv-r128-6.8.1-13.fc17.x86_64 from rawhide
xorg-x11-drv-rendition-4.2.4-10.fc17.x86_64 from rawhide
xorg-x11-drv-s3virge-1.10.4-11.fc17.x86_64 from rawhide
xorg-x11-drv-savage-2.3.3-3.fc17.x86_64 from rawhide
xorg-x11-drv-siliconmotion-1.7.5-5.fc17.x86_64 from rawhide
xorg-x11-drv-sis-0.10.3-9.fc17.x86_64 from rawhide
xorg-x11-drv-sisusb-0.9.4-9.fc17.x86_64 from rawhide
xorg-x11-drv-synaptics-1.5.99-2.20111110.fc17.x86_64 from rawhide
xorg-x11-drv-tdfx-1.4.3-11.fc17.x86_64 from rawhide
xorg-x11-drv-trident-1.3.4-10.fc17.x86_64 from rawhide
xorg-x11-drv-v4l-0.2.0-16.fc17.x86_64 from rawhide
xorg-x11-drv-vesa-2.3.0-11.fc17.x86_64 from rawhide
xorg-x11-drv-vmmouse-12.7.0-5.fc17.x86_64 from rawhide
xorg-x11-drv-vmware-11.0.3-9.fc17.x86_64 from rawhide
xorg-x11-drv-void-1.4.0-4.fc17.x86_64 from rawhide
xorg-x11-drv-voodoo-1.2.4-10.fc17.x86_64 from rawhide
xorg-x11-drv-wacom-0.12.0-1.fc17.x86_64 from rawhide
xorg-x11-server-Xorg-1.11.99.1-11.20111109.fc17.x86_64 from rawhide
[root@localhost ~]#
12 years, 2 months
Re: F17 QA schedule modification proposal
by Dennis Gilmore
Inicio del mensaje redirigido:
Fecha: Mon, 19 Dec 2011 10:35:48 -0600
Desde: Dennis Gilmore <dgilmore(a)redhat.com>
Para: test(a)lists.fedoraproject.org
Asunto: Re: F17 QA schedule modification proposal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El Mon, 19 Dec 2011 08:25:41 -0700
Robyn Bergeron <rbergero(a)redhat.com> escribió:
> On 12/05/2011 11:43 AM, Adam Williamson wrote:
> > On Mon, 2011-12-05 at 11:34 -0700, Robyn Bergeron wrote:
> >> On 11/29/2011 04:01 PM, Adam Williamson wrote:
> >>> Hi, Robyn. As discussed on the test list this week and at our
> >>> meeting, we'd like to propose the schedule modification described
> >>> in
> >>> https://lists.fedoraproject.org/pipermail/test/2011-November/104583.html
> >>> to the F17 QA schedule. Could you put that in there? Thanks!
> >> Sorry - this mail got filtered in ways that are all sorts of
> >> wrong. :(
> >>
> >> My only concern with the schedule as proposed is that we are
> >> essentially doing the Alpha Test Compose prior to Feature Freeze,
> >> which is the point where features should be testable. I've popped
> >> in the existing dates below, but I just want to point out that I
> >> think we know from past experience that a lot of features don't
> >> hit their feature freeze deadline until *on the actual deadline*,
> >> which means that we are essentially testing a compose of stuff a
> >> full week before I expect people to finish procrastinating and
> >> getting their stuff done. We still have the actual release
> >> candidate after that, but I don't want us to basically pull in a
> >> date and find out that it's not helpful because all the breaking
> >> pieces get pulled in/finished after the test compose date.
> >>
> >> Pre-Alpha Rawhide Acceptance Test Plan #1 2012-01-19
> >> Feature Submission Deadline 2012-01-24
> >> Pre-Alpha Rawhide Acceptance Test Plan #2 2012-01-26
> >> Test Alpha 'Test Compose' 2012-01-31
> >> Feature Freeze (Testable|Complete) 2012-02-07
> >> Fedora 17 Alpha Go/No-Go Meeting 2012-02-22
> >>
> >> Test Beta 'Test Compose' 2012-03-06
> >> Fedora 17 Beta Go/No-Go Meeting 2012-03-28
> >>
> >> Test 'Final' Test Compose (TC) 2012-04-09
> >> Fedora 17 Final Go/No-Go Meeting 2012-05-01
> >>
> >>
> >> Or it's possible that I'm nuts and it's not worth worrying
> >> over. :) We do the Test Compose for Beta a week before Features
> >> are required to be at 100%, but of course, they should already be
> >> testable/complete at alpha, so the breakage scenario in Beta is
> >> far smaller, theoretically.
> > I think in practice it's not such a huge deal. As far as release
> > validation goes we just don't really *care* about the feature
> > process very much.
> >
> > The main thing a TC achieves for us is to give us a sanity check on
> > the compose process - can we actually compose a full set of images
> > at this time, are they crazily over-size, etc - and the ability to
> > start identifying blocker bugs. I just don't see that it's actually
> > a problem if the TCs contain features that are incomplete, or if
> > some feature lands in TC3 that wasn't in TC1. All the work we did
> > identifying blockers in TC1 is still likely to be of value, and
> > even if TC3 introduces some new blocker, we haven't *lost* anything.
> Hey,
>
> So I've been ... afflicted with "the travel plague" (where I travel)
> and also "the death plague" (where I've been wanting to die). I
> haven't forgotten about this - I just pulled it up to make the new
> mods, but I need to talk to Dennis and make sure he's kosher with
> pulling back the Compose dates a week, particularly the Alpha (since
> the date the Alpha Compose would move to, 2/7, is also the date of
> dropping orphans and branching from rawhide, which sounds like it
> might be a busy day.)
>
> Dennis, what say ye? Is that doable or not for any particular reason?
TCS by there nature are throw away and never intended to be
complete or shipable. its to see where we are and whats broken.
replacing the RATS composes with TCS is fine. It should give us a early
warning if the world is broken and its really no more work for me than
doing a rats compose.
So i would say having a TC on the day of dropping orphans is a bit
silly, it should be the day after, to see what we broke.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAk7vZ+oACgkQkSxm47BaWfezOACfVRIJgVpDcwVMlPavzVRwElFx
EIAAnjFUF/Nhfe5x/KNHcVRRQb5B+cEm
=mwiB
-----END PGP SIGNATURE-----
12 years, 2 months