On Mon, 2017-05-22 at 17:17 -0700, Ryan wrote: > Hello everyone, Hi Ryan! > I gave a shot at running a verification test. I was looking at > Fedora_26_Branched_20170513.n.0 installation Should I be testing the > milestones labeled as Final in the nightly builds? Yes, absolutely! If a test is labeled as Final, that means that a failure of the test likely blocks the Final release. But that doesn't mean we should only run the Alpha tests on Alpha candidates and only the Alpha+Beta tests on Beta candidates; we should run as many of the tests as possible on all candidates, because it's much better to find and fix *all* the important bugs early. If we can find a Final blocker now and fix it, that's so much the better than waiting till after Beta comes out :) > I hope I did this the right way. Here is what I did. > Went to Fedora_26_Branched_20170513.n.0 installation, Image sanity, > and chose the repoclosure test case. Followed the procedures and got > the results below: > Added myrepo repo from /media > Reading in repository metadata - please wait.... > Checking Dependencies > Repos looked at: 1 > myrepo > Num Packages in Repos: 2836 > package: python-smbios-2.3.0-4.fc26.x86_64 from myrepo > unresolved deps: > python-ctypes > Which shows one unresolved dependency. If I am correct this would > qualify as a automatic blocker for the final release and I should > submit a bug report and update the test results page to show failed? That sounds exactly right, yep! Thanks very much for running this. A similar check is actually run on each compose automatically by releng, and that confirms your test: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170523.n.0/logs/x86_64/repoclosure-Server.x86_64.log I keep meaning to set up a little thing to take the releng test result and report it to the wiki, but haven't got around to it yet. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
