We need KDE aarch64 coverage for F42 release candidates

[Kamil Paral]

Hi folks,
the first F42 Beta RC just dropped:
https://lists.fedoraproject.org/archives/list/[e-mail]...

Since KDE is now release blocking not only on x86_64, but also on aarch64,
we need KDE folks to participate in testing and make sure all KDE-related
test cases are covered (Basic and Beta milestone). Especially for aarch64,
where we simply don't have the capacity to test it all.

I wrote a testing guide for the previous test cycle, it's here:
https://lists.fedoraproject.org/archives/list/[e-mail]/th...

Since the last time, we've overhauled our testcase_stats webpage, and you
can now easily see KDE coverage for all test cases (so from the guide,
ignore everything saying that determining per-desktop coverage is difficult
- now it's simple!).

See the current coverage here:
https://openqa.fedoraproject.org/testcase_stats/42/

Please pay particular attention to these sections:
https://openqa.fedoraproject.org/testcase_stats/42/#Release-blocking%20envir...)
and
https://openqa.fedoraproject.org/testcase_stats/42/#Release-blocking%20deskt...

Currently KDE is completely untested, with a red background. We don't like
red, we like green! Please help us turn it green.

For any questions, please visit #quality:fedoraproject.org Matrix channel,
and ask. There are several of us to help you with testing, and especially
lbrabec to help with aarch64 testing.

Thank you!

[Derek Enz]

Ok I have a rpi4 with F41 KDE setup. I’ll try to work on F42 next week.

Derek Enz

On Fri, Mar 7, 2025 at 4:44 AM Kamil Paral via kde <
[e-mail]> wrote:
> Hi folks,
> the first F42 Beta RC just dropped:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>
> Since KDE is now release blocking not only on x86_64, but also on aarch64,
> we need KDE folks to participate in testing and make sure all KDE-related
> test cases are covered (Basic and Beta milestone). Especially for aarch64,
> where we simply don't have the capacity to test it all.
>
> I wrote a testing guide for the previous test cycle, it's here:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]/th...
>
> Since the last time, we've overhauled our testcase_stats webpage, and you
> can now easily see KDE coverage for all test cases (so from the guide,
> ignore everything saying that determining per-desktop coverage is difficult
> now it's simple!).
>
> See the current coverage here:
> https://openqa.fedoraproject.org/testcase_stats/42/
>
> Please pay particular attention to these sections:
>
> https://openqa.fedoraproject.org/testcase_stats/42/#Release-blocking%20envir...)
> and
>
> https://openqa.fedoraproject.org/testcase_stats/42/#Release-blocking%20deskt...
>
> Currently KDE is completely untested, with a red background. We don't like
> red, we like green! Please help us turn it green.
>
> For any questions, please visit #quality:fedoraproject.org Matrix
> channel, and ask. There are several of us to help you with testing, and
> especially lbrabec to help with aarch64 testing.
> Thank you!
>
> kde mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Lukas Brabec]

Hello,

Fedora 42 Candidate Beta-1.3 is ready:
https://lists.fedoraproject.org/archives/list/[e-mail]...

KDE on aarch64 is still completely untested. Please test.

Thanks!
>

[Jason L Tibbitts III]

> > > > > Lukas Brabec via kde  writes:
> KDE on aarch64 is still completely untested. Please test.

What's the simplest/most economically reasonable way to test this for
those who don't currently have hardware?  I could potentially purchase
something for testing if it's not too expensive, but don't want to be
left with something that's uselessly slow our outdated in a year.

_ J<

[Troy Dawson]

On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde <
[e-mail]> wrote:
> Hello,
>
> Fedora 42 Candidate Beta-1.3 is ready:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>
> KDE on aarch64 is still completely untested. Please test.
>
> Thanks!
> >

I'm curious about the Fedora Workstation aarch64 tests.
What hardware is it run on?

I see that for both Workstation and KDE you give the aarch64 iso, instead
of the raw.xz
Is it using the iso provided?

Am I invalidating my tests by using the raw.xz?
Can I use an aarch64 virtual machine?  If yes, can it be running on x86_64?

Sorry for the questions, but this is my first time doing desktop testing.
Troy

[Neal Gompa]

On Tue, Mar 11, 2025, 5:11 PM Troy Dawson via kde <
[e-mail]> wrote:
> On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde <
> [e-mail]> wrote:
> > Hello,
> >
> > Fedora 42 Candidate Beta-1.3 is ready:
> >
> > https://lists.fedoraproject.org/archives/list/[e-mail]...
> >
> > KDE on aarch64 is still completely untested. Please test.
> >
> > Thanks!
> > >
>
> I'm curious about the Fedora Workstation aarch64 tests.
> What hardware is it run on?
>
> I see that for both Workstation and KDE you give the aarch64 iso, instead
> of the raw.xz
> Is it using the iso provided?
>
> Am I invalidating my tests by using the raw.xz?
> Can I use an aarch64 virtual machine?  If yes, can it be running on x86_64?
>
> Sorry for the questions, but this is my first time doing desktop testing.

You can use either, but the release blocking artifact is the raw xz which
is also available. I'd recommend testing both if you can.

[Troy Dawson]

On Tue, Mar 11, 2025 at 4:23 PM Neal Gompa  wrote:
> On Tue, Mar 11, 2025, 5:11 PM Troy Dawson via kde <
> [e-mail]> wrote:
> > On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde <
> > [e-mail]> wrote:
> > > Hello,
> > >
> > > Fedora 42 Candidate Beta-1.3 is ready:
> > >
> > > https://lists.fedoraproject.org/archives/list/[e-mail]...
> > >
> > > KDE on aarch64 is still completely untested. Please test.
> > >
> > > Thanks!
> > > >
> >
> > I'm curious about the Fedora Workstation aarch64 tests.
> > What hardware is it run on?
> >
> > I see that for both Workstation and KDE you give the aarch64 iso, instead
> > of the raw.xz
> > Is it using the iso provided?
> >
> > Am I invalidating my tests by using the raw.xz?
> > Can I use an aarch64 virtual machine?  If yes, can it be running on
> > x86_64?
> >
> > Sorry for the questions, but this is my first time doing desktop testing.
>
> You can use either, but the release blocking artifact is the raw xz which
> is also available. I'd recommend testing both if you can.

I wasn't able to get anything to boot the live iso  (Either KDE or
Workstation) so I used the raw xz.
Two things to note.
1- KDE does not automount, and I personally don't want it to automount.  It
tells me something is there and gives me the option to mount it with one
click.  So I grayed out that section.
2 - Printing.  There was literally no setup needed, it just worked
automatically.  I did the PDF save, worked great.  I then clicked on the
box where you would change printers, and there was my printer.  It not only
showed my printer, but it must have queried my printer for the options
because I could then tell it to print double sided.   Anyway, worked
great.  I wish other, proprietary operating systems printed that well.

Troy
p.s. I know I didn't finish, I ran out of time.  I'll try to get the rest
tomorrow.

[Neal Gompa]

On Tue, Mar 11, 2025 at 9:58 PM Troy Dawson  wrote:
> On Tue, Mar 11, 2025 at 4:23 PM Neal Gompa  wrote:
> > On Tue, Mar 11, 2025, 5:11 PM Troy Dawson via kde  wrote:
> > > On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde  wrote:
> > > > Hello,
> > > >
> > > > Fedora 42 Candidate Beta-1.3 is ready:
> > > > https://lists.fedoraproject.org/archives/list/[e-mail]...
> > > >
> > > > KDE on aarch64 is still completely untested. Please test.
> > > >
> > > > Thanks!
> > >
> > > I'm curious about the Fedora Workstation aarch64 tests.
> > > What hardware is it run on?
> > >
> > > I see that for both Workstation and KDE you give the aarch64 iso, instead of the raw.xz
> > > Is it using the iso provided?
> > >
> > > Am I invalidating my tests by using the raw.xz?
> > > Can I use an aarch64 virtual machine?  If yes, can it be running on x86_64?
> > >
> > > Sorry for the questions, but this is my first time doing desktop testing.
> >
> > You can use either, but the release blocking artifact is the raw xz which is also available. I'd recommend testing both if you can.
>
> I wasn't able to get anything to boot the live iso  (Either KDE or Workstation) so I used the raw xz.

I was able to boot the KDE live ISO on a System76 Thelio Astra and
boot the installed system while I was at SCaLE last week. It worked,
but everything was stuck at 800x600 because nouveau could not
initialize the NVIDIA RTX 40 series GPU, so I was stuck with
SimpleDRM. Alas, I am no longer at SCaLE and unable to continue
troubleshooting. :(
> Two things to note.
> 1- KDE does not automount, and I personally don't want it to automount.  It tells me something is there and gives me the option to mount it with one click.  So I grayed out that section.
> 2 - Printing.  There was literally no setup needed, it just worked automatically.  I did the PDF save, worked great.  I then clicked on the box where you would change printers, and there was my printer.  It not only showed my printer, but it must have queried my printer for the options because I could then tell it to print double sided.   Anyway, worked great.  I wish other, proprietary operating systems printed that well.
>
> Troy
> p.s. I know I didn't finish, I ran out of time.  I'll try to get the rest tomorrow.

Thanks!

--
真実はいつも一つ！/ Always, there's only one truth!

[Kamil Paral]

On Tue, Mar 11, 2025 at 10:11 PM Troy Dawson via kde <
[e-mail]> wrote:
> On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde <
> [e-mail]> wrote:
> > Hello,
> >
> > Fedora 42 Candidate Beta-1.3 is ready:
> >
> > https://lists.fedoraproject.org/archives/list/[e-mail]...
> >
> > KDE on aarch64 is still completely untested. Please test.
> >
> > Thanks!
> > >
>
> I'm curious about the Fedora Workstation aarch64 tests.
> What hardware is it run on?

Some tests run in OpenQA in a virtual machine (those with a robot icon),
other tests performed by lbrabec are tested on a RPi4.
> Can I use an aarch64 virtual machine?  If yes, can it be running on x86_64?

You can. But cross-arch virtualization will be painfully slow.

However, note that the purpose of release validation testing is to check
whether the images will work for the majority of our users. So while
testing in a VM is theoretically possible for all or most desktop test
cases (test cases which specifically require bare metal testing are marked
as such), it's not the real-world usage. So at least for a release
candidate, we definitely strive for bare metal coverage as much as possible
(in the past, we've seen a large number of issues happening only on a RPi,
for example).

Here's a list of officially supported boards:
https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms
(Oh yes, the page is horribly outdated. We've asked relevant people so many
times to update it. Nevertheless, this is what we have).

Most users will run on a RPi3 or RPi4, so that's what we should
realistically test, and that's what we do. Testing in a VM is good for
automation or when you have no other choice. Testing on exotic hardware
might be fun, but has very limited benefit.
> Sorry for the questions, but this is my first time doing desktop testing.

Very appreciated! I might not spot these questions in the KDE list every
time, feel free to use the test list or our #quality:fedoraproject.org
matrix channel, if you see no reply. Thanks.

[Troy Dawson]

On Wed, Mar 12, 2025 at 1:34 AM Kamil Paral  wrote:
> On Tue, Mar 11, 2025 at 10:11 PM Troy Dawson via kde <
> [e-mail]> wrote:
> > On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde <
> > [e-mail]> wrote:
> > > Hello,
> > >
> > > Fedora 42 Candidate Beta-1.3 is ready:
> > >
> > > https://lists.fedoraproject.org/archives/list/[e-mail]...
> > >
> > > KDE on aarch64 is still completely untested. Please test.
> > >
> > > Thanks!
> > > >
> >
> > I'm curious about the Fedora Workstation aarch64 tests.
> > What hardware is it run on?
>
> Some tests run in OpenQA in a virtual machine (those with a robot icon),
> other tests performed by lbrabec are tested on a RPi4.
> > Can I use an aarch64 virtual machine?  If yes, can it be running on
> > x86_64?
>
> You can. But cross-arch virtualization will be painfully slow.
>
> However, note that the purpose of release validation testing is to check
> whether the images will work for the majority of our users. So while
> testing in a VM is theoretically possible for all or most desktop test
> cases (test cases which specifically require bare metal testing are marked
> as such), it's not the real-world usage. So at least for a release
> candidate, we definitely strive for bare metal coverage as much as possible
> (in the past, we've seen a large number of issues happening only on a RPi,
> for example).
>
> Here's a list of officially supported boards:
> https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms
> (Oh yes, the page is horribly outdated. We've asked relevant people so
> many times to update it. Nevertheless, this is what we have).
>
> Most users will run on a RPi3 or RPi4, so that's what we should
> realistically test, and that's what we do. Testing in a VM is good for
> automation or when you have no other choice. Testing on exotic hardware
> might be fun, but has very limited benefit.
> > Sorry for the questions, but this is my first time doing desktop testing.
>
> Very appreciated! I might not spot these questions in the KDE list every
> time, feel free to use the test list or our #quality:fedoraproject.org
> matrix channel, if you see no reply. Thanks.

Thank you for the answers.  I've signed up for the mailling list, so I will
hopefully get these tested in a timely manner.
For those who are wondering, I'm testing on a rpi4, using the tar.gz image.

Troy

[Derek Enz]

I just started to try and get some of this done.

Testing with the same Troy.

Derek

On Wed, Mar 12, 2025 at 10:12 AM Troy Dawson via kde <
[e-mail]> wrote:
> On Wed, Mar 12, 2025 at 1:34 AM Kamil Paral  wrote:
> > On Tue, Mar 11, 2025 at 10:11 PM Troy Dawson via kde <
> > [e-mail]> wrote:
> > > On Tue, Mar 11, 2025 at 9:26 AM Lukas Brabec via kde <
> > > [e-mail]> wrote:
> > > > Hello,
> > > >
> > > > Fedora 42 Candidate Beta-1.3 is ready:
> > > >
> > > > https://lists.fedoraproject.org/archives/list/[e-mail]...
> > > >
> > > > KDE on aarch64 is still completely untested. Please test.
> > > >
> > > > Thanks!
> > > > >
> > >
> > > I'm curious about the Fedora Workstation aarch64 tests.
> > > What hardware is it run on?
> >
> > Some tests run in OpenQA in a virtual machine (those with a robot icon),
> > other tests performed by lbrabec are tested on a RPi4.
> > > Can I use an aarch64 virtual machine?  If yes, can it be running on
> > > x86_64?
> >
> > You can. But cross-arch virtualization will be painfully slow.
> >
> > However, note that the purpose of release validation testing is to check
> > whether the images will work for the majority of our users. So while
> > testing in a VM is theoretically possible for all or most desktop test
> > cases (test cases which specifically require bare metal testing are marked
> > as such), it's not the real-world usage. So at least for a release
> > candidate, we definitely strive for bare metal coverage as much as possible
> > (in the past, we've seen a large number of issues happening only on a RPi,
> > for example).
> >
> > Here's a list of officially supported boards:
> > https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms
> > (Oh yes, the page is horribly outdated. We've asked relevant people so
> > many times to update it. Nevertheless, this is what we have).
> >
> > Most users will run on a RPi3 or RPi4, so that's what we should
> > realistically test, and that's what we do. Testing in a VM is good for
> > automation or when you have no other choice. Testing on exotic hardware
> > might be fun, but has very limited benefit.
> > > Sorry for the questions, but this is my first time doing desktop testing.
> >
> > Very appreciated! I might not spot these questions in the KDE list every
> > time, feel free to use the test list or our #quality:fedoraproject.org
> > matrix channel, if you see no reply. Thanks.
>
> Thank you for the answers.  I've signed up for the mailling list, so I
> will hopefully get these tested in a timely manner.
> For those who are wondering, I'm testing on a rpi4, using the tar.gz image.
>
> Troy
>
> --
> _______________________________________________
> kde mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Kamil Paral]

On Tue, Mar 11, 2025 at 5:26 PM Lukas Brabec via kde <
[e-mail]> wrote:
> Hello,
>
> Fedora 42 Candidate Beta-1.3 is ready:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...

Please note that Beta RC1.3 is still affected by a blocker bug and there
will be Beta RC1.4 later today. However, testing RC1.3 is valuable and we
should be able to transfer most results (and then do just a couple of smoke
tests for RC1.4). See details here:
https://lists.fedoraproject.org/archives/list/[e-mail]/t...

(For anyone interested in KDE testing, it's very useful to subscribe to
test-announce [1] and test [2] lists. Thanks!)

[1]
https://lists.fedoraproject.org/archives/list/[e-mail]...
[2]
https://lists.fedoraproject.org/archives/list/[e-mail]/