[Test-Announce] 2023-04-03 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2023-04-03
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat

Greetings testers!

It's meeting time again!

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Window manager release criterion proposal
3. Fedora 38 status
4. Test Day / community event status
5. Open floor
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net



_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce] 2023-04-03 @ 16:00 UTC - Fedora 38 Blocker Review Meeting

# F38 Blocker Review meeting
# Date: 2023-04-03
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat

Hi folks! We have 2 proposed Final blockers and 2 proposed Final freeze
exception issues to review, so let's have a review meeting.

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F38 can be found on the
wiki [0].

For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good weekend and see you on Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net



_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce] Fedora 38 Branched 20230331.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event
for Fedora 38 Branched 20230331.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20230326.n.1: anaconda-38.23.3-1.fc38.src, 20230331.n.0: anaconda-38.23.4-1.fc38.src
lorax - 20230326.n.1: lorax-38.8-1.fc38.src, 20230331.n.0: lorax-38.10-1.fc38.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/38

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Security_Lab

Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Pine64 RockPro doesn't boot with F38 Beta 1 nor branched 20230326 nightly composed

Peter,

Makes total sense. Good luck!

On 3/31/23 2:37 PM, Peter Boy wrote:
> Hi Adam
>
>> Am 31.03.2023 um 18:28 schrieb Adam Sher <adam@shernet.com>:
>>
>> Hi,
>>
>> I'm not sure if it will help, but I had a lot of problems booting Fedora on the PineBook Pro that were solved by switching to tow-boot instead of u-boot. RockPro64 is on their list of supported devices.
>>
>> https://tow-boot.org/devices/index.html
> thanks for the information. The website makes a very good, systematic and trustworthy impression. For Fedora Server Edition we need a way officially supported in Fedora. But I will try tow in any case. I have there discovered a version for Radxa Rockpi4, where the SPI is not supported by Fedora/u-boot so far. At the moment I use a "wild construction" with Armbian. Maybe it works better and more elegant with tow.
>
>
> Thanks
> Peter
>
>
>
>
>
>
>
> --
> Peter Boy
> https://fedoraproject.org/wiki/User:Pboy
> pboy@fedoraproject.org
>
> Timezone: CET (UTC+1) / CEST (UTC+2)
>
>
> Fedora Server Edition Working Group member
> Fedora docs team contributor
> Java developer and enthusiast
>
>
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Pine64 RockPro doesn't boot with F38 Beta 1 nor branched 20230326 nightly composed

Hi Adam

> Am 31.03.2023 um 18:28 schrieb Adam Sher <adam@shernet.com>:
>
> Hi,
>
> I'm not sure if it will help, but I had a lot of problems booting Fedora on the PineBook Pro that were solved by switching to tow-boot instead of u-boot. RockPro64 is on their list of supported devices.
>
> https://tow-boot.org/devices/index.html

thanks for the information. The website makes a very good, systematic and trustworthy impression. For Fedora Server Edition we need a way officially supported in Fedora. But I will try tow in any case. I have there discovered a version for Radxa Rockpi4, where the SPI is not supported by Fedora/u-boot so far. At the moment I use a "wild construction" with Armbian. Maybe it works better and more elegant with tow.


Thanks
Peter







--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
pboy@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)


Fedora Server Edition Working Group member
Fedora docs team contributor
Java developer and enthusiast


_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Pine64 RockPro doesn't boot with F38 Beta 1 nor branched 20230326 nightly composed

> Am 31.03.2023 um 19:08 schrieb Peter Robinson <pbrobinson@gmail.com>:
>
> On Fri, Mar 31, 2023 at 4:44 PM Peter Boy <pboy@uni-bremen.de> wrote:
>>
>>
>>
>>> Am 29.03.2023 um 19:42 schrieb Dennis Gilmore <dennis@ausil.us>:
>>>
>>>
>>>
>>> On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson <pbrobinson@gmail.com> wrote:
>>>
>>> On Wed, Mar 29, 2023 at 6:18 PM Peter Boy <pboy@uni-bremen.de> wrote:
>>>>
>>>> Just another question: How do I get the Fedora spi image onto the device? As I found on the internet, the description at https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/ for the Pinebook doesn't work for the RockPro64. And indeed, it still does not. In another thread was noted that you are about to update the documentation to describe the process for RockPro64. Unfortunately, I couldn't find it in my internet researches.
>>>
>>> The process is the same as the PBP you just have to adjust the names
>>> so for example "sudo spi-flashing-disk --target=rockpro64-rk3399
>>> --media=/dev/XXX". I have has reports from a number of people it works
>>> just fine.
>>>
>>> I can confirm that this works just fine. I have 2 RockPro64's running Fedora 37 here and using u-boot on SPI from there.
>>
>> It did some experimentation and internet search that took its time.
>>
>> For me, it doesn't work, unfortunately.
>>
>> I get:
>>
>>> U-Boot (2022.10 (Oct 10 2022...)
>>>
>>> Soc: Rockchiop rk3399
>>> Reset cause: POR
>>> Model: Pine64 RockPro64 v2.1
>>> …
>>> MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
>>> Loading Environment from SPIFlash... SF: Detected gd25q128 …
>>> *** Warning - bad CRC, using default environment
>>>
>>> In: serial
>>> Out: vidconsole
>>> starting USB...
>>> ....
>>> scanning usb for storage devices...0 found
>>> Hit any key to stop autoboot:
>>> switch to partitions #0, OK
>>> mmc1 is current device
>>> Scanning mmc 1:1...
>>> Card did not respond to voltage select! : -110
>>> rockship_pcie pcie@f8000000: failed to find ep-gpios property
>>> scanning bus for devices....
>>>
>>> Device 0: unknown device
>>> Device 0: unknown device
>>> rockship_pcie pcie@f8000000: failed to find ep-gpios property
>>> Speed: 1000, full duplex
>>> BOOTP broadcast 1
>>> DHCP client bound to address 192.168.158.150 (6 ms)
>>> *** Warning: no boot file name: using 'COA89E98.img'
>>> …
>>
>>
>> Any idea what I might have missed?
>
> That is working fine, it's not finding the storage/OS, what are you
> trying to boot off, what image are you trying to boot?

On a F37 system (fresh install and fully updated as of today) I did:

[…]# dnf install arm-image-installer uboot-images-armv8
[…]# spi-flashing-disk --target=rockpro64-rk3399 —-media=/dev/mmcblk0

(mmcblk0 is the internal card reader of my test system)

Then I inserted the mSD card into the RockPro64 and turned power on. That produced the output as listed.








>
>> I noticed that a booted F37 shows no SPI storage, only mSD mmcblk0. When I boot the Armbian included in the board delivery, lsblk additionally shows a mtd 0, size 16m.
>>
>> I found an SPI flash at https://github.com/sigmaris/u-boot/releases/download/v2021.04-rockpro64-ci/flash_spi.img.gz
>>
>> The SPI storage was written with it and the board does boot from it. However, Fedora cannot be booted with it, a lack of an EFI partition is complained about and the file system is not recognized.
>>
>> Any help appreciated.
>>





--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
pboy@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)


Fedora Server Edition Working Group member
Fedora docs team contributor
Java developer and enthusiast


_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Pine64 RockPro doesn't boot with F38 Beta 1 nor branched 20230326 nightly composed

On Fri, Mar 31, 2023 at 4:44 PM Peter Boy <pboy@uni-bremen.de> wrote:
>
>
>
> > Am 29.03.2023 um 19:42 schrieb Dennis Gilmore <dennis@ausil.us>:
> >
> >
> >
> > On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson <pbrobinson@gmail.com> wrote:
> >
> > On Wed, Mar 29, 2023 at 6:18 PM Peter Boy <pboy@uni-bremen.de> wrote:
> > >
> > > Just another question: How do I get the Fedora spi image onto the device? As I found on the internet, the description at https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/ for the Pinebook doesn't work for the RockPro64. And indeed, it still does not. In another thread was noted that you are about to update the documentation to describe the process for RockPro64. Unfortunately, I couldn't find it in my internet researches.
> >
> > The process is the same as the PBP you just have to adjust the names
> > so for example "sudo spi-flashing-disk --target=rockpro64-rk3399
> > --media=/dev/XXX". I have has reports from a number of people it works
> > just fine.
> >
> > I can confirm that this works just fine. I have 2 RockPro64's running Fedora 37 here and using u-boot on SPI from there.
>
> It did some experimentation and internet search that took its time.
>
> For me, it doesn't work, unfortunately.
>
> I get:
>
> > U-Boot (2022.10 (Oct 10 2022...)
> >
> > Soc: Rockchiop rk3399
> > Reset cause: POR
> > Model: Pine64 RockPro64 v2.1
> > …
> > MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
> > Loading Environment from SPIFlash... SF: Detected gd25q128 …
> > *** Warning - bad CRC, using default environment
> >
> > In: serial
> > Out: vidconsole
> > starting USB...
> > ....
> > scanning usb for storage devices...0 found
> > Hit any key to stop autoboot:
> > switch to partitions #0, OK
> > mmc1 is current device
> > Scanning mmc 1:1...
> > Card did not respond to voltage select! : -110
> > rockship_pcie pcie@f8000000: failed to find ep-gpios property
> > scanning bus for devices....
> >
> > Device 0: unknown device
> > Device 0: unknown device
> > rockship_pcie pcie@f8000000: failed to find ep-gpios property
> > Speed: 1000, full duplex
> > BOOTP broadcast 1
> > DHCP client bound to address 192.168.158.150 (6 ms)
> > *** Warning: no boot file name: using 'COA89E98.img'
> > …
>
>
> Any idea what I might have missed?

That is working fine, it's not finding the storage/OS, what are you
trying to boot off, what image are you trying to boot?

> I noticed that a booted F37 shows no SPI storage, only mSD mmcblk0. When I boot the Armbian included in the board delivery, lsblk additionally shows a mtd 0, size 16m.
>
> I found an SPI flash at https://github.com/sigmaris/u-boot/releases/download/v2021.04-rockpro64-ci/flash_spi.img.gz
>
> The SPI storage was written with it and the board does boot from it. However, Fedora cannot be booted with it, a lack of an EFI partition is complained about and the file system is not recognized.
>
> Any help appreciated.
>
>
> @Dennis Gilmore
> > It reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
>
> I would appreciate that, too. And just in case that you used Fedora Server, I would like to publish it as part of the Fedora Server documentation (). I can help with the technical part. I'm making an effort to give more consideration to SBCs right now.
>
>
> Peter
>
>
>
>
>
>
>
>
> --
> Peter Boy
> https://fedoraproject.org/wiki/User:Pboy
> pboy@fedoraproject.org
>
> Timezone: CET (UTC+1) / CEST (UTC+2)
>
>
> Fedora Server Edition Working Group member
> Fedora docs team contributor
> Java developer and enthusiast
>
>
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue