Fedora-Cloud-33-20210216.0 compose check report

[Fedora compose checker]

No missing expected images.

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

Old soft failures (same test soft failed in Fedora-Cloud-33-20210215.0):

ID: 779016  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/779016
ID: 779023  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/779023

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Introduction to Test

[Hugh Campbell via test]

Thank y'all for the welcome! I'll definitely check out the Security Group
here as well as start going over the testing process so I can start
contributing as soon as possible. Look forward to working with you all and
helping to make Fedora even better than it already is!

On Mon, Feb 15, 2021 at 12:22 PM Alessio  wrote:

> On Mon, 2021-02-15 at 10:19 -0500, Matthew Miller wrote:
> > Awesome! One other area you might find interesting and where your
> > expertise
> > would by welcome is the Fedora Security Team. This effort has been ...
> > quiescent ... recently and there seems like there might be some energy
> > around restarting it. If you're interested in that, it could certainly
> > use
> > your help!
>
> I agree.
> In the meanwhile I sponsored you in the QA FAS group. It is a good way
> to stay in touch with the community and perform some tasks.
>
>
> 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 F34 could be also
> useful since we are approaching the next Fedora release.
>
> 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.
>
>

-- 
V/R
- Hugh

He / Him / His

Mobile: 843.718.7576

"You will never do anything in this world without courage. It is the
greatest quality of the mind next to honor." - Aristotle

"The supreme quality for leadership is unquestionably integrity. Without
it, no real success is possible, no matter whether it is on a section gang,
a football field, in an army, or in an office." - Dwight D. Eisenhower

七転び八起き ("Nana korobi ya oki", Fall seven times, rise eight.) - Japanese
Proverb
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Introduction to Test

[Alessio]

On Mon, 2021-02-15 at 10:19 -0500, Matthew Miller wrote:
> Awesome! One other area you might find interesting and where your
> expertise
> would by welcome is the Fedora Security Team. This effort has been ...
> quiescent ... recently and there seems like there might be some energy
> around restarting it. If you're interested in that, it could certainly
> use
> your help!

I agree.
In the meanwhile I sponsored you in the QA FAS group. It is a good way
to stay in touch with the community and perform some tasks.


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 F34 could be also
useful since we are approaching the next Fedora release.

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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Self-introduction: Josevaldo

[Alessio]

Hello Josevaldo. 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 F34 could be also
useful since we are approaching the next Fedora release.

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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Introduction to Test

[Matthew Miller]

On Sun, Feb 14, 2021 at 03:09:21PM -0500, Hugh Campbell via test wrote:
> I’m looking forward to helping the Fedora team currently with QA/Testing
> needs and in other areas as necessary. I’ve been an active Linux user since
> 2001 and have used Fedora since Core 1 release. Outside of some
> organizations requirements to use an enterprise Linux distribution such as
> RHEL/CentOS for workstations (and a brief period of using Debian/Ubuntu as
> a change of pace), Fedora has been my primary day-to-day driver for all my
> systems at home and at work.

Awesome! One other area you might find interesting and where your expertise
would by welcome is the Fedora Security Team. This effort has been ...
quiescent ... recently and there seems like there might be some energy
around restarting it. If you're interested in that, it could certainly use
your help!

https://lists.fedoraproject.org/archives/list/security-t...@lists.fedoraproject.org/message/CN76VU6IWCHXN5ZLQFHGIL65DRCXA3F7/


-- 
Matthew Miller

Fedora Project Leader
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: In Fedora 34, cannot install "C Development Tools and Libraries"

[wang_chen]

install opencsd-0.14:
dnf install -y 
ftp://ftp.sjtu.edu.cn/fedora/linux/updates/32/Everything/x86_64/Packages/o/opencsd-0.14.1-1.fc32.x86_64.rpm
 
dnf install -y 
ftp://ftp.sjtu.edu.cn/fedora/linux/updates/32/Everything/x86_64/Packages/o/opencsd-devel-0.14.1-1.fc32.x86_64.rpm
then run:
dnf -y groupinstall "C Development Tools and Libraries" "Development Tools"
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

[Lukas Ruzicka]

>
> So you say there's no need to change the Basic Audio test case [1] yet
> there is a testcase for it [2], which on a proper look is called slightly
> different but basically the same. Would it make sense to either rename it
> to something that is less interchangeable, or unify it into a single test
> case applicable for both use cases?
>

The Test Day basic audio has specific applications listed which should be
used, because this is what Wim suggested to test. The usual Audio Basic has
no such listings and I do not think that people want to specify some
applications and leave out some others that they might possibly test.

The name can be easily changed.



>
> [1] https://fedoraproject.org/wiki/QA:Testcase_audio_basic
> [2] https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio
>
> ___
> 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
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 

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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-IoT-34-20210215.0 compose check report

[Fedora compose checker]

Missing expected images:

Iot dvd aarch64
Iot dvd x86_64

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

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

ID: 778624  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/778624
ID: 778635  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/778635
ID: 778640  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/778640

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-20210214.2):

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

Passed openQA tests: 14/16 (x86_64), 13/15 (aarch64)
-- 
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-34-20210215.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Minimal raw-xz armhfp
Xfce raw-xz armhfp

Failed openQA tests: 32/183 (x86_64), 28/124 (aarch64)

New failures (same test not failed in Fedora-34-20210214.n.0):

ID: 778248  Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/778248
ID: 778318  Test: aarch64 Server-dvd-iso install_updates_nfs@uefi
URL: https://openqa.fedoraproject.org/tests/778318
ID: 778344  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/778344
ID: 778433  Test: aarch64 universal install_package_set_minimal@uefi
URL: https://openqa.fedoraproject.org/tests/778433
ID: 778458  Test: aarch64 universal install_blivet_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/778458

Old failures (same test failed in Fedora-34-20210214.n.0):

ID: 778178  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/778178
ID: 778182  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/778182
ID: 778189  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/778189
ID: 778194  Test: x86_64 Server-dvd-iso mediakit_fileconflicts
URL: https://openqa.fedoraproject.org/tests/778194
ID: 778198  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/778198
ID: 778201  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/778201
ID: 778203  Test: x86_64 Server-dvd-iso realmd_join_sssd
URL: https://openqa.fedoraproject.org/tests/778203
ID: 778215  Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/778215
ID: 778239  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/778239
ID: 778242  Test: x86_64 KDE-live-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/778242
ID: 778244  Test: x86_64 KDE-live-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/778244
ID: 778249  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/778249
ID: 778250  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/778250
ID: 778252  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/778252
ID: 778253  Test: x86_64 KDE-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/778253
ID: 778255  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/778255
ID: 778275  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/778275
ID: 778290  Test: aarch64 Server-dvd-iso support_server@uefi
URL: https://openqa.fedoraproject.org/tests/778290
ID: 778293  Test: aarch64 Server-dvd-iso 
server_role_deploy_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/778293
ID: 778295  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/778295
ID: 778303  Test: aarch64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/778303
ID: 778304  Test: aarch64 Server-dvd-iso install_btrfs_preserve_home@uefi
URL: https://openqa.fedoraproject.org/tests/778304
ID: 778305  Test: aarch64 Server-dvd-iso mediakit_fileconflicts@uefi
URL: https://openqa.fedoraproject.org/tests/778305
ID: 778309  Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi
URL: https://openqa.fedoraproject.org/tests/778309
ID: 778311  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/778311
ID: 778312  Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi
URL: https://openqa.fedoraproject.org/tests/778312
ID: 778323  Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi
URL: https://openqa.fedoraproject.org/tests/778323
ID: 778325  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/778325
ID: 778353  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/778353
ID: 778359  Test: x86_64 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/778359
ID: 778370  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/778370
ID: 778371  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/778371
ID: 778378  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/778378
ID: 778379  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: 

Fedora 34 compose report: 20210215.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-34-20210214.n.0
NEW: Fedora-34-20210215.n.0

= SUMMARY =
Added images:0
Dropped images:  2
Added packages:  0
Dropped packages:0
Upgraded packages:   60
Downgraded packages: 1

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   367.25 MiB
Size of downgraded packages: 16.73 MiB

Size change of upgraded packages:   3.97 MiB
Size change of downgraded packages: 289.65 KiB

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Cinnamon live x86_64
Path: Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-34-20210214.n.0.iso
Image: Comp_Neuro live x86_64
Path: Labs/x86_64/iso/Fedora-Comp_Neuro-Live-x86_64-34-20210214.n.0.iso

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  adf-gillius-fonts-1.009-1.fc34
Old package:  adf-gillius-fonts-1.008-21.fc34
Summary:  ADF Gillius sans-serif typeface family, a GillSans alternative
RPMs: adf-gillius-2-fonts adf-gillius-fonts adf-gillius-fonts-all 
adf-gillius-fonts-doc
Added RPMs:   adf-gillius-fonts-all adf-gillius-fonts-doc
Dropped RPMs: adf-gillius-fonts-common
Size: 376.02 KiB
Size change:  99.06 KiB
Changelog:
  * Sat Feb 13 2021 Michael J. Gruber  - 1.009-1
  - rebase with upstream 1.009
  - switch to current fonts rpm macros


Package:  amiri-fonts-0.113-1.fc34
Old package:  amiri-fonts-0.112-4.fc34
Summary:  A classical Arabic font in Naskh style
RPMs: amiri-fonts amiri-fonts-common amiri-quran-fonts
Size: 749.64 KiB
Size change:  -30.36 KiB
Changelog:
  * Mon Feb 15 2021 Mosaab Alzoubi  - 0.113-1
  - Update to 0.113


Package:  apt-2.1.20-1.fc34
Old package:  apt-2.1.18-2.fc34
Summary:  Command-line package manager for Debian packages
RPMs: apt apt-apidoc apt-devel apt-doc apt-libs apt-utils
Size: 16.81 MiB
Size change:  30.65 KiB
Changelog:
  * Mon Feb 15 2021 Mosaab Alzoubi  - 2.1.20-1
  - Update to 2.1.20


Package:  bpytop-1.0.62-1.fc34
Old package:  bpytop-1.0.61-2.fc34
Summary:  Linux/OSX/FreeBSD resource monitor
RPMs: bpytop
Size: 74.67 KiB
Size change:  509 B
Changelog:
  * Sun Feb 14 2021 Artem Polishchuk  - 1.0.62-1
  - build(update): 1.0.62


Package:  bugzilla-5.0.6-12.fc34
Old package:  bugzilla-5.0.6-11.fc34
Summary:  Bug tracking system
RPMs: bugzilla bugzilla-contrib bugzilla-doc bugzilla-doc-build
Size: 2.67 MiB
Size change:  -435 B
Changelog:
  * Sun Feb 14 2021 Emmanuel Seyman  - 5.0.6-12
  - Add make to BuildRequires


Package:  cadical-1:1.4.0-1.fc34
Old package:  cadical-1:1.3.0-2.fc34
Summary:  Simplified SAT solver
RPMs: cadical cadical-devel cadical-libs
Size: 2.04 MiB
Size change:  6.39 KiB
Changelog:
  * Sun Feb 14 2021 Jerry James  - 1:1.4.0-1
  - Version 1.4.0


Package:  cloc-1.88-1.fc34
Old package:  cloc-1.82-6.fc34
Summary:  Count lines of code
RPMs: cloc
Size: 122.33 KiB
Size change:  9.63 KiB
Changelog:
  * Sun Feb 14 2021 Chris Egeland  - 1.88-1
  - Latest release.


Package:  fuse-btfs-2.24-1.fc34
Old package:  fuse-btfs-2.23-2.fc34
Summary:  FUSE filesystem Bittorrent
RPMs: fuse-btfs
Size: 324.69 KiB
Size change:  1.37 KiB
Changelog:
  * Sun Feb 14 2021 Mikel Olasagasti Uranga  - 2.24-1
  - Update to 2.24


Package:  gap-pkg-profiling-2.4.1-1.fc34
Old package:  gap-pkg-profiling-2.4-1.fc34
Summary:  Line by line profiling and code coverage for GAP
RPMs: gap-pkg-profiling gap-pkg-profiling-doc
Size: 574.30 KiB
Size change:  1.55 KiB
Changelog:
  * Sun Feb 14 2021 Jerry James  - 2.4.1-1
  - Version 2.4.1


Package:  gnome-shell-40.0~alpha.1.1-8.20210212git829a096ba.fc34
Old package:  gnome-shell-40.0~alpha.1.1-6.20210212git829a096ba.fc34
Summary:  Window management and application launching for GNOME
RPMs: gnome-shell
Size: 7.94 MiB
Size change:  710 B
Changelog:
  * Sun Feb 14 2021 Florian M??llner  - 
40.0~alpha.1.1-7.20210212git829a096ba
  - Don't open app picker when clicking minimap

  * Sun Feb 14 2021 Florian M??llner  - 
40.0~alpha.1.1-8.20210212git829a096ba
  - Only open app picker on left-click/touch


Package:  goaccess-1.4.5-1.fc34
Old package:  goaccess-1.4.3-2.fc34
Summary:  Real-time web log analyzer and interactive viewer
RPMs: goaccess
Size: 1.65 MiB
Size change:  39.51 KiB
Changelog:
  * Sun Feb 14 2021 Eduardo Echeverria  - 1.4.5-1
  - Update to 1.4.5 fixes rhbz#1920124


Package:  godot-3.2.3-1.fc34
Old package:  godot-3.2.1-1.fc34.2
Summary:  Multi-platform 2D and 3D game engine with a feature-rich editor
RPMs: godot godot-headless godot-runner godot-server
Size: 176.59 MiB
Size change:  -829.56 KiB
Changelog:
  * Fri Feb 12 2021 R??mi Verschelde  - 3.2.3-1
  - Version 3.2.3-stable
  - Drop tentative support for building for RHEL8
  - Backport upstream patch to fix TGA loader crash (CVE-2021

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

[Kamil Paral]

On Mon, Feb 15, 2021 at 11:37 AM Lukas Ruzicka  wrote:

> On Mon, Feb 15, 2021 at 11:09 AM Kamil Paral  wrote:
>
>> Oh, one more question. Can you please specify which testcases you think
>> should be general testcases to be included in our release validation
>> matrices, and which testcases you consider PipeWire TestDay-related only?
>>
>
> All tests cases in this batch are intended for Audio Test Days. There is
> not need to change the Basic Audio test case we have already had and there
> is a new recording test case proposed that we discussed some time ago here
> on this list.
>

So you say there's no need to change the Basic Audio test case [1] yet
there is a testcase for it [2], which on a proper look is called slightly
different but basically the same. Would it make sense to either rename it
to something that is less interchangeable, or unify it into a single test
case applicable for both use cases?

[1] https://fedoraproject.org/wiki/QA:Testcase_audio_basic
[2] https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

[Lukas Ruzicka]

>
>
> "This test case can be performed on both bare machines." doesn't make
> sense to me.
>

Originally I thought that some tests could be done on VMs, too, but then I
thought that I do not want it, cause it may only cause some troubles. This
is a remnant which I overlooked.


>
> "Boot the system and log in as a common user." - I think the more
> frequently used term is a "regular user". Do I understand correctly that
> you mean any non-root user (i.e. your regular user can have admin
> privileges - be in the wheel group, right?). Perhaps you can clarify with
> "log in as a regular user (i.e. not root)" or similar.
>

Ok, "regular user" it will be.


>
> I really really really dislike when there's a testing step "Run command
> X", but the step doesn't say what the output should be. And you have to
> look at the bottom and try to figure out where it is in the Expected
> results section. And basically piece together the actual steps by jumping
> forth and back, easily making mistakes or skipping something. The Expected
> results section should contain some overall guidance that is valid for the
> whole testcase duration, or instructions which don't fit into the testing
> structure. But immediate result checking should be part of the How to test
> section. For example:
> "Check that the pipewire systemd service shows up as active: $ systemctl
> --user status pipewire"
> or
> "Run "pactl list" and verify that is lists all available audio and video
> devices on the system"
>

Hmm, this makes actually sense, because I dislike the way to split it, too.
Will rewrite it.
Thanks.


>
> "the server name must read PulseAudio (on PipeWire \ldots )" - that's some
> forgotten formatting in there, I guess?
>

Sure, LaTeX origin.


>
>
>>
>>- PipeWire CLI works (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
>>- ALSA backend works (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
>>- Basic Audio tests (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio)
>>- Pavucontrol works (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
>>)
>>- Pavucontrol mixing (
>>
>> https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
>>)
>>- Pavucontrol recording (
>>
>> https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_recording
>>)
>>- Pavucontrol add and remove devices (
>>
>> https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addremove
>>)
>>- PipeWire handles Bluetooth devices (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
>>)
>>- Jack applications (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
>>- Jack MIDI routing (
>>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)
>>
>>
> Could you please rewrite the rest of the testcases into a more readable
> format (regarding the "Expected results" section) before I review them all?
> Just by quickly looking at them, some of them are very hard to follow,
> especially when they commonly have 8+ points in the expected results, and
> my brain hurts when trying to make sense of them in this format. I would
> get discouraged from executing these test cases just on this ground alone
> :-) Thanks a lot.
>

Yes.


>
>
> ___
> 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
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 

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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

[Lukas Ruzicka]

On Mon, Feb 15, 2021 at 11:09 AM Kamil Paral  wrote:

> On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka  wrote:
>
>> Below, you can find the drafts of the test cases prepared on our Wiki for
>> you to read and comment. Also, if you have some other audio use cases that
>> you think should be tested, please let us know. Any suggestions are welcome.
>>
>
>> List of test cases to test that:
>>
>
> Oh, one more question. Can you please specify which testcases you think
> should be general testcases to be included in our release validation
> matrices, and which testcases you consider PipeWire TestDay-related only?
>

All tests cases in this batch are intended for Audio Test Days. There is
not need to change the Basic Audio test case we have already had and there
is a new recording test case proposed that we discussed some time ago here
on this list.

___

> 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
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 

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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

[Kamil Paral]

On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka  wrote:

> Below, you can find the drafts of the test cases prepared on our Wiki for
> you to read and comment. Also, if you have some other audio use cases that
> you think should be tested, please let us know. Any suggestions are welcome.
>

> List of test cases to test that:
>

Oh, one more question. Can you please specify which testcases you think
should be general testcases to be included in our release validation
matrices, and which testcases you consider PipeWire TestDay-related only?
I'm asking because testday-only testcases can often be more specific, while
general-purpose testcases should be more generic (so that we can use them
in many releases and environments), and I might be reading them in a
different light, then. Thanks.
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

[Kamil Paral]

On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka  wrote:

> List of test cases to test that:
>
>- PipeWire is used by default (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default
>)
>
>
"This test case can be performed on both bare machines." doesn't make sense
to me.

"Boot the system and log in as a common user." - I think the more
frequently used term is a "regular user". Do I understand correctly that
you mean any non-root user (i.e. your regular user can have admin
privileges - be in the wheel group, right?). Perhaps you can clarify with
"log in as a regular user (i.e. not root)" or similar.

I really really really dislike when there's a testing step "Run command X",
but the step doesn't say what the output should be. And you have to look at
the bottom and try to figure out where it is in the Expected results
section. And basically piece together the actual steps by jumping forth and
back, easily making mistakes or skipping something. The Expected results
section should contain some overall guidance that is valid for the whole
testcase duration, or instructions which don't fit into the testing
structure. But immediate result checking should be part of the How to test
section. For example:
"Check that the pipewire systemd service shows up as active: $ systemctl
--user status pipewire"
or
"Run "pactl list" and verify that is lists all available audio and video
devices on the system"

"the server name must read PulseAudio (on PipeWire \ldots )" - that's some
forgotten formatting in there, I guess?


>
>- PipeWire CLI works (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
>- ALSA backend works (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
>- Basic Audio tests (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio)
>- Pavucontrol works (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
>)
>- Pavucontrol mixing (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
>)
>- Pavucontrol recording (
>
> https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_recording
>)
>- Pavucontrol add and remove devices (
>
> https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addremove
>)
>- PipeWire handles Bluetooth devices (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
>)
>- Jack applications (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
>- Jack MIDI routing (
>https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)
>
>
Could you please rewrite the rest of the testcases into a more readable
format (regarding the "Expected results" section) before I review them all?
Just by quickly looking at them, some of them are very hard to follow,
especially when they commonly have 8+ points in the expected results, and
my brain hurts when trying to make sense of them in this format. I would
get discouraged from executing these test cases just on this ground alone
:-) Thanks a lot.
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-32-20210215.0 compose check report

[Fedora compose checker]

No missing expected images.

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

Old soft failures (same test soft failed in Fedora-Cloud-32-20210214.0):

ID: 777950  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/777950
ID: 777957  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/777957

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure