On 11/01/2019, pmkel...@frontier.com wrote:
>> https://fedoraproject.org/wiki/QA:Testcase_base_shutdown/reboot
>>
>> Basically:
>>
>> 1. On a running system, change to a virtual console by pressing
>> Ctrl+Alt+F2
>> 2. At the virtual console, login as the root user
>> +3. Halt the system by r
On 1/10/19 6:33 PM, Sumantro Mukherjee wrote:
Hey All,
Tuesday 2019-01-15 will be Kernel 4.20 Test Day[0] Test Day! As Fedora 29
will be getting 4.20, we want to test it across all arcs and different
variants of F28 and F29.
So this is an important Test Day! Test Day will focus on testing the
On 11/01/2019, pmkel...@frontier.com wrote:
>
> On 1/11/19 7:26 AM, Alan Jenkins wrote:
>> Hi QA people!
>>
>> In the past few years I've seen four shutdown bugs. The problem is that
>> the screen turns off too quickly, so even if it shows error messages, most
>> people don't actually see them.
Thanks for these! They look good and the formatted tests will make adding
them a lot easier. I have opened an issue on the QA pagure page [0] and
will plan to bring this up at the next QA meeting. Please attend if you can
as your perspective will help us all make a decision!
[0] https://pagure.io/
On Fri, Jan 11, 2019 at 12:43 PM Adam Williamson
wrote:
> It would be useful to have the branch date / Bodhi activation point on
> the QA calendar, as that's an important date for us. It would similarly
> also be useful to have the Change deadlines on there.
>
That's an easy change. I'll add the
On 1/11/19 7:26 AM, Alan Jenkins wrote:
Hi QA people!
In the past few years I've seen four shutdown bugs. The problem is that the
screen turns off too quickly, so even if it shows error messages, most people
don't actually see them. Or at least, it requires extra effort if you want to
repo
On Fri, 2019-01-11 at 10:58 -0500, Ben Cotton wrote:
> I am beginning to prepare the schedule for Fedora 31. One thing I want
> to do is to make sure it still accurately reflects the work of
> different teams within Fedora. Please look at the tasks on your team's
> schedule [1] and discuss them in
I am beginning to prepare the schedule for Fedora 31. One thing I want
to do is to make sure it still accurately reflects the work of
different teams within Fedora. Please look at the tasks on your team's
schedule [1] and discuss them in your team. Let me know if there are
tasks that should be adde
Hi QA people!
In the past few years I've seen four shutdown bugs. The problem is that the
screen turns off too quickly, so even if it shows error messages, most people
don't actually see them. Or at least, it requires extra effort if you want to
report them.
At least three of the four shutdo
