Fedora 29-20180917.n.0 compose check report
No missing expected images. Failed openQA tests: 3/132 (x86_64), 1/2 (arm) ID: 281610 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/281610 ID: 281626 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/281626 ID: 281629 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/281629 ID: 281632 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/281632 Soft failed openQA tests: 4/132 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 281594 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/281594 ID: 281595 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/281595 ID: 281619 Test: x86_64 KDE-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/281619 ID: 281657 Test: x86_64 universal upgrade_minimal_64bit URL: https://openqa.fedoraproject.org/tests/281657 ID: 281673 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/281673 ID: 281705 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/281705 Passed openQA tests: 125/132 (x86_64), 22/24 (i386) Skipped openQA tests: 1 of 158 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 29 compose report: 20180917.n.0 changes
OLD: Fedora-29-20180916.n.0 NEW: Fedora-29-20180917.n.0 = SUMMARY = Added images:3 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Scientific vagrant-libvirt x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-29-20180917.n.0.x86_64.vagrant-libvirt.box Image: Design_suite live i386 Path: Labs/i386/iso/Fedora-Design_suite-Live-i386-29-20180917.n.0.iso Image: Scientific vagrant-virtualbox x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-29-20180917.n.0.x86_64.vagrant-virtualbox.box = DROPPED IMAGES = Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-29-20180916.n.0.s390x.tar.xz = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Fedora 29 Silverblue Test Day 2018-09-20
Everything in my normal workflow is now working in Silverblue 29 except using my WiFi adapter as a hotspot and playing videos on Twitter in Firefox. On Sun, Sep 16, 2018 at 11:43 PM, M. Edward (Ed) Borasky wrote: > OK - downloading it now! > > On Sun, Sep 16, 2018 at 11:42 PM, Sumantro Mukherjee > wrote: >> >> >> - Original Message - >>> From: "M. Edward (Ed) Borasky" >>> To: "For testing and quality assurance of Fedora releases" >>> >>> Sent: Monday, September 17, 2018 11:53:29 AM >>> Subject: Re: Fedora 29 Silverblue Test Day 2018-09-20 >>> >>> On Sun, Sep 16, 2018 at 11:18 PM, Sumantro Mukherjee >>> wrote: >>> > Hey All, >>> > >>> > We have Silverblue Test Day coming up on 2018-09-20! >>> > Fedora Silverblue[0] is a new variant of Fedora Workstation with >>> > rpm-ostree >>> > at its core to provide fully atomic upgrades. >>> > Furthermore, Fedora Silverblue is immutable and upgrades as a whole, >>> > providing easy rollbacks from updates if something goes wrong. >>> > Fedora Silverblue is great for developers using Fedora with good support >>> > for container-focused workflows. >>> > >>> > Additionally, Fedora Silverblue delivers desktop applications as >>> > Flatpaks. >>> > This provides better isolation / sandboxing of applications, and >>> > streamlines updating applications — Flatpaks can be safely updated without >>> > reboot. >>> > >>> > Next Thursday, September 20 2018, Team Silverblue and Fedora QA are >>> > holding >>> > a Test Day >>> > for users to try out and test this new Fedora Workstation variant. >>> > >>> > The wiki page[1] for the silverblue has a lot of good information on what >>> > and how to test. >>> > After you’ve done some testing, you can log your results in the test day >>> > web application[2]. >>> > >>> > If you’re available on or around the day of the event, please do some >>> > testing and report your results. >>> > >>> > [0]https://silverblue.fedoraproject.org/ >>> > [1]https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday >>> > [2]http://testdays.fedorainfracloud.org/events/47 >>> > >>> > Thanks >>> > //sumantro >>> > ___ >>> > test mailing list -- test@lists.fedoraproject.org >>> > To unsubscribe send an email to test-le...@lists.fedoraproject.org >>> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >>> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> > List Archives: >>> > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >>> >>> Will there be install ISO files that have passed some kind of testing? >>> I've been installing Silverblue 28 (which works) and rebasing to >>> Silverblue 29 (which hangs in GDM on one of my machines). >>> >>> -- >>> Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics >>> >>> Markovs of the world, unite! You have nothing to lose but your chains! >>> ___ >>> test mailing list -- test@lists.fedoraproject.org >>> To unsubscribe send an email to test-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >>> >> >> Hey, we are testing >> https://dl.fedoraproject.org/pub/alt/stage/29_Beta-1.3/Silverblue/x86_64/iso/ >> >> if there are any bugs you manage to find,can you please report them to >> Bugzilla? >> >> >> Thanks >> //sumantro >> ___ >> test mailing list -- test@lists.fedoraproject.org >> To unsubscribe send an email to test-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > > > > -- > Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics > > Markovs of the world, unite! You have nothing to lose but your chains! -- Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics Markovs of the world, unite! You have nothing to lose but your chains! ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Forcibly resetting doesn't work anymore?
On Mon, Sep 17, 2018 at 5:27 AM, Michael Schwendt wrote: > Resetting "forcibly" by hitting Ctrl+Alt+Del more than seven times within two > seconds used to work. Now I only get a message about it, but nothing happens. > > The reason I need to reset the machine like that is that simply choosing > the "Restart" option inside GNOME Shell runs into annoying systemd timeouts > while waiting for jobs, such as user manager. That takes much too long. Dunno about the keyboard shortcut but I'd say, why is the delay happening? Here's a guide for getting better shutdown time information in the journal. https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 And then 'sudo reboot -f' will do an abrupt reboot that sidesteps systemd. And yet another way to hand it is to insert this line into /etc/systemd/logind.conf KillUserProcesses=yes When you logout (which happens right after you choose restart from GUI), this will forcibly kill all the user processes in the login session. Just be aware it'll kill everything including screen and tmux sessions when you log out. -- Chris Murphy ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Forcibly resetting doesn't work anymore?
On 9/17/18 4:27 AM, Michael Schwendt wrote: Resetting "forcibly" by hitting Ctrl+Alt+Del more than seven times within two seconds used to work. Now I only get a message about it, but nothing happens. The reason I need to reset the machine like that is that simply choosing the "Restart" option inside GNOME Shell runs into annoying systemd timeouts while waiting for jobs, such as user manager. That takes much too long. I wasn't aware that it ever worked like that. You could just switch to a console using CTRL-ALT-F3 and then CTRL-ALT-DEL will work the first time. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Proposal to modify release criteria for fwraid
On Mon, Sep 17, 2018 at 9:56 AM, Adam Williamson wrote: > On Mon, 2018-09-17 at 17:25 +0200, Kamil Paral wrote: >> On Mon, Sep 17, 2018 at 2:45 PM Stephen Gallagher >> wrote: >> >> > On Mon, Sep 17, 2018 at 5:16 AM Petr Šabata wrote: >> > >> > > I hope this won't just mean we discover the problems later, in practice. >> > >> > The policy of Fedora QA is to run all of the GA-blocking tests at Beta as >> > well. >> > >> >> My goal has always been to run all Final testcases with the publicly >> released Beta image as soon as possible. I don't think we're too successful >> at running all Final testcases with pre-Beta images or Beta RCs. I'm not >> aware of any policy per say. But we certainly try. > > I've been saying for a long time that we ought to be doing that, and > it's why we started doing validation events for nightly composes > throughout the cycle (instead of starting shortly before Alpha as we > used to). I definitely would like us to be running the validation tests > a long time before Beta freeze. Maybe there needs to be a milestone for it? Something like alpha in terms of the timing, but non-blocking since there's no release specific to this hypothetical milestone, but does give you the resources to plan for and implement it. -- Chris Murphy ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Proposal to modify release criteria for fwraid
On Mon, 2018-09-17 at 08:56 -0700, Adam Williamson wrote: > On Mon, 2018-09-17 at 17:25 +0200, Kamil Paral wrote: > > On Mon, Sep 17, 2018 at 2:45 PM Stephen Gallagher > > wrote: > > > > > On Mon, Sep 17, 2018 at 5:16 AM Petr Šabata wrote: > > > > > > > I hope this won't just mean we discover the problems later, in practice. > > > > > > The policy of Fedora QA is to run all of the GA-blocking tests at Beta as > > > well. > > > > > > > My goal has always been to run all Final testcases with the publicly > > released Beta image as soon as possible. I don't think we're too successful > > at running all Final testcases with pre-Beta images or Beta RCs. I'm not > > aware of any policy per say. But we certainly try. > > I've been saying for a long time that we ought to be doing that, and > it's why we started doing validation events for nightly composes > throughout the cycle (instead of starting shortly before Alpha as we > used to). I definitely would like us to be running the validation tests > a long time before Beta freeze. Sorry, though to clarify a bit more: we *aim* to run as many of the tests as possible, as early as possible. But it's an aspirational thing. We don't *commit* to having the Final tests run by Beta. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Nvidia and Fedora current state
On Mon, Sep 17, 2018 at 10:52 AM Michael Schwendt wrote: > The F28 reference installation with rpmfusion's nvidia driver packages > (based on akmod I think) has stopped working all of a sudden, warns about > falling back to nouveau and then crashes upon gdm login. > The errors messages are not helpful and it took me a while to figure out but when I had that problem it's because my card was no longer compatible with the latest drivers (GTS-450) and as soon as I downloaded one of the older versions and rerun akmods it worked. Thanks, Richard ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Proposal to modify release criteria for fwraid
On Mon, 2018-09-17 at 17:25 +0200, Kamil Paral wrote: > On Mon, Sep 17, 2018 at 2:45 PM Stephen Gallagher > wrote: > > > On Mon, Sep 17, 2018 at 5:16 AM Petr Šabata wrote: > > > > > I hope this won't just mean we discover the problems later, in practice. > > > > The policy of Fedora QA is to run all of the GA-blocking tests at Beta as > > well. > > > > My goal has always been to run all Final testcases with the publicly > released Beta image as soon as possible. I don't think we're too successful > at running all Final testcases with pre-Beta images or Beta RCs. I'm not > aware of any policy per say. But we certainly try. I've been saying for a long time that we ought to be doing that, and it's why we started doing validation events for nightly composes throughout the cycle (instead of starting shortly before Alpha as we used to). I definitely would like us to be running the validation tests a long time before Beta freeze. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Nvidia and Fedora current state
On Sun, 16 Sep 2018 16:55:05 -0700, M. Edward (Ed) Borasky wrote: > I have no interest in running Fedora on that machine. I have a working > system with Arch and unless that changes I don't see any reason to > troubleshoot other distros. You are posting to Fedora test@ list, on the other hand, and the subject in question is unrelated to whether you want to run Fedora. While it may be seen as relevant to tell how other dists perform with the same hardware, above post is non-productive. The F28 reference installation with rpmfusion's nvidia driver packages (based on akmod I think) has stopped working all of a sudden, warns about falling back to nouveau and then crashes upon gdm login. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Proposal to modify release criteria for fwraid
On Mon, Sep 17, 2018 at 2:45 PM Stephen Gallagher wrote: > On Mon, Sep 17, 2018 at 5:16 AM Petr Šabata wrote: > > > > > I hope this won't just mean we discover the problems later, in practice. > > > The policy of Fedora QA is to run all of the GA-blocking tests at Beta as > well. > My goal has always been to run all Final testcases with the publicly released Beta image as soon as possible. I don't think we're too successful at running all Final testcases with pre-Beta images or Beta RCs. I'm not aware of any policy per say. But we certainly try. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 29 successful testing of 1.1.1 to create EDDSA certificates
Fedora 29 beta just provided (in testing-update repo): openssl-1.1.1-2.fc29.armv7hl.rpm Against this version, I successfully produced my ED25519 pki per: https://github.com/rgmhtt/draft-moskowitz-eddsa-pki I have some minor textual edits to make in the draft and then submit it. Then I can also go to IEEE 802.1 and raise up adding EDDSA support to IEEE 802.1AR. Thank you for providing the code! ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Proposal to modify release criteria for fwraid
On Mon, Sep 17, 2018 at 5:16 AM Petr Šabata wrote: > > On Fri, Sep 14, 2018 at 10:22:12AM -0400, Stephen Gallagher wrote: > > At yesterday's F29 Go/No-Go meeting, we discussed the blocker status > > of BZ #1628192 - Fedora 29 installation cannot see a firmware RAID > > device. While the blocker criteria clearly states that this should be > > a blocker for Beta, many of the people present at the meeting > > disagreed, for a variety of reasons. > > > > * Hardware supporting fwraid is considerably less pervasive than it > > was when the criterion was written > > > > * Testing this criterion can only be done with install media, which > > limits our testing pool to the very dedicated members of Fedora QA. > > Yes, anyone *can* download a nightly compose and try it, but in > > practice this tends to be limited to the core testers. The majority of > > testing that this feature will get will tend to happen as people try > > out the Beta release. > > > > To that end, I'd like to propose that we make the following change to > > the criteria going forward: > > > > "The blocking criterion for successful installation atop a firmware > > RAID array is moved to the GA release criteria." > > I hope this won't just mean we discover the problems later, in practice. The policy of Fedora QA is to run all of the GA-blocking tests at Beta as well. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Forcibly resetting doesn't work anymore?
Resetting "forcibly" by hitting Ctrl+Alt+Del more than seven times within two seconds used to work. Now I only get a message about it, but nothing happens. The reason I need to reset the machine like that is that simply choosing the "Restart" option inside GNOME Shell runs into annoying systemd timeouts while waiting for jobs, such as user manager. That takes much too long. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Neverending CPU usage by gnome-software and packagekit
$ rpm -q gnome-software PackageKit gnome-software-3.30.0-1.fc29.x86_64 PackageKit-1.1.10-4.fc29.x86_64 It's over 35 minutes since booting F29, and the two processes are still working on something. What is it? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Proposal to modify release criteria for fwraid
On Fri, Sep 14, 2018 at 10:22:12AM -0400, Stephen Gallagher wrote: > At yesterday's F29 Go/No-Go meeting, we discussed the blocker status > of BZ #1628192 - Fedora 29 installation cannot see a firmware RAID > device. While the blocker criteria clearly states that this should be > a blocker for Beta, many of the people present at the meeting > disagreed, for a variety of reasons. > > * Hardware supporting fwraid is considerably less pervasive than it > was when the criterion was written > > * Testing this criterion can only be done with install media, which > limits our testing pool to the very dedicated members of Fedora QA. > Yes, anyone *can* download a nightly compose and try it, but in > practice this tends to be limited to the core testers. The majority of > testing that this feature will get will tend to happen as people try > out the Beta release. > > To that end, I'd like to propose that we make the following change to > the criteria going forward: > > "The blocking criterion for successful installation atop a firmware > RAID array is moved to the GA release criteria." I hope this won't just mean we discover the problems later, in practice. P signature.asc Description: PGP signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Fedora 29 Silverblue Test Day 2018-09-20
OK - downloading it now! On Sun, Sep 16, 2018 at 11:42 PM, Sumantro Mukherjee wrote: > > > - Original Message - >> From: "M. Edward (Ed) Borasky" >> To: "For testing and quality assurance of Fedora releases" >> >> Sent: Monday, September 17, 2018 11:53:29 AM >> Subject: Re: Fedora 29 Silverblue Test Day 2018-09-20 >> >> On Sun, Sep 16, 2018 at 11:18 PM, Sumantro Mukherjee >> wrote: >> > Hey All, >> > >> > We have Silverblue Test Day coming up on 2018-09-20! >> > Fedora Silverblue[0] is a new variant of Fedora Workstation with rpm-ostree >> > at its core to provide fully atomic upgrades. >> > Furthermore, Fedora Silverblue is immutable and upgrades as a whole, >> > providing easy rollbacks from updates if something goes wrong. >> > Fedora Silverblue is great for developers using Fedora with good support >> > for container-focused workflows. >> > >> > Additionally, Fedora Silverblue delivers desktop applications as Flatpaks. >> > This provides better isolation / sandboxing of applications, and >> > streamlines updating applications — Flatpaks can be safely updated without >> > reboot. >> > >> > Next Thursday, September 20 2018, Team Silverblue and Fedora QA are holding >> > a Test Day >> > for users to try out and test this new Fedora Workstation variant. >> > >> > The wiki page[1] for the silverblue has a lot of good information on what >> > and how to test. >> > After you’ve done some testing, you can log your results in the test day >> > web application[2]. >> > >> > If you’re available on or around the day of the event, please do some >> > testing and report your results. >> > >> > [0]https://silverblue.fedoraproject.org/ >> > [1]https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday >> > [2]http://testdays.fedorainfracloud.org/events/47 >> > >> > Thanks >> > //sumantro >> > ___ >> > test mailing list -- test@lists.fedoraproject.org >> > To unsubscribe send an email to test-le...@lists.fedoraproject.org >> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> > List Archives: >> > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >> >> Will there be install ISO files that have passed some kind of testing? >> I've been installing Silverblue 28 (which works) and rebasing to >> Silverblue 29 (which hangs in GDM on one of my machines). >> >> -- >> Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics >> >> Markovs of the world, unite! You have nothing to lose but your chains! >> ___ >> test mailing list -- test@lists.fedoraproject.org >> To unsubscribe send an email to test-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org >> > > Hey, we are testing > https://dl.fedoraproject.org/pub/alt/stage/29_Beta-1.3/Silverblue/x86_64/iso/ > > if there are any bugs you manage to find,can you please report them to > Bugzilla? > > > Thanks > //sumantro > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org -- Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics Markovs of the world, unite! You have nothing to lose but your chains! ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Fedora 29 Silverblue Test Day 2018-09-20
- Original Message - > From: "M. Edward (Ed) Borasky" > To: "For testing and quality assurance of Fedora releases" > > Sent: Monday, September 17, 2018 11:53:29 AM > Subject: Re: Fedora 29 Silverblue Test Day 2018-09-20 > > On Sun, Sep 16, 2018 at 11:18 PM, Sumantro Mukherjee > wrote: > > Hey All, > > > > We have Silverblue Test Day coming up on 2018-09-20! > > Fedora Silverblue[0] is a new variant of Fedora Workstation with rpm-ostree > > at its core to provide fully atomic upgrades. > > Furthermore, Fedora Silverblue is immutable and upgrades as a whole, > > providing easy rollbacks from updates if something goes wrong. > > Fedora Silverblue is great for developers using Fedora with good support > > for container-focused workflows. > > > > Additionally, Fedora Silverblue delivers desktop applications as Flatpaks. > > This provides better isolation / sandboxing of applications, and > > streamlines updating applications — Flatpaks can be safely updated without > > reboot. > > > > Next Thursday, September 20 2018, Team Silverblue and Fedora QA are holding > > a Test Day > > for users to try out and test this new Fedora Workstation variant. > > > > The wiki page[1] for the silverblue has a lot of good information on what > > and how to test. > > After you’ve done some testing, you can log your results in the test day > > web application[2]. > > > > If you’re available on or around the day of the event, please do some > > testing and report your results. > > > > [0]https://silverblue.fedoraproject.org/ > > [1]https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday > > [2]http://testdays.fedorainfracloud.org/events/47 > > > > Thanks > > //sumantro > > ___ > > test mailing list -- test@lists.fedoraproject.org > > To unsubscribe send an email to test-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > > Will there be install ISO files that have passed some kind of testing? > I've been installing Silverblue 28 (which works) and rebasing to > Silverblue 29 (which hangs in GDM on one of my machines). > > -- > Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics > > Markovs of the world, unite! You have nothing to lose but your chains! > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > Hey, we are testing https://dl.fedoraproject.org/pub/alt/stage/29_Beta-1.3/Silverblue/x86_64/iso/ if there are any bugs you manage to find,can you please report them to Bugzilla? Thanks //sumantro ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Fedora 29 Silverblue Test Day 2018-09-20
On Sun, Sep 16, 2018 at 11:18 PM, Sumantro Mukherjee wrote: > Hey All, > > We have Silverblue Test Day coming up on 2018-09-20! > Fedora Silverblue[0] is a new variant of Fedora Workstation with rpm-ostree > at its core to provide fully atomic upgrades. > Furthermore, Fedora Silverblue is immutable and upgrades as a whole, > providing easy rollbacks from updates if something goes wrong. > Fedora Silverblue is great for developers using Fedora with good support for > container-focused workflows. > > Additionally, Fedora Silverblue delivers desktop applications as Flatpaks. > This provides better isolation / sandboxing of applications, and streamlines > updating applications — Flatpaks can be safely updated without reboot. > > Next Thursday, September 20 2018, Team Silverblue and Fedora QA are holding a > Test Day > for users to try out and test this new Fedora Workstation variant. > > The wiki page[1] for the silverblue has a lot of good information on what and > how to test. > After you’ve done some testing, you can log your results in the test day web > application[2]. > > If you’re available on or around the day of the event, please do some testing > and report your results. > > [0]https://silverblue.fedoraproject.org/ > [1]https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday > [2]http://testdays.fedorainfracloud.org/events/47 > > Thanks > //sumantro > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Will there be install ISO files that have passed some kind of testing? I've been installing Silverblue 28 (which works) and rebasing to Silverblue 29 (which hangs in GDM on one of my machines). -- Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics Markovs of the world, unite! You have nothing to lose but your chains! ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 29 Silverblue Test Day 2018-09-20
Hey All, We have Silverblue Test Day coming up on 2018-09-20! Fedora Silverblue[0] is a new variant of Fedora Workstation with rpm-ostree at its core to provide fully atomic upgrades. Furthermore, Fedora Silverblue is immutable and upgrades as a whole, providing easy rollbacks from updates if something goes wrong. Fedora Silverblue is great for developers using Fedora with good support for container-focused workflows. Additionally, Fedora Silverblue delivers desktop applications as Flatpaks. This provides better isolation / sandboxing of applications, and streamlines updating applications — Flatpaks can be safely updated without reboot. Next Thursday, September 20 2018, Team Silverblue and Fedora QA are holding a Test Day for users to try out and test this new Fedora Workstation variant. The wiki page[1] for the silverblue has a lot of good information on what and how to test. After you’ve done some testing, you can log your results in the test day web application[2]. If you’re available on or around the day of the event, please do some testing and report your results. [0]https://silverblue.fedoraproject.org/ [1]https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday [2]http://testdays.fedorainfracloud.org/events/47 Thanks //sumantro ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 29-20180916.n.0 compose check report
No missing expected images. Failed openQA tests: 5/132 (x86_64), 1/2 (arm) ID: 281187 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/281187 ID: 281203 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/281203 ID: 281206 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/281206 ID: 281209 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/281209 ID: 281253 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/281253 ID: 281273 Test: x86_64 universal install_shrink_ext4 URL: https://openqa.fedoraproject.org/tests/281273 Soft failed openQA tests: 3/132 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 281171 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/281171 ID: 281172 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/281172 ID: 281177 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/281177 ID: 281249 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/281249 ID: 281250 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/281250 Passed openQA tests: 124/132 (x86_64), 22/24 (i386) Skipped openQA tests: 1 of 158 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
