[Fedora QA] #140: Proventester Mentor Request
by fedora-badges
#140: Proventester Mentor Request
-----------------------------------------+----------------------------------
Reporter: mrjfont | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Hi,
I am requesting a mentor in order to join this group. I am looking forward
to make contributions in order to have a final release of Fedora 14. Thank
you;
J. Font
Fedora Project Contributor
Bug Zapper, Triager.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/140>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 2 months
[PATCH] incite bug reporters to post feedback
by François Cami
Hi bodhi@, test@,
The following patch tentatively changes the message bodhi posts to
bugzilla when a build is tagged as an update candidate to make clear
that we expect bug reporters to post their feedbacks on updates in the
bodhi instance.
Please review the message - I am sure someone can make it better.
Caveat emptor: I do not have a bodhi+koji+bz instance, so this is
completely untested.
Signed-Off-By: François Cami <fcami(a)fedoraproject.org>
Patch also attached because I'm pretty sure the inline version will get mangled.
diff --git a/bodhi/controllers.py b/bodhi/controllers.py
index f323291..3c55512 100644
--- a/bodhi/controllers.py
+++ b/bodhi/controllers.py
@@ -971,9 +971,12 @@ class Root(controllers.RootController):
log.debug("Updating newly added bug: %s" % bug)
try:
Bugzilla.byBz_id(bug).add_comment(update,
- "%s has been submitted as an update
for %s.\n%s" %
- (update.title, release.long_name,
- config.get('base_address') +
tg_url(update.get_url())))
+ "%s has been submitted as an update
for %s and "
+ "will soon be available in the
updates-testing "
+ "repository. Please comment on your
experience at:\n"
+ "%s" % (
+ update.title, release.long_name,
+ config.get('base_address') +
tg_url(update.get_url())))
except SQLObjectNotFound:
log.debug('Bug #%d not found in our
database' % bug)
@@ -992,9 +995,12 @@ class Root(controllers.RootController):
# Comment on all bugs
for bug in update.bugs:
bug.add_comment(update,
- "%s has been submitted as an update for %s.\n%s" %
- (update.title, release.long_name,
- config.get('base_address') +
tg_url(update.get_url())))
+ "%s has been submitted as an update for %s and "
+ "will soon be available in the updates-testing "
+ "repository. Please comment on your experience at:\n"
+ "%s" % (
+ update.title, release.long_name,
+ config.get('base_address') +
tg_url(update.get_url())))
# If a request is specified, make it. By default we're submitting
# new updates directly into testing
--
1.7.3.2
13 years, 3 months
Fedora install support for netbooks -- small screen size
by Robert Moskowitz
I am doing another FC12 install on my ASUS 701ee. This is a test
system, and I end up installing every month or so.
Of course with the small screen size, I end up pressing <cntl-N> a lot,
as I cannot see the Next button. And on some screens I just miss some
options, like getting to customize the install packages. I am always
forgetting the key combo to turn that check box on.
Is there some way to either get the ability to pan the screen around or
scroll the screen so that on Netbooks that SHOULD be a popular install
platform for Fedora, can have workable installation?
13 years, 3 months
Xen Dom0 and Fedora
by Steven Haigh
I'm just writing to try and gauge the progress of Xen in newer Fedora
releases.
I spent a bit of the night trying to get F14 to work as a Xen Dom0
using the included 4.0.1 hypervisor - that is until I realised that Dom0
is not available in F14!
So I've rolled everything back to CentOS 5.5 & Xen 3.2.3 via the Gitco
repo and its up and running again. Everything I managed to find says
*maybe* in F15? Anyone in the know able to help out?
--
Steven Haigh
Email: netwiz(a)crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
13 years, 3 months
Package-specific test case and critical path test case project: drafts for review
by Adam Williamson
Hi, everyone. So, in the recent debate about the update process it again
became clear that we were lacking a good process for providing
package-specific test instructions, and particularly specific
instructions for testing critical path functions.
I've been working on a process for this, and now have two draft Wiki
pages up for review which together describe it:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_SOP_test_case_creation
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_SOP_package_test_pl...
the first isn't particularly specific to this, but it was a prerequisite
that I discovered was missing: it's a guide to test case creation in
general, explaining the actual practical process of how you create a
test case, and the best principles to consider in doing it.
The second is what's really specific to this subject. It describes how
to create a set of test cases for a particular package, and a proposed
standardized categorization scheme which will allow us to denote test
cases as being associated with specific packages, and also denote them
as concerning critical path functionality.
Given that mediawiki has a handy API which also allows you to deal with
categories, this should make it easy to both manually and
programmatically derive a list of test cases for a given package, and a
list of *critical path* test cases for a given package. You can do this
manually, but I also envision Bodhi and fedora-easy-karma utilizing the
API so that when an update is pushed for a package for which test cases
have been created under this system, they will link to those test cases;
and when an update is pushed for a critical path package, they will be
able to display separately (and more prominently, perhaps) the list of
test cases relevant to the critical path functionality of the package.
Comments, suggestions and rotten fruit welcome :) I'm particularly
interested in feedback from package maintainers and QA contributors in
whether you feel, just after reading these pages, that you'd be
confident in going ahead and creating some test cases, or if there's
stuff that's scary or badly explained or that you feel like something is
missing and you wouldn't know where to start, etc.
The trac ticket on this is probably valuable for background, explaining
why some things in the proposal are the way they are:
https://fedorahosted.org/fedora-qa/ticket/154
it also mentions one big current omission: dependencies. For instance,
it would be very useful to be able to express 'when yum is updated, we
should also run the PackageKit test plan' (because it's possible that a
change in yum could be fine 'within itself', and all the yum test cases
pass, but could break PackageKit). That's rather complex, though,
especially with a Wiki-based system. If anyone has any bright ideas on
how to achieve this, do chip in! Thanks.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 3 months
F14 cpuspeed / ondemand broken?
by Steven Haigh
I've been trying to nut out an issue with cpuspeed on a Fedora14 box...
It seems when cpuspeed is started, it clocks the frequency back to the
lowest available (350Mhz in my case), and there it stays.
If I do something to create CPU load ( while true; do true; done ) then
the CPU fails to be clocked back up to max frequency. In fact, no matter
what I do on that box the CPU doesn't move from 350Mhz...
To get the system back to 2.8Ghz I need to rmmod the p4-clockmod module.
I thought this might have been something silly with the thresholds so I
set UP_THRESHOLD and DOWN_THRESHOLD manually in /etc/sysconfig/cpuspeed
- however then when starting cpuspeed I see:
# /etc/init.d/cpuspeed restart
Disabling performance cpu frequency scaling: [ OK ]
/etc/init.d/cpuspeed: line 86:
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold: No such file
or directory
/etc/init.d/cpuspeed: line 86:
/sys/devices/system/cpu/cpu1/cpufreq/ondemand/up_threshold: No such file
or directory
Enabling ondemand cpu frequency scaling: [ OK ]
Kernel version is:
# cat /proc/version
Linux version 2.6.35.6-45.fc14.i686
(mockbuild(a)x86-16.phx2.fedoraproject.org) (gcc version 4.5.1 20100924
(Red Hat 4.5.1-4) (GCC) ) #1 SMP Mon Oct 18 23:56:17 UTC 2010
Anyone have any ideas on this? :\
--
Steven Haigh
Email: netwiz(a)crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
13 years, 3 months
CR-48
by Timothy Davis
I don't mean to brag (but I will) but has anyone gotten Fedora on a Google
Chrome Notebook. I know Ubuntu has been installed on it and there are plenty
of howtos on the "that" particular subject but can those instructions be
modified to fit Fedora? or rather can someone modify them. I haven't had the
time to work on it and would appreciate anyone who does have the time.
13 years, 3 months