Pre-Beta Acceptance Test Plan
by Tao Wu
Greetings folks,
Just wanted to summarize how testing held up for the pre-beta acceptance test run of Fedora 15. Thanks for your attention. It is a good news that the pre-RC installation version has passed the major test, which is used to identify any major test blockers prior to the Test Compose (TC).Let's expect the exciting coming out of F15-TC1 next week!
If you have spare time and want to contribute by verify this version, the test cases and results can be found on the following URL:
https://fedoraproject.org/wiki/Test_Results:Fedora_15_Pre-RC_Acceptance_T...
Thanks a lot!
Good Luck,
Tao Wu
12 years, 9 months
New BugZapper Introduction
by Pete Wojtaszek
Hello ladies and gentlemen,
My name is Pete aka wojox. I'm a thirty-nine year old
systems administrator from San Antonio, Tx. I have been
involved in Linux for quite a few years. Mainly on the
Debian side of things. I'm familiar with YUM and RPM as
well.
I've reported a fair amount of bugs in Ubuntu, but never
triaged. I would be looking for some form of mentorship
if someone would have me.
Thank you for your support.
Pete Wojtaszek
wojox
wojox AT irc.freenode.net
12 years, 9 months
proposal: 'base' validation matrix
by Adam Williamson
Hey, folks. So, right now, as most of you know, we have two release
validation 'matrices' - sets of tests we run and document on each
candidate build of Fedora to check compliance with the release criteria.
A few of us have been working in ticket #151 -
https://fedorahosted.org/fedora-qa/ticket/151 - to ensure the tests are
in line with the criteria, particularly that we have tests to cover each
criterion, and we've introduced a few new tests to cover criteria that
weren't previously covered.
Some of these don't really fit easily into the category of
'installation' tests or 'desktop' tests, so I'm proposing we introduce a
new, third matrix, which I'm currently thinking of as 'base'. There have
already been three tests written in this proposed new category:
https://fedoraproject.org/wiki/QA:Testcase_base_firstboot
https://fedoraproject.org/wiki/QA:Testcase_base_startup
https://fedoraproject.org/wiki/QA:Testcase_base_system_logging
there will likely be more as we go through the Beta and Final criteria.
I've thrown up a quick draft of how the matrix might look here:
https://fedoraproject.org/wiki/User:Adamwill/Draft_base_validation_matrix
Just wanted to make sure the group knows about this week, and ask for
feedback on the test cases, the matrix and the overall plan here - do
you agree a third matrix is the best way to organize things? Any ideas
for naming, etc? Any comments on the test cases written so far? Thanks!
(also thanks to Athmane Madjouj and Rui He for helping out with this
work.)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12 years, 9 months
Clock Issues in Rawhide
by Clyde E. Kunkel
Recently, the time in the gnome status bar has been incrementing by UTC
offset for my locale. I reset it using date time settings but it wasn't
holding. Then I noticed:
systemd[1]: Cannot add dependency job for unit hwclock-load.service,
ignoring: Unit hwclock-load.service failed to load: No such file or
directory. See system logs and 'systemctl status' for details.
And indeed the service was missing from /lib/systemd/system. yum
whatprovides didn't show anything, so I copied the missing services
(also ...save.service) from a F15 installation and that fixed the problem.
What I don't know is who/what is responsible for providing the
hwclock-load.service files in /lib/systemd/system. systemd-units? If
anyone can help with this, I will do some more testing and, if
indicated, create a bz.
TIA
--
Regards,
OldFart
12 years, 9 months