Re: Proven Testers - Testing Protocols - Discussion Starter
On Wed, Jun 30, 2010 at 08:16:12PM -0400, Bob Lightfoot wrote: > 2. Open the VM with the GUI tool and perform System - Shutdown - Restart > > SYSTEM MUST REBOOT WITHOUT ERROR OR AVC DENIAL ** > In case of an error or avc denial -- report -1 karma against the > offending package > It may be necessary to fresh install and install updates-testing > on at a time to find offender Actually the -1 karma is only justified if the avc denial does not exist for the stable version of the package. Also it is helpful to also open a bug report against selinux-policy in this case and provide the bug number in the feedback comment. > 3. Open terminal and run yum list installed | grep updates-testing >> > packs-to-test-$(Date) > > 4. In First Terminal nano packs-to-test-$(DATE) > > 5. Test the application for any package you readily recognize and add # > -1/0/+1 comment before the package in packs-to-test-$(DATE) Why do you do these steps? I would just run fedora-easy-karma, test the packages in the order f-e-k suggests, skip packages one does not want to test and as soon as a test is finished, select the karma and comment in f-ek. A big disadvantage of step 3 is, that it will not filter out updates that have already been tested by you. But in case you want the file from step 3 for documentation purposes, you might want to use "$(date -I)" to get a string like 2010-07-03 directly by the shell. Regards Till pgpIdFMPUx0q1.pgp Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
RE: Proven Testers - Testing Protocols - Discussion Starter - Answer to Hurry (Adam Miller)
Hi Bob, Below is a very good guidance on how to obtain and use your personal space on fedorapeople.org : http://fedoraproject.org/wiki/Infrastructure/fedorapeople.org Please refer to it. And I'll forward and discuss your script with Adam on another thread. Thanks, Hurry On Thu, 2010-07-01 at 19:39 -0400, Bob Lightfoot wrote: > Adam - I;m having issues with my fedorapeoplespace right now. But I > emailed you the script under seperate cover. You and Hurry can figure > out how it needs to be sanitized and formatted for public release and do > so with my blessing. > > BobLfoot -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
RE: Proven Testers - Testing Protocols - Discussion Starter - Answer to Hurry (Adam Miller)
Adam - I;m having issues with my fedorapeoplespace right now. But I emailed you the script under seperate cover. You and Hurry can figure out how it needs to be sanitized and formatted for public release and do so with my blessing. BobLfoot -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proven Testers - Testing Protocols - Discussion Starter - Answer to Hurry
Is there any way we might be able to get our hands on that script? Would you mind uploading it to your fedorapeople space or $other for public consumption? -AdamM (From Android) On Jul 1, 2010 8:30 AM, "Bob Lightfoot" wrote: Hurry - yes I wrote the script vmsupdate.sh and it updates all six VM's when run from a terminal on the host. I've sent the script to you in a seperate email. It will work with 3.1.8 I know. I think 3.2 changes the syntax for port forwarding so it'll need a rewrite/mod but nothing major. Bob Lightfoot -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Proven Testers - Testing Protocols - Discussion Starter - Answer to Hurry
Hurry - yes I wrote the script vmsupdate.sh and it updates all six VM's when run from a terminal on the host. I've sent the script to you in a seperate email. It will work with 3.1.8 I know. I think 3.2 changes the syntax for port forwarding so it'll need a rewrite/mod but nothing major. Bob Lightfoot -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proven Testers - Testing Protocols - Discussion Starter
Clear steps, well done.
On Wed, 2010-06-30 at 20:16 -0400, Bob Lightfoot wrote:
> Dear Test Community:
> Being in the queue for Proven-Tester status and waiting for a
> mentor I am spending my time testing packages as they reach
> updates-testing. I thought I'd share for discussion the protocol I
> am
> using when I have a test night. Keep in mind I wrote this for my use
> on
> a Host System with 6 VMs {2-F12; 2-F13 and 2-F14 when released}, but
> I
> think portions will have broader applications.
>
> *
> # Steps used to provide karma for updates-testing releases
>
> 1. run ./vmsupdate.sh and install all updates from updates-testing
> into
> all VMs
>
>
I'm curious about vmsupdate.sh. Did you write this file yourself so that
all virt guests will install updates once you run it on the host?
Thanks,
Hurry
--
Contacts
Hurry
FAS Name: Rhe
Timezone: UTC+8
TEL: 86-010-62608141
IRC nick: rhe #fedora-qa #fedora-zh
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Proven Testers - Testing Protocols - Discussion Starter
Dear Test Community:
Being in the queue for Proven-Tester status and waiting for a
mentor I am spending my time testing packages as they reach
updates-testing. I thought I'd share for discussion the protocol I am
using when I have a test night. Keep in mind I wrote this for my use on
a Host System with 6 VMs {2-F12; 2-F13 and 2-F14 when released}, but I
think portions will have broader applications.
*
# Steps used to provide karma for updates-testing releases
1. run ./vmsupdate.sh and install all updates from updates-testing into
all VMs
# Apply the following to each VM once the script concludes
2. Open the VM with the GUI tool and perform System - Shutdown - Restart
SYSTEM MUST REBOOT WITHOUT ERROR OR AVC DENIAL **
In case of an error or avc denial -- report -1 karma against the
offending package
It may be necessary to fresh install and install updates-testing
on at a time to find offender
3. Open terminal and run yum list installed | grep updates-testing >>
packs-to-test-$(Date)
4. In First Terminal nano packs-to-test-$(DATE)
5. Test the application for any package you readily recognize and add #
-1/0/+1 comment before the package in packs-to-test-$(DATE)
6. For packages you don't readily recognize in Second Terminal run
command repoquery --alldeps --whatrequires packagename
7. Test an application related to the package and add # -1/0/+1 comment
before the package in packs-to-test-$DATE
8. You may decide not to test a package in item 5 or 7 due to time or
unfamiliarity this is OK. Volunteer Help and Testing is appreciated
where you can.
9. When all package tests are complete save packs-to-test-$(DATE) and
in Second Terminal run su -c "fedora-easy-karma"
10. You can CTRL-ALT-ARROW between terminals to get your logged tests
results to input to fedora-easy-karma
11. Close the WM and proceed to the next test bed.
**
Hope this is a starting point and yes I welcome suggestions to make me a
better tester,
Bob Lightfoot - boblfoot
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
