Re: Testcase Audio Recording Basic (new test case proposal)

[Kamil Paral]

On Fri, Jan 22, 2021 at 8:00 AM Kamil Paral  wrote:

> Your reaction is the tribalism I was talking about, negatively reacting to
> anything that has "GNOME" or "K" in the name.
>

As an exercise, imagine the application is not called the GNOME Sound
Recorder, but a Fred's Sound Recorder instead. I don't think we'd be having
this conversation at all, in that case.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Kamil Paral]

On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa  wrote:

> GNOME applications pull in most of the GNOME desktop as dependencies.
> Properly developed KDE applications will pull in the KF5 libraries and
> occasionally some Plasma libraries. That's just how it goes. It is
> also unrealistic to expect GNOME applications to work fully "to spec"
> on KDE because KDE does not provide all the D-Bus interfaces and
> services that GNOME does. We can and do have quirks when applications
> are transplanted from one desktop environment to another, if the
> underlying frameworks don't handle this well. While most of the KDE
> frameworks adapt well to a non-KDE environment, it's rare that GNOME
> applications fully do, especially ones that depend on things like
> gnome-settings-daemon, gnome-shell, or gnome-control-center. In the
> case of gnome-sound-recorder, it'll be fine as it's quite simple. But
> if you were using something like the GNOME screencast app, that would
> fail in KDE. Note that I'm specifically saying "GNOME applications".
> Plain GTK applications are generally fine on Plasma.
>

Neal, you're doing a great job in Fedora, but this made me somewhat angry.
Because I *did* spend the time yesterday, installed KDE in a VM from
scratch, and tested gnome-sound-recorder, audacity and kwave in it. And
sounds like you haven't. Gnome-sound-recorder only pulls in gjs and
libhand1, and that's *all*. It's the most minimal application I could find.
I also tested its functionality, it worked without issues. I stand by my
opinion that this is the best sound recorder to recommend. Your reaction is
the tribalism I was talking about, negatively reacting to anything that has
"GNOME" or "K" in the name.

Audacity is OK, but it's UI is quite old, it crashes every time I close it,
and it pulls more dependencies (11 more packages in KDE). It's a decent
fallback option, but I wouldn't recommend it as the first one.

KWave pulls a zillion packages on GNOME systems (over 50 packages) and it's
UI is the worst of the three, at least from a beginner perspective.


>
> If you want to endorse a cross-desktop tool for testing, I would
> suggest Audacity. It's simple, powerful, and known to work on all
> desktops. It also standardizes the test and minimizes the variables
> for validation.
>

Sigh, this is just a testcase. We don't "endorse" it or place it anywhere
visible. It's just a hint for anyone helping us test releases (which is our
core QA team plus a handful more people from time to time; at most this
will be read by 20 people during a testday) to be aware of a small and
simple application to record sound, in case they don't know any.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora-IoT-33-20210121.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 3/15 (aarch64)

New failures (same test not failed in Fedora-IoT-33-20210113.0):

ID: 759803  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/759803
ID: 759814  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi
URL: https://openqa.fedoraproject.org/tests/759814

Old failures (same test failed in Fedora-IoT-33-20210113.0):

ID: 759801  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/759801

Soft failed openQA tests: 1/16 (x86_64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-33-20210113.0):

ID: 759785  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/759785

Passed openQA tests: 15/16 (x86_64), 12/15 (aarch64)

New passes (same test not passed in Fedora-IoT-33-20210113.0):

ID: 759799  Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/759799
ID: 759815  Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/759815
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: [External] Re: Respins for OEM preloads

[Adam Williamson]

On Thu, 2021-01-21 at 15:41 -0500, Mark Pearson wrote:
> 
> On 21/01/2021 14:31, Adam Williamson wrote:
> > On Thu, 2021-01-21 at 11:42 -0500, Mohan Boddu wrote:
> > > On Thu, Jan 21, 2021 at 11:06 AM Mark Pearson  
> > > wrote:
> > > > 
> > > > 
> > > > On 21/01/2021 10:46, Mohan Boddu wrote:
> > > > > On Wed, Jan 20, 2021 at 3:30 PM Adam Williamson
> > > > >  wrote:
> > > > > > 
> > > > > > Yeah, I don't think that should be really tricky for anyone. I'd
> > > > > > suggest we just run it as a post-release nightly compose rather 
> > > > > > than a
> > > > > > candidate and don't give it any kind of label. I don't think it 
> > > > > > should
> > > > > > be hard for releng to run that,
> > > > > 
> > > > > Yes, RelEng can create a live media with updates repo included, it
> > > > > wont be a huge deal and we can sign the checksums manually making it
> > > > > official. But I notice that the cadence hasn't been finalized yet, I
> > > > > would really appreciate if we know how often do we have to run this, I
> > > > > understand it is subjected to change, but having a schedule really
> > > > > helps.
> > > > > 
> > > > From Lenovo perspective we'd like the image now (or next week) ready for
> > > > the 2021 Carbon. If there was a blocker issue then running it again
> > > > would be useful (but so far test results are good and I'll know in the
> > > > next couple week(ish) if there are any red flags.
> > > 
> > > I will start building an image asap, expect something by the end of
> > > the day today (hopefully).
> > 
> > So the image is built now:
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=60156482
> > 
> > I ran the openQA tests on it:
> > https://openqa.fedoraproject.org/tests/overview?build=Fedora-33-Lenovo-20210121.n.0-NOREPORT=33=fedora=1
> > 
> > there were a few failures that all basically related to the GNOME top
> > bar and/or notifications. I'm re-running the tests, and will also
> > download the ISO and poke it a bit locally.
> > 
> Wow - thank you!
> 
> I've grabbed it and it looks good so far, we'll start kicking the tires
> on it and let you know if we find any issues.

The failures are...odd. This is what they seem to have in common:
they're all in tests where we try to open something from the top bar
after a while. For the desktop notifications tests we click where the
time is, to open the notifications panel. For the switch_user test
we're trying to click the top-right menu.

In all three cases, it seems like the click just doesn't do anything.
I've re-run all the tests and they failed again the same way second
time, so it doesn't *just* seem like a blip.

I'm currently downloading the ISO to test locally and see if I can
reproduce this sort of behaviour...
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: [External] Re: Respins for OEM preloads

[Mark Pearson]

On 21/01/2021 14:31, Adam Williamson wrote:
> On Thu, 2021-01-21 at 11:42 -0500, Mohan Boddu wrote:
>> On Thu, Jan 21, 2021 at 11:06 AM Mark Pearson  wrote:
>>>
>>>
>>> On 21/01/2021 10:46, Mohan Boddu wrote:
>>>> On Wed, Jan 20, 2021 at 3:30 PM Adam Williamson
>>>>  wrote:
>>>>>
>>>>> Yeah, I don't think that should be really tricky for anyone. I'd
>>>>> suggest we just run it as a post-release nightly compose rather than a
>>>>> candidate and don't give it any kind of label. I don't think it should
>>>>> be hard for releng to run that,
>>>>
>>>> Yes, RelEng can create a live media with updates repo included, it
>>>> wont be a huge deal and we can sign the checksums manually making it
>>>> official. But I notice that the cadence hasn't been finalized yet, I
>>>> would really appreciate if we know how often do we have to run this, I
>>>> understand it is subjected to change, but having a schedule really
>>>> helps.
>>>>
>>> From Lenovo perspective we'd like the image now (or next week) ready for
>>> the 2021 Carbon. If there was a blocker issue then running it again
>>> would be useful (but so far test results are good and I'll know in the
>>> next couple week(ish) if there are any red flags.
>>
>> I will start building an image asap, expect something by the end of
>> the day today (hopefully).
> 
> So the image is built now:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=60156482
> 
> I ran the openQA tests on it:
> https://openqa.fedoraproject.org/tests/overview?build=Fedora-33-Lenovo-20210121.n.0-NOREPORT=33=fedora=1
> 
> there were a few failures that all basically related to the GNOME top
> bar and/or notifications. I'm re-running the tests, and will also
> download the ISO and poke it a bit locally.
> 
Wow - thank you!

I've grabbed it and it looks good so far, we'll start kicking the tires
on it and let you know if we find any issues.

Mark
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Brandon Nielsen]

On 1/21/21 6:01 AM, Neal Gompa wrote:
On Thu, Jan 21, 2021 at 6:59 AM Lukas Ruzicka > wrote:




On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa mailto:ngomp...@gmail.com>> wrote:

On Thu, Jan 21, 2021 at 6:15 AM Kamil Paral mailto:kpa...@redhat.com>> wrote:
 >
 > On Thu, Jan 21, 2021 at 11:24 AM Lukas Ruzicka
mailto:lruzi...@redhat.com>> wrote:
 >>
 >>
 >> On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka
mailto:lruzi...@redhat.com>> wrote:
 
  Have you tested whether gnome-sound-recorder works well in
KDE and optionally also other desktops? If not (or if it pulls
too many dependencies), it would be good to suggest an
alternative tool as well.
 >>
 >>
 >

If you want to endorse a cross-desktop tool for testing, I would
suggest Audacity. It's simple, powerful, and known to work on all
desktops. It also standardizes the test and minimizes the variables
for validation.



Ok, let's make it Audacity.

The corrected text now looks:

Install any sound recording application you're familiar with. If
you've never worked with any, *Audacity* (the |audacity| package) is
a popular full-featured audio editor which can also easily capture
sound from your microphone.



Works for me!



I love Audacity, but it feels a little unloved on Fedora[0]. I have had 
issues with 2.3.3 (the currently packaged version) crashing[1].


[0] - https://bugzilla.redhat.com/show_bug.cgi?id=1836497
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1873051
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: [External] Re: Respins for OEM preloads

[Adam Williamson]

On Thu, 2021-01-21 at 11:42 -0500, Mohan Boddu wrote:
> On Thu, Jan 21, 2021 at 11:06 AM Mark Pearson  wrote:
> > 
> > 
> > On 21/01/2021 10:46, Mohan Boddu wrote:
> > > On Wed, Jan 20, 2021 at 3:30 PM Adam Williamson
> > >  wrote:
> > > > 
> > > > Yeah, I don't think that should be really tricky for anyone. I'd
> > > > suggest we just run it as a post-release nightly compose rather than a
> > > > candidate and don't give it any kind of label. I don't think it should
> > > > be hard for releng to run that,
> > > 
> > > Yes, RelEng can create a live media with updates repo included, it
> > > wont be a huge deal and we can sign the checksums manually making it
> > > official. But I notice that the cadence hasn't been finalized yet, I
> > > would really appreciate if we know how often do we have to run this, I
> > > understand it is subjected to change, but having a schedule really
> > > helps.
> > > 
> > From Lenovo perspective we'd like the image now (or next week) ready for
> > the 2021 Carbon. If there was a blocker issue then running it again
> > would be useful (but so far test results are good and I'll know in the
> > next couple week(ish) if there are any red flags.
> 
> I will start building an image asap, expect something by the end of
> the day today (hopefully).

So the image is built now:
https://koji.fedoraproject.org/koji/taskinfo?taskID=60156482

I ran the openQA tests on it:
https://openqa.fedoraproject.org/tests/overview?build=Fedora-33-Lenovo-20210121.n.0-NOREPORT=33=fedora=1

there were a few failures that all basically related to the GNOME top
bar and/or notifications. I'm re-running the tests, and will also
download the ISO and poke it a bit locally.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora-IoT-34-20210121.0 compose check report

[Fedora compose checker]

Missing expected images:

Iot dvd aarch64
Iot dvd x86_64

Failed openQA tests: 4/15 (aarch64), 1/16 (x86_64)

New failures (same test not failed in Fedora-IoT-34-20210119.0):

ID: 759750  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/759750
ID: 759754  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi
URL: https://openqa.fedoraproject.org/tests/759754

Old failures (same test failed in Fedora-IoT-34-20210119.0):

ID: 759736  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/759736
ID: 759752  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/759752
ID: 759755  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/759755

Soft failed openQA tests: 1/16 (x86_64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-34-20210119.0):

ID: 759733  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/759733

Passed openQA tests: 14/16 (x86_64), 11/15 (aarch64)

Installed system changes in test aarch64 IoT-dvd_ostree-iso 
install_default_upload@uefi: 
System load changed from 0.32 to 0.19
Previous test data: https://openqa.fedoraproject.org/tests/758723#downloads
Current test data: https://openqa.fedoraproject.org/tests/759749#downloads
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora-Rawhide-20210120.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Minimal raw-xz armhfp
Xfce raw-xz armhfp

Compose FAILS proposed Rawhide gating check!
5 of 43 required tests failed, 8 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 21/180 (x86_64), 14/122 (aarch64)

New failures (same test not failed in Fedora-Rawhide-20210118.n.1):

ID: 759419  Test: x86_64 Silverblue-dvd_ostree-iso desktop_terminal
URL: https://openqa.fedoraproject.org/tests/759419
ID: 759456  Test: aarch64 Server-dvd-iso install_vncconnect_server@uefi
URL: https://openqa.fedoraproject.org/tests/759456
ID: 759489  Test: aarch64 Workstation-raw_xz-raw.xz desktop_terminal@uefi
URL: https://openqa.fedoraproject.org/tests/759489
ID: 759507  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/759507
ID: 759539  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/759539
ID: 759604  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/759604
ID: 759615  Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/759615
ID: 759630  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/759630
ID: 759638  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/759638
ID: 759646  Test: x86_64 Workstation-live-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/759646
ID: 759647  Test: x86_64 Workstation-live-iso install_default_upload 
**GATING**
URL: https://openqa.fedoraproject.org/tests/759647

Old failures (same test failed in Fedora-Rawhide-20210118.n.1):

ID: 759345  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/759345
ID: 759357  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/759357
ID: 759365  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/759365
ID: 759394  Test: x86_64 KDE-live-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/759394
ID: 759396  Test: x86_64 KDE-live-iso install_no_user **GATING**
URL: https://openqa.fedoraproject.org/tests/759396
ID: 759397  Test: x86_64 KDE-live-iso install_default_upload **GATING**
URL: https://openqa.fedoraproject.org/tests/759397
ID: 759468  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/759468
ID: 759477  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/759477
ID: 759478  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/759478
ID: 759523  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/759523
ID: 759524  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/759524
ID: 759537  Test: x86_64 universal upgrade_2_minimal_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/759537
ID: 759538  Test: x86_64 universal upgrade_2_realmd_client
URL: https://openqa.fedoraproject.org/tests/759538
ID: 759545  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/759545
ID: 759558  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/759558
ID: 759563  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/759563
ID: 759568  Test: x86_64 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/759568
ID: 759576  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/759576
ID: 759577  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/759577
ID: 759595  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/759595
ID: 759617  Test: aarch64 universal install_cyrillic_language@uefi
URL: https://openqa.fedoraproject.org/tests/759617
ID: 759618  Test: aarch64 universal upgrade_2_server_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/759618
ID: 759619  Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/759619
ID: 759626  Test: aarch64 universal upgrade_2_minimal_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/759626

Soft failed openQA tests: 6/180 (x86_64), 3/122 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Rawhide-20210118.n.1):

ID: 759332  Test: 

Re: [External] Re: Respins for OEM preloads

[Mohan Boddu]

On Thu, Jan 21, 2021 at 11:06 AM Mark Pearson  wrote:
>
>
> On 21/01/2021 10:46, Mohan Boddu wrote:
> > On Wed, Jan 20, 2021 at 3:30 PM Adam Williamson
> >  wrote:
> >>
> >> Yeah, I don't think that should be really tricky for anyone. I'd
> >> suggest we just run it as a post-release nightly compose rather than a
> >> candidate and don't give it any kind of label. I don't think it should
> >> be hard for releng to run that,
> >
> > Yes, RelEng can create a live media with updates repo included, it
> > wont be a huge deal and we can sign the checksums manually making it
> > official. But I notice that the cadence hasn't been finalized yet, I
> > would really appreciate if we know how often do we have to run this, I
> > understand it is subjected to change, but having a schedule really
> > helps.
> >
> From Lenovo perspective we'd like the image now (or next week) ready for
> the 2021 Carbon. If there was a blocker issue then running it again
> would be useful (but so far test results are good and I'll know in the
> next couple week(ish) if there are any red flags.

I will start building an image asap, expect something by the end of
the day today (hopefully).

>
> We have some other platforms that come out later in the year with Fedora
> - around the end of the summer. Last year because of various things it
> worked out really well that we were ready for testing just as F33
> released so we of course used that. I'm focusing right now on improving
> how we get our releases out much more quickly (now I know where many of
> the issues lie) so I'm not sure everything will line up quite as well,
> and that's probably worthy of discussion. Is it better to have the new
> Fedora out but a later release of a platform? Or earlier HW with older
> Fedora? Generally the biggest criticisms I get are cost (whether I have
> no control over) and release dates after Windows (where we have sucked
> and I have lots of scope for improvement).
>
> Sorry - long answer to say "once or at worst twice a year"

Thank you very much Mark, once or twice a year is gonna be fine for us.

>
> >> and I should be able to run openQA
> >> tests and even create a validation event if necessary, I might need to
> >> metaphorically whang a few things with a hammer because it won't quite
> >> fit the normal flows but it shouldn't be a big deal.
> >>
> >> Also, I forgot to mention it'll obviously be completely impossible for
> >> this to work without Lenovo shipping me some hardware for,
> >> uh...testing. Yup. That's definitely non-negotiable. Two of everything.
> >> :D
> >
> > I hope one of them is for RelEng or else it will be three of everything :D
> I have noted the request ;)

Hehe :)

>
> Mark
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora rawhide compose report: 20210120.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20210118.n.1
NEW: Fedora-Rawhide-20210120.n.0

= SUMMARY =
Added images:11
Dropped images:  1
Added packages:  10
Dropped packages:211
Upgraded packages:   140
Downgraded packages: 0

Size of added packages:  177.06 MiB
Size of dropped packages:65.69 MiB
Size of upgraded packages:   8.07 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   72.97 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: KDE_Appliance raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-armhfp-Rawhide-20210120.n.0-sda.raw.xz
Image: Scientific vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20210120.n.0.x86_64.vagrant-virtualbox.box
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-Rawhide-20210120.n.0.aarch64.raw.xz
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20210120.n.0.ppc64le.qcow2
Image: Design_suite live x86_64
Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-Rawhide-20210120.n.0.iso
Image: Scientific vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20210120.n.0.x86_64.vagrant-libvirt.box
Image: LXDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-LXDE-armhfp-Rawhide-20210120.n.0-sda.raw.xz
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20210120.n.0.ppc64le.raw.xz
Image: Container_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Base-Rawhide-20210120.n.0.ppc64le.tar.xz
Image: Minimal raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Minimal-Rawhide-20210120.n.0.aarch64.raw.xz
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20210120.n.0.ppc64le.tar.xz

= DROPPED IMAGES =
Image: Workstation_Appliance raw-xz armhfp
Path: 
Workstation/armhfp/images/Fedora-Workstation-armhfp-Rawhide-20210118.n.1-sda.raw.xz

= ADDED PACKAGES =
Package: golang-github-bep-godartsass-0.11.0-1.fc34
Summary: Go API backed by the native Dart Sass Embedded executable
RPMs:golang-github-bep-godartsass-devel
Size:39.19 KiB

Package: golang-github-cli-safeexec-1.0.0-1.fc34
Summary: A safer version of exec.LookPath on Windows
RPMs:golang-github-cli-safeexec-devel
Size:12.09 KiB

Package: golang-github-evanw-esbuild-0.8.20-0.8.20-1.fc34
Summary: Fast JavaScript bundler and minifier
RPMs:golang-github-evanw-esbuild-0.8.20-devel
Size:404.19 KiB

Package: golang-github-fujiwara-shapeio-0-0.1.20210119gitc073257.fc34
Summary: Traffic shaper for Golang io.Reader and io.Writer
RPMs:golang-github-fujiwara-shapeio-devel
Size:11.20 KiB

Package: golang-github-paulmach-protoscan-0.2.0-1.fc34
Summary: Low-level reader for protobuf data
RPMs:golang-github-paulmach-protoscan-devel
Size:27.91 KiB

Package: ocaml-graphics-5.1.0-1.fc34
Summary: Portable drawing primitives for OCaml
RPMs:ocaml-graphics ocaml-graphics-devel
Size:1.21 MiB

Package: pgaudit-1.4.0-3.module_f34+11060+94930af7
Summary: PostgreSQL Audit Extension
RPMs:pgaudit
Size:281.83 KiB

Package: postgres-decoderbufs-1.4.0-1.Final.module_f34+11060+94930af7
Summary: PostgreSQL Protocol Buffers logical decoder plugin
RPMs:postgres-decoderbufs postgres-decoderbufs-llvmjit
Size:306.86 KiB

Package: postgresql-12.5-1.module_f34+11060+94930af7
Summary: PostgreSQL client programs
RPMs:postgresql postgresql-contrib postgresql-docs postgresql-llvmjit 
postgresql-plperl postgresql-plpython postgresql-plpython3 postgresql-pltcl 
postgresql-server postgresql-server-devel postgresql-static postgresql-test 
postgresql-test-rpm-macros postgresql-upgrade postgresql-upgrade-devel
Size:174.77 MiB

Package: python-sphinx_lv2_theme-1.0.0-2.fc34
Summary: A minimal pure-CSS theme for Sphinx
RPMs:python3-sphinx_lv2_theme
Size:25.27 KiB


= DROPPED PACKAGES =
Package: ekiga-4.0.1-50.fc33
Summary: A Gnome based SIP/H323 teleconferencing application
RPMs:ekiga
Size:40.52 MiB

Package: nodejs-acorn-dynamic-import-3.0.0-6.fc33
Summary: Support dynamic imports in acorn
RPMs:nodejs-acorn-dynamic-import
Size:12.19 KiB

Package: nodejs-amdefine-0.0.4-14.fc33
Summary: Provide AMD's define() API for declaring modules in the AMD format
RPMs:nodejs-amdefine
Size:13.97 KiB

Package: nodejs-ansicolors-0.3.2-14.fc33
Summary: Functions that surround a string with ansi color codes so it prints in 
color
RPMs:nodejs-ansicolors
Size:10.36 KiB

Package: nodejs-any-promise-1.3.0-7.fc32
Summary: Resolve any installed ES6 compatible promise
RPMs:nodejs-any-promise
Size:14.14 KiB

Package: nodejs-append-transform-0.4.0-9.fc33
Summary: Install a transform to `require.extensions` that always runs last
RPMs:nodejs-append-transform
Size:11.98 KiB

Package: nodejs-array-buffer-from-string-0.1.0-7.fc33
Summary: Create an ArrayBuffer with the [raw 

Re: [External] Re: Respins for OEM preloads

[Mark Pearson]

On 21/01/2021 10:46, Mohan Boddu wrote:
> On Wed, Jan 20, 2021 at 3:30 PM Adam Williamson
>  wrote:
>>
>> Yeah, I don't think that should be really tricky for anyone. I'd
>> suggest we just run it as a post-release nightly compose rather than a
>> candidate and don't give it any kind of label. I don't think it should
>> be hard for releng to run that,
> 
> Yes, RelEng can create a live media with updates repo included, it
> wont be a huge deal and we can sign the checksums manually making it
> official. But I notice that the cadence hasn't been finalized yet, I
> would really appreciate if we know how often do we have to run this, I
> understand it is subjected to change, but having a schedule really
> helps.
> 
From Lenovo perspective we'd like the image now (or next week) ready for
the 2021 Carbon. If there was a blocker issue then running it again
would be useful (but so far test results are good and I'll know in the
next couple week(ish) if there are any red flags.

We have some other platforms that come out later in the year with Fedora
- around the end of the summer. Last year because of various things it
worked out really well that we were ready for testing just as F33
released so we of course used that. I'm focusing right now on improving
how we get our releases out much more quickly (now I know where many of
the issues lie) so I'm not sure everything will line up quite as well,
and that's probably worthy of discussion. Is it better to have the new
Fedora out but a later release of a platform? Or earlier HW with older
Fedora? Generally the biggest criticisms I get are cost (whether I have
no control over) and release dates after Windows (where we have sucked
and I have lots of scope for improvement).

Sorry - long answer to say "once or at worst twice a year"

>> and I should be able to run openQA
>> tests and even create a validation event if necessary, I might need to
>> metaphorically whang a few things with a hammer because it won't quite
>> fit the normal flows but it shouldn't be a big deal.
>>
>> Also, I forgot to mention it'll obviously be completely impossible for
>> this to work without Lenovo shipping me some hardware for,
>> uh...testing. Yup. That's definitely non-negotiable. Two of everything.
>> :D
> 
> I hope one of them is for RelEng or else it will be three of everything :D
I have noted the request ;)

Mark
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Respins for OEM preloads

[Mohan Boddu]

On Wed, Jan 20, 2021 at 3:30 PM Adam Williamson
 wrote:
>
> Yeah, I don't think that should be really tricky for anyone. I'd
> suggest we just run it as a post-release nightly compose rather than a
> candidate and don't give it any kind of label. I don't think it should
> be hard for releng to run that,

Yes, RelEng can create a live media with updates repo included, it
wont be a huge deal and we can sign the checksums manually making it
official. But I notice that the cadence hasn't been finalized yet, I
would really appreciate if we know how often do we have to run this, I
understand it is subjected to change, but having a schedule really
helps.

> and I should be able to run openQA
> tests and even create a validation event if necessary, I might need to
> metaphorically whang a few things with a hammer because it won't quite
> fit the normal flows but it shouldn't be a big deal.
>
> Also, I forgot to mention it'll obviously be completely impossible for
> this to work without Lenovo shipping me some hardware for,
> uh...testing. Yup. That's definitely non-negotiable. Two of everything.
> :D

I hope one of them is for RelEng or else it will be three of everything :D

> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Proposal to modify: Working Sound Beta Release Criterion

[Lukas Ruzicka]

Hello friends of Fedora,

I have been thinking about a proposal to modify the %subj. I have tried
several version and I did not like any, so finally I am proposing this text:

*Working sound*

*The installed system must be able to play back and record audio.*

This is a very short and general version, but I believe it supports the
following:

   1. Playback and recording must work (which we want)
   2. You can test on any application you like (The recording test case
   will recommend Audacity)
   3. It does not say that all applications must work, so we should be fine
   if *some do*

What do you think?

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Self-Introduction: Ben Klepzig

[Alessio]

On Mon, 2021-01-11 at 20:32 +, Ben Klepzig wrote:
> Hello everyone,

Hello Ben. Sorry for the late reply.

I just sponsored you in the QA team.


This list will get updates on different testing related activities and
updates from time to time.

You can start to test updates in [http://bodhi.fedoraproject.org/] for
Fedora 32 and Fedora 33.
Update testing is where a tester tests a package and gives out a +1
Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora
Releases and tags viz "pending" & "testing". You can read much about
update testing here [1]. You can also use the RPM package fedora-easy-
karma for giving out feedbacks from the command line for the installed
packages (enable the updates-testing repository!).

Running release validation tests [2] [3] on Rawhide could be also
useful.

We usually involve ourselves in activities marked in [4], you can catch
us mostly at #fedora-qa on freenode IRC or Telegram.

If you have any question, please ask!

[0]
https://communityblog.fedoraproject.org/contribute-at-the-fedora-test-week-for-kernel-5-10/
[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2] https://fedoramagazine.org/release-validation-testing-fedora/
[3] https://fedoraproject.org/wiki/Test_Results:Current_Summary
[4] https://fedoraproject.org/wiki/QA#Activities


Ciao,
A.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction Amanda Cavalcante

[Lukas Ruzicka]

> You can start to test updates in [http://bodhi.fedoraproject.org/] for
> Fedora 32 and Fedora 33.
> Update testing is where a tester tests a package and gives out a +1
> Karma for PASS and -1 Karma for FAIL. You can go to
> bodhi.fedoraproject.org where you can sort the packages with Fedora
> Releases and tags viz "pending" & "testing". You can read much about
> update testing here [1]. You can also use the RPM package fedora-easy-
> karma for giving out feedbacks from the command line for the installed
> packages (enable the updates-testing repository!).
>

Yes, I agree this is very useful. However, for the start, I recommend you
only focus on things that you really do use on Linux to see how that works
and then you can explore more.



>
> Running release validation tests [2] [3] on Rawhide could be also
> useful.
>

Validation testing is where I would recommend to start completely, because
we have nice test cases written step by step, so first you will be guided
and helped through things and second, you will learn a lot about Linux
itself.

If I could be of any help to you - explanations, help, guidance ...  feel
free to drop a line.

Lukas



>
> We usually involve ourselves in activities marked in [4], you can catch
> us mostly at #fedora-qa on freenode IRC or Telegram.
>
> If you have any question, please ask!
>
> [0]
>
> https://communityblog.fedoraproject.org/contribute-at-the-fedora-test-week-for-kernel-5-10/
> [1] https://fedoraproject.org/wiki/QA:Updates_Testing
> [2] https://fedoramagazine.org/release-validation-testing-fedora/
> [3] https://fedoraproject.org/wiki/Test_Results:Current_Summary
> [4] https://fedoraproject.org/wiki/QA#Activities
>
>
> Ciao,
> A.
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Neal Gompa]

On Thu, Jan 21, 2021 at 6:59 AM Lukas Ruzicka  wrote:

>
>
> On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa  wrote:
>
>> On Thu, Jan 21, 2021 at 6:15 AM Kamil Paral  wrote:
>> >
>> > On Thu, Jan 21, 2021 at 11:24 AM Lukas Ruzicka 
>> wrote:
>> >>
>> >>
>> >> On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka 
>> wrote:
>> 
>>  Have you tested whether gnome-sound-recorder works well in KDE and
>> optionally also other desktops? If not (or if it pulls too many
>> dependencies), it would be good to suggest an alternative tool as well.
>> >>
>> >>
>> >
>>
>> If you want to endorse a cross-desktop tool for testing, I would
>> suggest Audacity. It's simple, powerful, and known to work on all
>> desktops. It also standardizes the test and minimizes the variables
>> for validation.
>>
>>
>>
> Ok, let's make it Audacity.
>
> The corrected text now looks:
>
> Install any sound recording application you're familiar with. If you've
> never worked with any, *Audacity* (the audacity package) is a popular
> full-featured audio editor which can also easily capture sound from your
> microphone.
>
>
Works for me!


-- 
真実はいつも一つ！/ Always, there's only one truth!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction Amanda Cavalcante

[Alessio]

On Wed, 2021-01-20 at 01:26 +, Amanda dos Santos Cavalcante wrote:
> Hello, Fedora Project people !!!

Hello Amanda, and welcome. I just sponsored you in the QA team.
Being a beginner in the Linux universe is not an issue, IMHO.
By joining this team you have the chance to learn various things, also
how to use Fedora Linux :-D At the same time I think that tests
performed by a non expert are also valuable (I don't want to say that
I'm an expert, indeed I have to learn a lot of things).
In addition, if geraldosimiao is willing to assist you, I think that
you have a great chance to learn and to help the community.


This list will get updates on different testing related activities and
updates from time to time. Subscribing the test-announce list can be
useful as well.

You can start to test updates in [http://bodhi.fedoraproject.org/] for
Fedora 32 and Fedora 33.
Update testing is where a tester tests a package and gives out a +1
Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora
Releases and tags viz "pending" & "testing". You can read much about
update testing here [1]. You can also use the RPM package fedora-easy-
karma for giving out feedbacks from the command line for the installed
packages (enable the updates-testing repository!).

Running release validation tests [2] [3] on Rawhide could be also
useful.

We usually involve ourselves in activities marked in [4], you can catch
us mostly at #fedora-qa on freenode IRC or Telegram.

If you have any question, please ask!

[0]
https://communityblog.fedoraproject.org/contribute-at-the-fedora-test-week-for-kernel-5-10/
[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2] https://fedoramagazine.org/release-validation-testing-fedora/
[3] https://fedoraproject.org/wiki/Test_Results:Current_Summary
[4] https://fedoraproject.org/wiki/QA#Activities


Ciao,
A.

___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Lukas Ruzicka]

On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa  wrote:

> On Thu, Jan 21, 2021 at 6:15 AM Kamil Paral  wrote:
> >
> > On Thu, Jan 21, 2021 at 11:24 AM Lukas Ruzicka 
> wrote:
> >>
> >>
> >> On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka 
> wrote:
> 
>  Have you tested whether gnome-sound-recorder works well in KDE and
> optionally also other desktops? If not (or if it pulls too many
> dependencies), it would be good to suggest an alternative tool as well.
> >>
> >>
> >
>
> If you want to endorse a cross-desktop tool for testing, I would
> suggest Audacity. It's simple, powerful, and known to work on all
> desktops. It also standardizes the test and minimizes the variables
> for validation.
>
>
>
Ok, let's make it Audacity.

The corrected text now looks:

Install any sound recording application you're familiar with. If you've
never worked with any, *Audacity* (the audacity package) is a popular
full-featured audio editor which can also easily capture sound from your
microphone.



>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Neal Gompa]

On Thu, Jan 21, 2021 at 6:15 AM Kamil Paral  wrote:
>
> On Thu, Jan 21, 2021 at 11:24 AM Lukas Ruzicka  wrote:
>>
>>
>> On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka  wrote:

 Have you tested whether gnome-sound-recorder works well in KDE and 
 optionally also other desktops? If not (or if it pulls too many 
 dependencies), it would be good to suggest an alternative tool as well.
>>
>>
>> So, now I have found the KDE recording tool - KWave. I have tested it and 
>> works ok for the purposes of the test. I am updating the steps in the 
>> proposal to:
>>
>> If you do not have any sound recording application installed, install Gnome 
>> Sound Recorder (the gnome-sound-recorder package) on GNOME or KWave (the 
>> kwave package) on KDE.
>
>
> I believe we should move away from desktop tribalism, if possible. If one 
> tool works well on all desktops, recommend that one, regardless of its name 
> or library toolkit used. Of course ideally such a tool shouldn't pull half of 
> some desktop with it as dependencies (as KWave does), and should have a 
> reasonably newcomer friendly UI. It would also make the instructions sound 
> better, currently it seems like we only care about GNOME and KDE.
>

GNOME applications pull in most of the GNOME desktop as dependencies.
Properly developed KDE applications will pull in the KF5 libraries and
occasionally some Plasma libraries. That's just how it goes. It is
also unrealistic to expect GNOME applications to work fully "to spec"
on KDE because KDE does not provide all the D-Bus interfaces and
services that GNOME does. We can and do have quirks when applications
are transplanted from one desktop environment to another, if the
underlying frameworks don't handle this well. While most of the KDE
frameworks adapt well to a non-KDE environment, it's rare that GNOME
applications fully do, especially ones that depend on things like
gnome-settings-daemon, gnome-shell, or gnome-control-center. In the
case of gnome-sound-recorder, it'll be fine as it's quite simple. But
if you were using something like the GNOME screencast app, that would
fail in KDE. Note that I'm specifically saying "GNOME applications".
Plain GTK applications are generally fine on Plasma.

If you want to endorse a cross-desktop tool for testing, I would
suggest Audacity. It's simple, powerful, and known to work on all
desktops. It also standardizes the test and minimizes the variables
for validation.



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Kamil Paral]

On Thu, Jan 21, 2021 at 11:24 AM Lukas Ruzicka  wrote:

>
> On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka 
> wrote:
>
>> Have you tested whether gnome-sound-recorder works well in KDE and
>>> optionally also other desktops? If not (or if it pulls too many
>>> dependencies), it would be good to suggest an alternative tool as well.
>>>
>>
> So, now I have found the KDE recording tool - KWave. I have tested it and
> works ok for the purposes of the test. I am updating the steps in the
> proposal to:
>
> If you do not have any sound recording application installed, install *Gnome
> Sound Recorder* (the gnome-sound-recorder package) on GNOME or *KWave*
> (the kwave package) on KDE.
>

I believe we should move away from desktop tribalism, if possible. If one
tool works well on all desktops, recommend that one, regardless of its name
or library toolkit used. Of course ideally such a tool shouldn't pull half
of some desktop with it as dependencies (as KWave does), and should have a
reasonably newcomer friendly UI. It would also make the instructions sound
better, currently it seems like we only care about GNOME and KDE.

After playing with this a bit (on my GNOME desktop and in a KDE VM), I'd
say that gnome-sound-recorder is the best universal application to
recommend, it has minimal dependencies and a very straightforward UI. An
alternative could be Audacity, which has a bit more dependencies but still
nothing too large, and while it's a professional editor, it's UI to start
and playback a recording is still simpler than in KWave.

So, what about something like:
"Install any sound recording application you're familiar with. If you've
never worked with any, the GNOME Sound Recorder (`gnome-sound-recorder`
package) is small in size and simple to use. Alternatively, Audacity
(`audacity` package) is a popular full-featured audio editor which can also
easily capture sound from your microphone."

I didn't try too many available sound recording applications, perhaps there
are even better tools, but the mentioned ones are OK.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction Amanda Cavalcante

[Geraldo Simião Kutz]

Hello friends.
I know Amanda from the Brazilian telegram group, she's a friendly and
helpful person. I can help her in knowing how to contribute in the QA team,
but I cannot add her because I'm not a sponsor. So, please, if any sponsor
could help adding her to the team I'll be thankful. :)

Geraldo Simião

geraldosimiao

Em qui, 21 de jan de 2021 01:59, Amanda dos Santos Cavalcante <
amanda_kid...@hotmail.com> escreveu:

> I want to join the QA team and help.
>
> --
> *De:* Robbi Nespu 
> *Enviado:* terça-feira, 19 de janeiro de 2021 23:08
> *Para:* test@lists.fedoraproject.org 
> *Assunto:* Re: Introduction Amanda Cavalcante
>
>
>
> On 20/1/2021 9:26 am, Amanda dos Santos Cavalcante wrote:
> > Hello, Fedora Project people !!!
> >
> > I am very happy to join the Fedora team !!!
> > I'm a beginner in the Linux universe and I'm very excited to help.
> > I have only 6 months of experience in Linux, but I want to enjoy it for
> > the rest of my life.
> >
> > My name is Amanda dos Santos Cavalcante, I am 34 years old, I live in
> > Recife-PE, Brazil.
> > As I started to use a computer, around 2007, I always used Windows.
> > Linux here in Brazil is still very wronged.
> > It was in 2018 that I started flirting with Linux through YouTuber
> > Diolinux. But only in 2020 did I have direct contact with Linux.
> >
> > My first contact with Linux was EndlessOS when I bought a notebook that
> > came with the system by default. But I found it very limited for my
> > profile and installed Mint 20 Cinnamon. I was using Mint for 3 months
> > and then came to Fedora Mate 33.
> >
> > I am in love with Fedora Mate 33 because it is teaching me to understand
> > much more about Linux !!!
> > So I want to be able to help in whatever I can.
> > I hope to be useful so that the Fedora Project can be stronger and
> > stronger !!!
> >
> > Fas account: amandacavalcante
> > Telegram: @Amandextra
> > Emails: amanda_kid...@hotmail.com
> > cavalcante...@gmail.com
>
> Welcome to Fedora, this is testing (QA) mailing list so people here
> expect you interested to do testing. You can check here[1] for information.
>
> If you want to test new package, you can install testing repo[2] and
> give feedback on Bodhi if you encounter bug or nobug by giving karma.
>
> Warning: If it maybe breaking you system and IMO, I think new linux
> don't like it..but to me, this is fun. You can learn and contribute at
> the same time.
>
> Since you are using Fedora Mate Compiz, you can report bug if you
> encounter. I am sorry, I could find Fedora Mate Compiz SIG or it own
> mail list. Maybe someone else can show where it hide :)
>
> If you think you are in wrong mail list, then check[4]. It can guide you
> which area you like to contribute.
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FQAdata=04%7C01%7C%7Cd1ba3337455b4129c60908d8bce8498f%7C84df9e7fe9f640afb435%7C1%7C0%7C637467053134746387%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=U17oENAVnvmdslVe2ZVvt%2BD%2B6RVpTBGvDc8KstohJj4%3Dreserved=0
> [2]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FQA%3AUpdates_Testingdata=04%7C01%7C%7Cd1ba3337455b4129c60908d8bce8498f%7C84df9e7fe9f640afb435%7C1%7C0%7C637467053134756341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=fBVFvJUGIUYZmjBj9SmpuW5j1wjG4feHKM06k9S43mM%3Dreserved=0
> [3]
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbodhi.fedoraproject.org%2Fdata=04%7C01%7C%7Cd1ba3337455b4129c60908d8bce8498f%7C84df9e7fe9f640afb435%7C1%7C0%7C637467053134756341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=65KLkWHSq1vguoAgWSOiJTmaM2c7sutLvJODXp3RSJk%3Dreserved=0
> [4]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatcanidoforfedora.org%2Fendata=04%7C01%7C%7Cd1ba3337455b4129c60908d8bce8498f%7C84df9e7fe9f640afb435%7C1%7C0%7C637467053134756341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=SQxi%2BwMx9pYNdBeK4IeWl4UyOLzWI2iR9PmZo%2FKjQl8%3Dreserved=0
>
> --
> Email: robbinespu[@]fedoraproject[.]org
> PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
> PGP key:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkeybase.io%2Frobbinespu%2Fpgp_keys.ascdata=04%7C01%7C%7Cd1ba3337455b4129c60908d8bce8498f%7C84df9e7fe9f640afb435%7C1%7C0%7C637467053134756341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=h4sATLUHf5SHnE7PlLmDENaOf3ZTbLr7dIsCtQt4P8U%3Dreserved=0
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of 

Re: Testcase Audio Recording Basic (new test case proposal)

[Lukas Ruzicka]

On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka  wrote:

> Have you tested whether gnome-sound-recorder works well in KDE and
>> optionally also other desktops? If not (or if it pulls too many
>> dependencies), it would be good to suggest an alternative tool as well.
>>
>
So, now I have found the KDE recording tool - KWave. I have tested it and
works ok for the purposes of the test. I am updating the steps in the
proposal to:

If you do not have any sound recording application installed, install *Gnome
Sound Recorder* (the gnome-sound-recorder package) on GNOME or *KWave* (the
kwave package) on KDE.


>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>

>
> --
>
> Lukáš Růžička
>
> FEDORA QE, RHCE
>
> Red Hat
>
> 
>
> Purkyňova 115
>
> 612 45 Brno - Královo Pole
>
> lruzi...@redhat.com
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Lukas Ruzicka]

>
> Have you tested whether gnome-sound-recorder works well in KDE and
> optionally also other desktops? If not (or if it pulls too many
> dependencies), it would be good to suggest an alternative tool as well.
>

No, I haven't tested it and I was thinking about finding an alternative for
KDE. Thanks for reminding me. I will look for it and update the document.



>
>
>>
>>- Make sure the input sound device is correctly connected to your
>>computer, so that you can expect that sound will be recorded, i.e. you 
>> have
>>a microphone (or any sound producing device) connected to the input of 
>> your
>>sound adapter.
>>- Run *Settings* and navigate to the *Sound* tab. Check that your
>>sound device is correctly recognized by the system. In case you have more
>>input sound devices, make sure all of these devices are listed.
>>- Select a preferred device for input and set the input level using
>>the slider and the indicator below to avoid over-excitation of the signal
>>and sound distortion.
>>
>> How to test
>>
>>- Start a sound recording application.
>>- Record a sound clip of about 10 seconds using the microphone (or
>>another sound producing device).
>>- Play back the recorded sound.
>>
>> Expected Results
>>
>>- The recorded sound clip is *correctly* recorded and can be played
>>back. Note that the quality of the recording depends on many factors, such
>>as the quality of the sound adapter, the microphone, the wires used, etc.
>>Therefore the sound quality should not be considered a test failing
>>criterion unless the quality is much worse than expected.
>>
>>
> Except for the note above, LGTM.
>
> Do you intend to propose a new audio recording criterion? I think it has a
> reasonable chance of getting accepted.
>

Yes. Then I should probably write one :D



>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Fedora Audio Test Cases for Test Day (a proposal)

[Lukas Ruzicka]

On Wed, Jan 20, 2021 at 5:21 PM Kamil Paral  wrote:

> On Wed, Jan 20, 2021 at 5:02 PM Brandon Nielsen 
> wrote:
>
>> Would some kind of device switching test case be feasible? In my
>> experience that's where a lot of weird behavior creeps in. For example,
>> plugging in a USB interface, using it, and unplugging it. Or switching back
>> and forth between Bluetooth and wired hardware (or even changing Bluetooth
>> headset mode back and forth between A2DP / HFP).
>>
>
> This is a great idea, I love it! Most of us now have at least two output
> devices - the usual jack output and a display connected over DP/HDMI. Not
> all monitors have integrated speakers, but some have a jack connector you
> can connect your headphones in. And that's exactly how I use it - speakers
> connected to my desktop's output jack, and headphones connected to my
> monitor, which allows me to switch between speakers and headphones in a
> pure software way, without replugging connectors all the time. Sometimes it
> causes some issues. This would be a great test case with Pipewire.
>
> And as suggested by Brandon, other devices like USB headphones or
> Bluetooth headphones are probably even more common than my own use case.
> Let's cover this.
>

Ack




>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org