[Test-Announce] Call for Test Days for Fedora 18
by Adam Williamson
Hey, folks. It's that time again - time to start thinking about Test
Days for Fedora 18.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization, or any combination of the
two. To propose a Test Day, just file a ticket in QA trac - full details
are at https://fedoraproject.org/wiki/QA/Test_Days/Create . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at
https://fedoraproject.org/wiki/QA/Fedora_18_test_days . There are many
slots open right now, with the earliest on 2012-08-09 and the latest
2012-11-01. Consider the development schedule, though, in deciding when
you want to run your Test Day - for some topics you may want to avoid
the time before the Alpha release or the time after the feature freeze
or the Final freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific timeframe due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or timeframe you'd
like, and we'll figure it out from there.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any other member of the QA team on test@ or in
#fedora-qa on IRC. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
11 years, 2 months
[Fedora QA] #151: Tests consistent with Criterion
by fedora-badges
#151: Tests consistent with Criterion
---------------------------+------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 15
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
Criteria was kept changing during F-14 test cycle, but some installation
tests didn't update accordingly. On the other hand, the criterion should
be modified to include preupgrade_from_older_release test and new tests
created for F-15.
= enhancement recommendation =
Installation tests need be reviewed and updated to fit for the criterion.
Criterion for preupgrade_from_older_release test is required.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/151>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 2 months
[Fedora QA] #325: Update sync fails if update title is too long
by fedora-badges
#325: Update sync fails if update title is too long
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: defect | Status: new
Priority: blocker | Milestone: Fedora 18
Component: Blocker bug tracker page | Version: 1.0
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= bug description =
If an update's title is too long, it won't fit into the database field
(currently 2048 characters long) and the sync crashes prior to completing.
[https://admin.fedoraproject.org/updates/FEDORA-2012-20337/ A recent ocaml
update caused this bug to surface]
= bug analysis =
At the moment, the tracker's sync operation fails 100% of the time since
the previously mentioned ocaml update is marked as an NTH fix.
= fix recommendation =
This should be fixed properly, but at this point I'm just planning to do a
dirty hack of checking the title's length against a hardcoded value and
truncating it if it's too long.
This is the wrong way to fix the issue and I suspect that it'll cause
problems with link formation to bodhi but it needs to be fixed well enough
now so that sync doesn't crash midway through.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/325>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 2 months
F18 beta experience under VM
by Michael Cronenworth
Getting to the first anaconda UI screen took a good 1-2 minutes. I
wasn't sure if the VM had locked up as I had no indication of work being
done. I can see people being frustrated with the wait and rebooting a
few times and then posting on @test or @users that F18 won't install.
The custom partitioning manager, as mentioned on other threads, is
confusing and buggy. The VM I tested with was already F18 alpha.
Anaconda saw F18 already installed, and when I offered to reformat the
existing partitions they disappeared from the F18 alpha list (not
expecting that) and I found them under the F18 beta partitioning without
a mount point. When I added a mount point the partition was duplicated
so for example I had a 500MB ext4 partition and gave it a /boot mount
point, which created a 500MB "Boot" ext4 partition leaving the original
partition still on my screen.
Overall I think the NewUI is a step in the right direction even if it is
a very rough, if not still in carbon form, diamond.
May I suggest that the "Date/Time" setting be moved to the "User
Settings" page, which is during package installation? The root password
setting looks lonely.
Michael
11 years, 2 months
resume failed for the 2nd time since I upgraded to F18
by Julian Sikorski
Hi,
since I upgraded to F18, resume from S3 has failed for me 2 times
already. It worked many more times, but still it is a bit concerning,
and also makes it way harder to pinpoint. All I can see in the logs is this:
Dec 15 04:19:55 snowball2 systemd-logind[753]: Lid closed.
Dec 15 04:19:55 snowball2 systemd-logind[753]: Suspending...
Dec 15 04:19:57 snowball2 systemd[1]: SELinux Got Sender :1.0
Dec 15 04:19:57 snowball2 systemd[1]: Starting Sleep.
Dec 15 04:19:57 snowball2 systemd[1]: Reached target Sleep.
Dec 15 04:19:57 snowball2 systemd[1]: Starting Suspend...
Dec 15 04:19:57 snowball2 systemd-sleep[8033]:
/usr/lib/systemd/system-sleep/notify-upower.sh exited with exit status 1.
Dec 15 04:19:57 snowball2 systemd-sleep[8033]: Suspending system...
When I tried to resume the machine in the morning, all I could see was a
blinking cursor. Where should I look in order to debug this problem and
investigate what is going on?
Regards,
Julian
11 years, 3 months
update some testcases
by Lili Nie
Hi all,
I have taken part in the "improve the test wiki page"proposed by Tao Wu.
As there is huge change in f18, some test cases in the "test wiki page"seem to be inapplicable.
I suggest to modify some of them, as the following:
Testcase::https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%2...
How to test
Boot the installer using any available means
Make sure your disk is set to be encrypted
you can encryted the whole disk before custom partitioning your disk
or encryted part of the disk (for example,/root) after custom partitioning your disk
Select the appropriate disk, and continue installation, choosing all provided defaults
After installation is complete, perform QA:Testcase_base_startup to ensure the installed system boots correctly with the encrypted partitioning
Testcase::https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%2...
How to test
Boot the installer using any available means
Make sure your disk is not set to be encrypted
Select the appropriate disk, and continue installation, choosing all provided defaults
As for the text mode, you should choose"use free space"for the Autopartitioning Options
Complete the installation
Testcase:: https://fedoraproject.org/wiki/QA:Testcase_Partitioning_No_Swap
How to test
Boot the installer using any available means (netinst/boot.iso, PXE, or DVD)
Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue
At the manual partitioning screen, remove the swap partition created by anaconda, and select Finish Partitioning
Complete the installation
Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_p...
How to test
Boot the installer using any available means (netinst/boot.iso, PXE, or DVD)
Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue
At the manual partitioning screen, choose root and click Customize
Place the root filesystem(/) on an ext3 formatted partition,and select Finish Partitioning
Complete the installation
Testcase::https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_...
Boot the installer using any available means (netinst/boot.iso, PXE, or DVD)
Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue
At the manual partitioning screen, choose root and click Customize
Place the root filesystem(/) on an xfs formatted partition,and select Finish Partitioning
Complete the installation
Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext4_rootfs_on_disk_p...
Boot the installer using any available means (netinst/boot.iso, PXE, or DVD)
Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue
At the manual partitioning screen, choose root and click Customize
Place the root filesystem(/) on an ext4 formatted partition,select Standard Partition for Device type
Select Finish Partitioning,and Complete the installation
Any comments on these will be welcome, and as soon as we have a decision
on the changes, I will update the wiki-page.
Thank you,
Lili Nie
11 years, 3 months
Uh-oh something has gone wrong....
by Clyde E. Kunkel
After installing updates from rawhide 20121219 had to revert clutter,
clutter-gtk and mutter to get desktop back. Don't know what is causing
this or who to bz. If anyone knows, tell me and I will bz.
--
Regards,
OldFart
11 years, 3 months
Anyone else using Open vSwitch on F18?
by Ian Pilcher
And getting a ton of SELinux AVCs?
According to https://bugzilla.redhat.com/show_bug.cgi?id=872974#c2,
the openvswitch policy should be in selinux-policy-targeted-
3.11.1-66.fc18.noarch, but I'm seeing a ton of messages related to kmod,
files in /etc/modprobe.d, and a netlink socket.
type=AVC msg=audit(1356894958.32:2022): avc: denied { module_request }
for pid=1584 comm="ovs-vswitchd" kmod="netdev-vnet6"
scontext=system_u:system_r:openvswitch_t:s0
tcontext=system_u:system_r:kernel_t:s0 tclass=system
type=SYSCALL msg=audit(1356894958.32:2022): arch=x86_64 syscall=ioctl
success=no exit=ENODEV a0=10 a1=8913 a2=7fff99c842d0 a3=ffffffff items=0
ppid=1583 pid=1584 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=ovs-vswitchd
exe=2F7573722F7362696E2F6F76732D7673776974636864202864656C6574656429
subj=system_u:system_r:openvswitch_t:s0 key=(null)
type=AVC msg=audit(1356894968.741:2209): avc: denied { nlmsg_write }
for pid=1584 comm="ovs-vswitchd"
scontext=system_u:system_r:openvswitch_t:s0
tcontext=system_u:system_r:openvswitch_t:s0 tclass=netlink_route_socket
type=SYSCALL msg=audit(1356894968.741:2209): arch=x86_64 syscall=sendmsg
success=yes exit=EBADE a0=25 a1=7fff99c83530 a2=0 a3=200 items=0
ppid=1583 pid=1584 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=ovs-vswitchd
exe=2F7573722F7362696E2F6F76732D7673776974636864202864656C6574656429
subj=system_u:system_r:openvswitch_t:s0 key=(null)
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
11 years, 3 months
atkbd messages filling syslog
by Gene Czarcinski
https://bugzilla.redhat.com/show_bug.cgi?id=889794
I have a hard time believe that I am the only person seeing this
problem. It only occurs with a qemu-kvm virtual guest (F17, F18, does
not matter) and running on a F18 virtualization host (with all updates
applied).
The problem is that the guest's syslog is filling with messages:
atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on
isa0060/serio0)
Use 'setkeycodes 00 <keycode>' to make it known.
Yes, entering "setkeycode 00 247" makes it go away but this should not
be happening and it does not happen with a F17 host.
Has anyone else seen this?
Gene
11 years, 3 months