test-announce April 2017

test-announce@lists.fedoraproject.org

5 participants
17 discussions

2017-05-01 @ 16:00 UTC ** Fedora Blocker Review Meeting
by Mike Ruckman 30 Apr '17

30 Apr '17

# F26 Blocker Review meeting # Date: 2017-05-01 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Greetings testers! Last week was a busy week and we had 5 proposed blockers for Beta and 6 proposed blockers for Final. If you have time between now and Monday to go through the list of blockers, please do so. You can find the full list here: https://qa.fedoraproject.org/blockerbugs/ . 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 F26 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 // Mike -- Fedora QA

1 0

Proposal to CANCEL: 2017-05-01 Fedora QA Meeting
by Adam Williamson 28 Apr '17

28 Apr '17

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have anything significant to discuss. If you think there is something we need to discuss, please do reply to this mail and we can go ahead and schedule the meeting! Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

openQA test results for critpath updates now shown in Bodhi
by Adam Williamson 24 Apr '17

24 Apr '17

Hi folks! I thought this was worth sending out an announcement about so as many packagers and testers as possible are aware of it. With the rollout of Bodhi 2.6.0 to production today, openQA test results for critpath updates now appear in the Bodhi webUI! Click the 'Automated Tests' tab on any critical path update (from the last two months or so) and you should see, as well as the 'dist.*' tests you're probably familiar with that are run by Taskotron, results for several 'update.*' tests. These are the openQA test results. Clicking any result will take you to the openQA webUI page for that job. If you're investigating a failure, look for thumbnails with a *red* border. Usually, the first one of these will be the attempted image match or console command that did not give the expected result. If you can't understand a failure, please do come ask on test@ or in #fedora-qa . Myself and garretraziel (Jan Sedlak) should be able to explain. This isn't a perfect test system, yet; there have been and will continue to be 'false' failures, where something goes wrong in the test process itself or the test just hits some transient bug that isn't actually caused by the update. Because of this, we wrote an openQA plugin that automatically retries all failed update tests one time, but sometimes we get unlucky and a false failure happens again on the retry. This is quite common for Fedora 26 updates; there seem to be several of these transient bugs in F26 at present, meaning sometimes the test VM just doesn't boot successfully, sometimes GNOME crashes, and so on. If you see a 'red' screenshot which is just a partially-completed bootsplash screen, or the GDM login screen, this may be what happened. Notably, *any* failure before the _advisory_update step cannot possibly be a bug in the update, as nothing from the update is actually installed until near the end of that step. It's not currently possible for anyone but openQA admins to re-run individual tests. You can cause *all* the openQA tests for your update to be re-run by editing the update in any way (*any* edit event triggers a re-run of the tests, not just changes to the update's package manifest), but please be a bit sparing with this, as openQA doesn't have unlimited capacity. For now you can, again, ask Jan or I to re-run a single test if you'd like this. We will endeavour to set up some kind of re-run request system in future. Just like the taskotron results, at present these results are entirely advisory. They do not have any effect on whether or when you can push your update stable. But we set up this system to help out packagers, so I hope you'll find it useful to keep an eye on the results and take a look at any failures to see if they may indicate a bug in the update. Once again, please do ask for any help you need in interpreting or understanding the results. And please do send any suggestions, comments or complaints our way! And just to be clear, these tests are currently run only on *critical path* updates. If your update does not include a critical path package, the tests will not be run. I'm thinking of implementing some sort of 'whitelist' system for listing or otherwise marking non-critpath packages for which we want to run some or all of the tests; for instance, it would make a lot of sense to run the FreeIPA tests for any package in the FreeIPA stack. But that's not implemented yet. We don't just run the tests on *all* updates because we simply don't have the capacity to do so at present. I have written a blog post about this, with some more information, including a brief explanation of what the current set of update tests covers, here: https://www.happyassassin.net/2017/04/24/automated-critical-path-update-fun… -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2017-04-24 @ 16:00 UTC ** Blocker Review Meeting
by Mike Ruckman 22 Apr '17

22 Apr '17

# F26 Blocker Review meeting # Date: 2017-04-24 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Greetings testers! It's that time of the week again: Blocker Review time! We got a break last week, but now we have a couple to look at - it should still be a shorter meeting though. We currently have 2 proposals for Beta and 3 for Final. If you have time between now and Monday to go through the list of blockers, please do so. You can find the full list here: https://qa.fedoraproject.org/blockerbugs/ . 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 F26 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 // Mike -- Fedora QA

1 0

2017-04-24 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson 22 Apr '17

22 Apr '17

# Fedora Quality Assurance Meeting # Date: 2017-04-24 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! I don't have a big agenda this week, but figured we might as well get together for a quick check-in. We might go less than an hour if there isn't a lot to talk about. 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. Fedora 26 status 3. Test Day status 4. Action ideas? 5. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora 26 Branched 20170420.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 20 Apr '17

20 Apr '17

Announcing the creation of a new nightly release validation test event for Fedora 26 Branched 20170420.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: pykickstart - 20170416.n.0: pykickstart-2.33-2.fc26.src, 20170420.n.0: pykickstart-2.34-1.fc26.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26 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_26_Branched_20170420.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170420.n.0… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

[Test Day] Fedora Media Writer 2017-04-20
by Sumantro Mukherjee 18 Apr '17

18 Apr '17

Hey Testers, Thursday 2017-04-20 will be Fedora Media Writer Test Day[1]! As part of this planned Change[2] for Fedora 26, So this is an important Test Day! Test Day will focus on Fedora Media Writer. Fedora Media Writer, is used for creating bootable flashdrives on different operating systems and architectures. The tool is intended to be provided as the primary download option for Fedora 25, with the aim of lowering the barrier for potential users to try and install Fedora. In this test day, we aim to test both Fedora 25 and Fedora 26 Pre-Release boot-media creation on Windows, OS X, and Fedora, specifically targeting creation of ARM-bootable media to see whether it's working well enough and catch any remaining issues. It's also pretty easy to join in: all you'll need is 4GB flash drive (With all it's *data backed up*). As always, the event will be in #fedora-test-day on Freenode IRC. [1]: https://fedoraproject.org/wiki/Test_Day:2017-04-20_Fedora_Media_Writer [2]: https://fedoraproject.org/wiki/Changes/ArmSupportInFmw -- Sumantro On Behalf of Fedora QA team

1 0

2017-04-17 @ 16:00 UTC ** Proposal to Cancel Blocker Review
by Mike Ruckman 16 Apr '17

16 Apr '17

Greetings testers! I apologize for the late notice (had a holiday weekend and lost track of time), but I don't see a reason to have a Blocker Review Meeting tomorrow since we've only 1/1 proposed blockers for Beta/Final. If you feel strongly that we have the blocker review tomorrow for those two bugs, please reply to the list! Thanks and see you on IRC! // Mike -- Fedora QA

1 0

Fedora 26 Branched 20170416.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 16 Apr '17

16 Apr '17

Announcing the creation of a new nightly release validation test event for Fedora 26 Branched 20170416.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 - 20170413.n.0: anaconda-26.21.1-1.fc26.src, 20170416.n.0: anaconda-26.21.3-1.fc26.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26 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_26_Branched_20170416.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170416.n.0… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

Proposal to CANCEL: 2017-04-17 Fedora QA Meeting
by Adam Williamson 15 Apr '17

15 Apr '17

Hi folks! I'm proposing we cancel the QA meeting on Monday. It's a holiday in many parts of the world, and we don't have anything specific to discuss, I don't think. If you think there is something we need to discuss, please do reply to this mail and we can go ahead and schedule the meeting! Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce April 2017