Re: fcitx issues on Fedora 34
在 2021-04-29星期四的 11:48 -0400，Leander Hutton via test写道： > On 4/28/21 12:26 PM, Qiyu Yan wrote: > a it will happily stay running until logout. > > > > Try this workaround: > > edit /etc/xdg/startkderc, comment out systemdBoot=true (or set to > > false) > > Setting this to false allows fcitx to load on start up, thanks! I > guess this setting changed between FL33 and FL34? Yes, for KDE session (F34's KDE switched to Wayland for default), the autostart desktop files will be started by systemd-xdg- autostart-generator. As fcitx tries to daemonize it self, systemd treats fcitx as exited after exiting of main-process and killes everything in the cgroup, I guess. That is just a workaround(and to determine the problem), I will try to change the Desktop file to avoid daemonizing. (Or avoid killing by systemd) > > Thanks! > > Leander > > -- > --- > Leander Hutton > lean...@one-button.org > www.one-button.org > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en- > US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraprojec > t.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Qiyu Yan GPG keyid: 0x4FC914F065F2DF12 signature.asc Description: This is a digitally signed message part ___ 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-20210429.1 compose check report
No missing expected images. Failed openQA tests: 1/16 (x86_64), 1/15 (aarch64) New failures (same test not failed in Fedora-IoT-34-20210423.0): ID: 873671 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/873671 Old failures (same test failed in Fedora-IoT-34-20210423.0): ID: 873687 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/873687 Passed openQA tests: 15/16 (x86_64), 14/15 (aarch64) Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: System load changed from 0.05 to 0.30 Previous test data: https://openqa.fedoraproject.org/tests/868176#downloads Current test data: https://openqa.fedoraproject.org/tests/873673#downloads Installed system changes in test aarch64 IoT-dvd_ostree-iso install_default_upload@uefi: System load changed from 0.33 to 0.17 Previous test data: https://openqa.fedoraproject.org/tests/868191#downloads Current test data: https://openqa.fedoraproject.org/tests/873688#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: post go upgrades (re)testing
On Thu, 2021-04-29 at 10:09 +0200, Kamil Paral wrote: > On Wed, Apr 28, 2021 at 6:56 PM Adam Williamson > wrote: > > > We do sort of have this already, because openQA tests all updates, and > > one of the tests it runs on them is an upgrade test. > > > > Now, the iptables thing is interesting, because the logs of that test > > on an F34 update show the issue: > > > > 2021-04-28T04:30:39-0400 WARNING > > Problem: cannot install both iptables-libs-1.8.7-3.fc34.x86_64 and > > iptables-libs-1.8.7-6.fc34.x86_64 > > - package iptables-1.8.7-3.fc34.x86_64 requires iptables-libs(x86-64) = > > 1.8.7-3.fc34, but none of the providers can be installed > > - cannot install the best update candidate for package > > iptables-libs-1.8.5-6.fc33.x86_64 > > - cannot install the best update candidate for package > > iptables-1.8.5-6.fc33.x86_64 > > > > but it's only logged as a WARNING and does not prevent the upgrade > > running. So the test passes. It doesn't even need to use `-- > > allowerasing` so it doesn't register as a soft fail. > > > > I assume that's because iptables from the main (fedora) repo are used > instead. But the upgrade would fail if we added "--best" (I tested it). > Here's a thought. What if we modified the openQA test to first try with > "--best". If there's any error, log it as a softfail, and continue without > it (and if if fails again, log it as a hard error). This way, we can catch > *some* broken updates (it's still possible that one broken update obscures > a second one and we'll not know about the latter - but the benefit is > definitely there). > > If we did it this way, what exactly happens with the softfailed result? > Does it disable Bodhi's autopush? Or does it entirely depend on QA noticing > it soon enough? So I looked into this some more yesterday. openQA did in fact catch this bug, straight up: when the iptables update was initially submitted, an openQA upgrade test failed on exactly this problem. The upgrade succeeded, but the test failed because of the last-step check we do in openQA that, if any package from the update is installed, it is the version from the update that is installed. Because the upgrade pulled in the earlier -3 version and not the -6 version from the update, the test failed. I mentioned this in Bodhi, even, but I noted that if the update was pushed stable *before* F34's final release, the bug should disappear, because the -3 builds would no longer be available as options and dnf would in that case choose to go with -6 and remove iptables (I tested this). Unfortunately, the update was *not* pushed stable before final release, so the -3 builds are in the frozen 'fedora' repo forever now, and we have a more or less insoluble problem (probably the best option is just to put the iptables package back in F34, and re-do this better for F35). See the bug report for more details: https://bugzilla.redhat.com/show_bug.cgi?id=1953178 Given this, I don't think we need to use your idea, since it's demonstrated that openQA *does* actually catch bugs like this already. We just need maintainers to pay more attention and follow up better. > > As for manual testing, what do you think about my previous proposal? > > we could extend our upgrade testing matrices with two variants - one > would test with stable updates, the other would test with updates-testing > enabled Sure, it's possible. It just adds more testing that either a human or a robot needs to do. And, again, it turns out our current testing did actually catch this problem just fine. If anything went wrong, it was the follow-up. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: fcitx issues on Fedora 34
On 4/28/21 12:26 PM, Qiyu Yan wrote: a it will happily stay running until logout. > > Try this workaround: > edit /etc/xdg/startkderc, comment out systemdBoot=true (or set to > false) Setting this to false allows fcitx to load on start up, thanks! I guess this setting changed between FL33 and FL34? Thanks! Leander -- --- Leander Hutton lean...@one-button.org www.one-button.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-32-20210429.0 compose check report
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-20210428.0): ID: 873167 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/873167 ID: 873174 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/873174 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
Fedora-IoT-35-20210429.0 compose check report
No missing expected images. Failed openQA tests: 3/16 (x86_64), 2/15 (aarch64) New failures (same test not failed in Fedora-IoT-35-20210411.0): ID: 873134 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/873134 ID: 873135 Test: x86_64 IoT-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/873135 ID: 873136 Test: x86_64 IoT-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/873136 ID: 873151 Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi URL: https://openqa.fedoraproject.org/tests/873151 Old failures (same test failed in Fedora-IoT-35-20210411.0): ID: 873150 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/873150 Skipped non-gating openQA tests: 26 of 31 -- 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
[Test-Announce] Fedora-IoT 35 RC 20210429.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora-IoT 35 RC 20210429.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 Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/35iot 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-IoT_35_RC_20210429.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_35_RC_20210429.0_General 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-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-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-33-20210429.0 compose check report
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-20210428.0): ID: 872895 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/872895 ID: 872902 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/872902 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: post go upgrades (re)testing
Gmail doesn't display it when you put the quote below your text, let me quote it differently: As for manual testing, what do you think about my previous proposal? "we could extend our upgrade testing matrices with two variants - one would test with stable updates, the other would test with updates-testing enabled" ___ 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: post go upgrades (re)testing
On Wed, Apr 28, 2021 at 6:56 PM Adam Williamson wrote: > We do sort of have this already, because openQA tests all updates, and > one of the tests it runs on them is an upgrade test. > > Now, the iptables thing is interesting, because the logs of that test > on an F34 update show the issue: > > 2021-04-28T04:30:39-0400 WARNING > Problem: cannot install both iptables-libs-1.8.7-3.fc34.x86_64 and > iptables-libs-1.8.7-6.fc34.x86_64 > - package iptables-1.8.7-3.fc34.x86_64 requires iptables-libs(x86-64) = > 1.8.7-3.fc34, but none of the providers can be installed > - cannot install the best update candidate for package > iptables-libs-1.8.5-6.fc33.x86_64 > - cannot install the best update candidate for package > iptables-1.8.5-6.fc33.x86_64 > > but it's only logged as a WARNING and does not prevent the upgrade > running. So the test passes. It doesn't even need to use `-- > allowerasing` so it doesn't register as a soft fail. > I assume that's because iptables from the main (fedora) repo are used instead. But the upgrade would fail if we added "--best" (I tested it). Here's a thought. What if we modified the openQA test to first try with "--best". If there's any error, log it as a softfail, and continue without it (and if if fails again, log it as a hard error). This way, we can catch *some* broken updates (it's still possible that one broken update obscures a second one and we'll not know about the latter - but the benefit is definitely there). If we did it this way, what exactly happens with the softfailed result? Does it disable Bodhi's autopush? Or does it entirely depend on QA noticing it soon enough? As for manual testing, what do you think about my previous proposal? > we could extend our upgrade testing matrices with two variants - one would test with stable updates, the other would test with updates-testing enabled ___ 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-Rawhide-20210428.n.1 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 11 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 32/189 (x86_64), 26/127 (aarch64) New failures (same test not failed in Fedora-Rawhide-20210425.n.0): ID: 872321 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/872321 ID: 872325 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/872325 ID: 872328 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/872328 ID: 872329 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/872329 ID: 872332 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/872332 ID: 872333 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/872333 ID: 872339 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/872339 ID: 872342 Test: x86_64 Server-dvd-iso server_cockpit_updates URL: https://openqa.fedoraproject.org/tests/872342 ID: 872345 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/872345 ID: 872347 Test: x86_64 Server-dvd-iso server_cockpit_basic URL: https://openqa.fedoraproject.org/tests/872347 ID: 872349 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/872349 ID: 872365 Test: x86_64 Workstation-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/872365 ID: 872366 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/872366 ID: 872379 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/872379 ID: 872424 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/872424 ID: 872437 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/872437 ID: 872445 Test: aarch64 Server-dvd-iso release_identification@uefi URL: https://openqa.fedoraproject.org/tests/872445 ID: 872446 Test: aarch64 Server-dvd-iso server_role_deploy_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/872446 ID: 872447 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/872447 ID: 872450 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/872450 ID: 872453 Test: aarch64 Server-dvd-iso modularity_tests@uefi URL: https://openqa.fedoraproject.org/tests/872453 ID: 872456 Test: aarch64 Server-dvd-iso server_freeipa_replication_master@uefi URL: https://openqa.fedoraproject.org/tests/872456 ID: 872459 Test: aarch64 Server-dvd-iso server_freeipa_replication_replica@uefi URL: https://openqa.fedoraproject.org/tests/872459 ID: 872460 Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi URL: https://openqa.fedoraproject.org/tests/872460 ID: 872461 Test: aarch64 Server-dvd-iso server_freeipa_replication_client@uefi URL: https://openqa.fedoraproject.org/tests/872461 ID: 872476 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/872476 ID: 872581 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/872581 ID: 872592 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/872592 Old failures (same test failed in Fedora-Rawhide-20210425.n.0): ID: 872297 Test: x86_64 Server-boot-iso install_default **GATING** URL: https://openqa.fedoraproject.org/tests/872297 ID: 872298 Test: x86_64 Server-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/872298 ID: 872309 Test: x86_64 Server-dvd-iso install_vnc_server URL: https://openqa.fedoraproject.org/tests/872309 ID: 872351 Test: x86_64 Everything-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/872351 ID: 872352 Test: x86_64 Everything-boot-iso install_default **GATING** URL: https://openqa.fedoraproject.org/tests/872352 ID: 872353 Test: x86_64 Everything-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/872353 ID: 872417 Test: aarch64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/872417 ID: 872419 Test: aarch64 Server-dvd-iso install_vnc_server@uefi URL: https://openqa.fedoraproject.org/tests/872419 ID: 872490 Test: x86_64 universal install_kickstart_firewall_disabled **GATING** URL: https://openqa.fedoraproject.org/tests/872490 ID:
Fedora 34 in vmware workstation systemd-oomd 60% CPU consumption
vmware workstation 15 pro, fedora workstation 34 1.2, install opencv, nng,
import cv2
from pynng import Pair1
import numpy as np
address = 'tcp://0.0.0.0:5'
with Pair1(listen = address, polyamorous = True) as svr :
while(True) :
msg = svr.recv_msg()
frame = np.frombuffer(msg.bytes, dtype = np.uint8)
frame = cv2.imdecode(frame, cv2.IMREAD_UNCHANGED)
cv2.namedWindow('window', cv2.WINDOW_GUI_NORMAL)
cv2.imshow('window', frame)
if cv2.waitKey(1) == 27:
break
cv2.destroyAllWindows()
in top command, systemd-oomd Occupy CPU wildly.
___
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: [Test-Announce] Fedora 35 Rawhide 20210428.n.1 nightly compose nominated for testing
Workstation live & Server dvd ISOs work Everything boot does not work On Thu, Apr 29, 2021 at 6:03 AM wrote: > Announcing the creation of a new nightly release validation test event > for Fedora 35 Rawhide 20210428.n.1. 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 > > Test coverage information for the current release can be seen at: > https://openqa.fedoraproject.org/testcase_stats/35 > > 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_35_Rawhide_20210428.n.1_Summary > > The individual test result pages are: > > > https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n.1_Installation > > https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n.1_Base > > https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n.1_Server > > https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n.1_Cloud > > https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n.1_Desktop > > https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n.1_Security_Lab > > Thank you for testing! > -- > Mail generated by relvalconsumer: > https://pagure.io/fedora-qa/relvalconsumer > ___ > test-announce mailing list -- test-annou...@lists.fedoraproject.org > To unsubscribe send an email to > test-announce-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-annou...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-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/de...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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
