On Mon, Feb 20, 2012 at 12:28 PM, Clyde E. Kunkel
wrote:
>
> How do I get the numlock the turn off? (please don't tell me to press the
> NumLock key!! It doesn't work in rawhide right now. :-) )
>
> I tried numlockx off, but no effect.
I installed F17 (F17 Desktop Live CD) and Rawhide (F16 Desk
At https://fedoraproject.org/wiki/Features/Gnome_shell_software_rendering
I am reading "The standard Gnome 3 experience is now available on all
hardware". Is this a plan, a wish or this is supposedly describing the
current situation? I am asking because on my rawhide installation
(Radeon RV280 gr
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20120220
Next meeting is scheduled for 2012-02-27 at 1600 UTC in #fedora-meeting.
If you have topics you think we should bring up at the meeting, please
add them to the Wiki page at
https
Don't worry, they don't carry diseases.
I really just wanted to spread this news out a little more because it's
really cool stuff.
Thanks to Hongqing Yang and Kamil Paral, one of the long-term goals of
the AutoQA project is now a reality:
http://autoqa-stg.fedoraproject.org/resultsdb/frontend/se
Another quick F17 Alpha status update: we now have updates in for all
open blockers. However, the fix for the plymouth issue was to add it to
comps, and it takes a few hours for that change to be registered before
we can do a compose.
(All times in the following are PST). The compose should be hap
Loks like you don't have the 32 bit version of anaconda installed and that
is what revisor is looking for.
On Feb 20, 2012 7:04 PM, "Rob Healey" wrote:
> Greetings:
>
> I was trying to run Revisor, and it will not work. This is what I get on
> my terminal screen...
>
> [Frog@localhost /]$ reviso
On Mon, 2012-02-20 at 17:34 -0500, Samuel Greenfeld wrote:
> In my view, the big questions in that thread were (1) what are we
> trying to accomplish with a test day
This is always a key question to ask :)
> and (2) if we need to have test cases for test days in the first
> place.
As a point of
On Mon, 2012-02-20 at 16:56 -0500, Samuel Greenfeld wrote:
> I had a similar conversation on test cases while trying to plan for an
> upcoming test day:
>
> http://lists.laptop.org/pipermail/testing/2012-February/002609.html
>
> In general, it might be useful to know how skilled most test day
> p
On Mon, 2012-02-20 at 09:49 +, "Jóhann B. Guðmundsson" wrote:
> Needless to say now 6000+ components later we have no more how to debug
> or how to test pages then we did back then which makes it pretty evident
> that unless fesco/fpc make it mandatory you will be chasing your tail
> and ot
The following Fedora 17 Security updates need testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-1800/xulrunner-10.0.1-3.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-1794/thunderbird-10.0.1-2.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-1892/libpng-1
On Tue, 2012-02-21 at 00:11 +, "Jóhann B. Guðmundsson" wrote:
> On 02/20/2012 11:42 PM, Adam Williamson wrote:
> > I wish I had better background on it, but I'm pretty sure we did discuss
> > having an explicit criterion before going with the 'vague' paragraph
> > instead. All that mail (by me)
The following Fedora 15 Security updates need testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-1283/drupal6-6.24-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-0752/jetty-6.1.26-7.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-1250/drupal7-7.12-1.fc15
The following Fedora 16 Security updates need testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-0730/jetty-6.1.26-8.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1268/drupal7-7.12-1.fc16
https://admin.fedoraproject.org/updates/FEDORA-2012-1709/apr-1.4.6-1.fc16
Greetings:
I was trying to run Revisor, and it will not work. This is what I get on
my terminal screen...
[Frog@localhost /]$ revisor
Cannot find anaconda-runtime in /usr/lib/anaconda-runtime
And yet I know I have it installed...
[Frog@localhost /]$ whereis anaconda
anaconda: /sbin/anaconda /u
On 02/20/2012 10:34 PM, Samuel Greenfeld wrote:
In general I don't want to have test cases scattered all over the
place, as Sugar information already is found in at least three Wikis,
with developers only tending to update one or two.
(An interesting take on this can be seen in the opening s
On 02/20/2012 11:42 PM, Adam Williamson wrote:
I wish I had better background on it, but I'm pretty sure we did discuss
having an explicit criterion before going with the 'vague' paragraph
instead. All that mail (by me) says is that I didn't think a specific
criterion 'worked well', which is pret
On Mon, 20 Feb 2012 17:33:11 -0500
Jon Stanley wrote:
> No packages need to be installed, everything is right there in the
> install environment. In the window with the traceback, there's a
> 'debug' option that will drop you into PDB (I haven't looked at the
> code, but it probably calls pdb.pos
On Mon, 2012-02-20 at 20:59 +0100, drago01 wrote:
> We currently don't have any explicit criterion that mandates that
> keyboard layouts choose in the installer should work in the installed
> system.
> As a maintainer of one of the packages involved there
> (system-setup-keyboard) I see such bugs i
On 02/20/2012 10:34 PM, Samuel Greenfeld wrote:
In general I don't want to have test cases scattered all over the
place, as Sugar information already is found in at least three Wikis,
with developers only tending to update one or two.
The location of content for test days is irrelevant we ha
On Mon, Feb 20, 2012 at 17:43:33 -0500,
"Clyde E. Kunkel" wrote:
> On 02/20/2012 01:57 PM, Bruno Wolff III wrote:
> >On Mon, Feb 20, 2012 at 12:28:02 -0500,
> > "Clyde E. Kunkel" wrote:
> >>How do I get the numlock the turn off? (please don't tell me to
> >>press the NumLock key!! It doesn'
On 16 February 2012 21:42, Ian Pilcher wrote:
> Just kidding ... sort of.
>
> I'm willing to bet that I wouldn't be getting a "NameError: global name
> 'BRFSError' is not defined" traceback if it were. (BTRFSError anyone?)
>
Would writing it in pypy count :)?
--
Stephen J Smoogen.
"The core sk
On 02/20/2012 10:36 PM, Jon Stanley wrote:
I think that's a great idea - you wouldn't want someone who has never
seen a CLI attempting to set up an iSCSI initiator and target, for
example.
However the problem is that difficulty level is subjective. I find
compiling kernels extraordinarily easy -
> No packages need to be installed, everything is right there in the
> install environment. In the window with the traceback, there's a
> 'debug' option that will drop you into PDB (I haven't looked at the
> code, but it probably calls pdb.post_mortem() with the exception
> object). See http://docs
2012/2/20 "Jóhann B. Guðmundsson" :
> A while back I proposed having the test case structure split by
> experience/difficult levels.
I think that's a great idea - you wouldn't want someone who has never
seen a CLI attempting to set up an iSCSI initiator and target, for
example.
However the proble
In my view, the big questions in that thread were (1) what are we trying to
accomplish with a test day and (2) if we need to have test cases for test
days in the first place.
OLPC has a set of test cases in their Wiki, but's a bit stale, and the
current implementation makes them hard to go through
On Mon, Feb 20, 2012 at 5:21 PM, stan wrote:
> Can you expand on entering the debugger when a traceback occurs? What
> packages need to be installed? How is it invoked immediately after the
> traceback in order to pick up the failed job?
No packages need to be installed, everything is right th
On 02/20/2012 09:47 PM, Chris Lumens wrote:
anaconda does not do a constant rewrite every release cycle.
Atleast some parts of it like the UI other parts arguably not so much...
JBG
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listin
On Sun, 19 Feb 2012 22:56:25 -0500
Jon Stanley wrote:
> No, you'd instead get much less useful errors instead. Obviously this
> particular typo would never compile, but logic errors, instead of
> giving you a nice traceback (and the ability to enter a debugger
> straight from where the installer
On 02/20/2012 09:56 PM, Samuel Greenfeld wrote:
ng test day:
http://lists.laptop.org/pipermail/testing/2012-February/002609.html
In general, it might be useful to know how skilled most test day
participants are at testing, as well as the test approach preferred by
the Fedora project as a whol
I had a similar conversation on test cases while trying to plan for an
upcoming test day:
http://lists.laptop.org/pipermail/testing/2012-February/002609.html
In general, it might be useful to know how skilled most test day
participants are at testing, as well as the test approach preferred by the
2012/2/20 "Jóhann B. Guðmundsson" :
> On 02/20/2012 07:59 PM, drago01 wrote:
>>
>> As a maintainer of one of the packages involved there
>> (system-setup-keyboard) I see such bugs in basically every release,
>> during the development cycle.
>
>
> As one of the maintainer why does this have to break
> Is this due to Anaconda's constant rewrite every release cycle that
> this happens?
anaconda does not do a constant rewrite every release cycle.
- Chris
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On 02/20/2012 07:59 PM, drago01 wrote:
So I propose something like: "The keyboard layout selected in the
installer must be in use after rebooting the installer (plymouth and
X)".
Makes sense
ack...
JBG
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproje
On 02/20/2012 07:59 PM, drago01 wrote:
As a maintainer of one of the packages involved there
(system-setup-keyboard) I see such bugs in basically every release,
during the development cycle.
As one of the maintainer why does this have to break every release cycle?
Is this due to Anaconda's con
We currently don't have any explicit criterion that mandates that
keyboard layouts choose in the installer should work in the installed
system.
As a maintainer of one of the packages involved there
(system-setup-keyboard) I see such bugs in basically every release,
during the development cycle.
We
On Mon, Feb 20, 2012 at 12:28:02 -0500,
"Clyde E. Kunkel" wrote:
> How do I get the numlock the turn off? (please don't tell me to
> press the NumLock key!! It doesn't work in rawhide right now. :-) )
>
> I tried numlockx off, but no effect.
Have you seen a bug filed for this yet? I noticed
On 02/20/2012 05:14 PM, Petr Schindler wrote:
I've added test case [1] to [2].
[1]https://fedoraproject.org/wiki/QA:Testcase_Services_start
[2]https://fedoraproject.org/wiki/QA:Base_validation_results_template
You probably want to add to that an test that requires testers to check
for service
How do I get the numlock the turn off? (please don't tell me to press
the NumLock key!! It doesn't work in rawhide right now. :-) )
I tried numlockx off, but no effect.
TIA
--
Regards,
OldFart
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/m
I've added test case [1] to [2].
[1] https://fedoraproject.org/wiki/QA:Testcase_Services_start
[2] https://fedoraproject.org/wiki/QA:Base_validation_results_template
On Tue, 2012-01-31 at 07:23 -0500, Petr Schindler wrote:
> > From: "Adam Williamson"
> > To: "For testing and quality assurance of
The following Fedora 17 Security updates need testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-1800/xulrunner-10.0.1-3.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-1794/thunderbird-10.0.1-2.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-1892/libpng-1
On Tue, 2012-01-31 at 10:24 -0800, Adam Williamson wrote:
> > Thank you for suggestions on this. I would require only methods for
> > which we have test case [1] [2] and from alpha [3]. So I propose
> beta
> > criterion:
> >
> > "The installer must be able to use an [[Anaconda/Updates|installer
>
On Tue, 2012-01-31 at 12:01 -0800, Adam Williamson wrote:
> On Tue, 2012-01-31 at 11:42 -0500, Chris Lumens wrote:
> > > "The installer must be able to handle the failure and report the
> issue. The installer must be also able to access debug mode."
> >
> > Debug mode is intended to be used by dev
On Tue, 2012-01-31 at 12:00 -0800, Adam Williamson wrote:
> On Tue, 2012-01-31 at 11:43 -0500, Chris Lumens wrote:
> > > "The installed system must run normally if the user chooses to install
> > > without SELinux"
> > >
> > > There is no test case for this now.
> > >
> > > I have one note on th
Anaconda team wants to support upgrading by text interface [1], so
everything is fine and no changes have to be done here.
[1]
https://www.redhat.com/archives/anaconda-devel-list/2012-February/msg00032.html
On Fri, 2012-02-03 at 17:56 +0100, Petr Schindler wrote:
> I propose to change release lev
On Mon, 2012-02-13 at 14:23 +0100, Petr Schindler wrote:
> If you have some objection on this one, please, let me know till
> tomorrow, otherwise if there are no suggestions I'll make changes.
I've made changes. I've added new alpha and final release criterion to
[1] [2]. And I've changed release
I've added it to alpha criteria [1]. If this feature isn't working now,
we should test it and propose new blocker bug.
[1] https://fedoraproject.org/wiki/Fedora_17_Alpha_Release_Criteria
On Thu, 2012-02-16 at 09:28 -0800, Adam Williamson wrote:
> On Thu, 2012-02-16 at 14:45 +0100, Petr Schindler
Join us on irc.freenode.net in #fedora-meeting for this important
meeting, wherein we shall determine the readiness of the Alpha
taste-testing of the Beefy Miracle, better known as Fedora 17.
Wednesday, February 22, 2011 @22:00 UTC (17:00 EST/14:00 PST)
"Before each public release Development,
Hi,
I am Gaurav Kumar, I am 20 years old.My nick at irc.freenode.net is aavrug
I am using fedora since Fedora 13. Presently I am working on Transifex
which is written in python and i have also done Hindi translation for
Transifex,
beside that I also know Java, Django(Python WebFramework) and C/C+
Compose started at Mon Feb 20 08:15:08 UTC 2012
Broken deps for x86_64
--
[HippoDraw]
HippoDraw-devel-1.21.3-2.fc17.i686 requires python-numarray
HippoDraw-devel-1.21.3-2.fc17.x86_64 requires python-numarray
HippoDraw-
On 02/20/2012 04:19 AM, Jon Stanley wrote:
I had a conversation with Adam at FUDCon about things that might be
beneficial to QA that I could champion and make sure that it happened,
and provide regular status reports, the whole nine yards. What we came
up with is updating "How to debug" and "How
50 matches
Mail list logo
