Fedora Rawhide-20161214.n.1 compose check report
Missing expected images: Workstation live i386 Kde live x86_64 Workstation live x86_64 Kde live i386 Failed openQA tests: 10/80 (x86_64), 1/15 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20161211.n.0): ID: 51305 Test: x86_64 universal install_shrink_ext4 URL: https://openqa.fedoraproject.org/tests/51305 ID: 51309 Test: x86_64 universal install_kickstart_firewall_disabled URL: https://openqa.fedoraproject.org/tests/51309 ID: 51313 Test: x86_64 universal install_rescue_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/51313 Old failures (same test failed in Rawhide-20161211.n.0): ID: 51234 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/51234 ID: 51247 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/51247 ID: 51282 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/51282 ID: 51297 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/51297 ID: 51298 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/51298 ID: 51300 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/51300 ID: 51302 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/51302 ID: 51312 Test: x86_64 universal install_rescue_encrypted URL: https://openqa.fedoraproject.org/tests/51312 ID: 51324 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/51324 Soft failed openQA tests: 1/80 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test did not soft fail in Rawhide-20161211.n.0): ID: 51236 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/51236 Passed openQA tests: 66/80 (x86_64), 14/15 (i386) New passes (same test did not pass in Rawhide-20161211.n.0): ID: 51230 Test: i386 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/51230 ID: 51231 Test: x86_64 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/51231 ID: 51244 Test: x86_64 Server-dvd-iso support_server URL: https://openqa.fedoraproject.org/tests/51244 ID: 51245 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/51245 ID: 51246 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/51246 ID: 51255 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/51255 ID: 51261 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/51261 ID: 51281 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/51281 ID: 51301 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/51301 ID: 51310 Test: x86_64 universal install_kickstart_firewall_configured URL: https://openqa.fedoraproject.org/tests/51310 ID: 51311 Test: x86_64 universal install_kickstart_nfs URL: https://openqa.fedoraproject.org/tests/51311 ID: 51317 Test: i386 universal install_simple_encrypted URL: https://openqa.fedoraproject.org/tests/51317 Skipped openQA tests: 1 of 97 -- 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
[Test-Announce] Fedora 26 Rawhide 20161214.n.1 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 26 Rawhide 20161214.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 Notable package version changes: pungi - 20161210.n.0: pungi-4.1.11-3.fc26.src, 20161214.n.1: pungi-4.1.11-4.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_Rawhide_20161214.n.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161214.n.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161214.n.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161214.n.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161214.n.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161214.n.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161214.n.1_Security_Lab Thank you for testing! -- Mail generated by relval: https://www.happyassassin.net/relval/ ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora 24 Respin 20161210 compose check report
Missing expected images: Lxde live x86_64 Failed openQA tests: 2/22 (x86_64) ID: 51209 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/51209 ID: 51224 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/51224 Soft failed openQA tests: 2/22 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 51206 Test: x86_64 Workstation-live-iso base_services_start URL: https://openqa.fedoraproject.org/tests/51206 ID: 51217 Test: x86_64 KDE-live-iso base_services_start URL: https://openqa.fedoraproject.org/tests/51217 Passed openQA tests: 18/22 (x86_64) -- 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
Introduction
Hello Everyone, My name is Jaskaran Singh Narula and I am interested in contributing in the Fedora project and QA is a area where I can enhance my skills over Linux. I have been using and working over Linux from last 4 years and I am also RHCSA Certified and as well placed in Red Hat also. Right now I am working as a Linux instructor, and teacher. I am looking forward to assist fedora project in any possible way I can. Thank you, Jaskaran Singh Narula ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
2016-12-15 @ 17:00 UTC - Outage for qadevel.cloud replacement
I realize this is a little last minute but there's no telling how much longer the current auth system will continue to work. I'm planning to take qadevel down (phabricator, some docs etc.) tomorrow so that I can finally replace it with an instance that has working auth among other improvements. This is going to be a rather large change and I expect that it will take at least 4 hours. If this is going to be a huge problem, please let me know soon. The big changes will be: - new hostname *.qadevel.cloud.fedoraproject.org will become *.qa.fedoraproject.org - better cert handling no more errors when http:// is used - new auth system using fedora systems, no longer relying on persona - newer version of phabricator - lots of other boring changes under the hood :) pgp3TX6hvkk0G.pgp Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Please Test Staging Phabricator
On Tue, 2016-12-13 at 18:34 -0700, Tim Flink wrote: > On Wed, 7 Dec 2016 08:52:53 -0700 > Tim Flinkwrote: > > > As support for the Persona system has winded down, we finally have a > > new method for logging into our phabricator instance (that should > > also get rid of all those 500s on login). > > > > My goal has been to set up the migration so that there's no account > > fiddling needed to use the new auth system. Things are working in my > > testing but I'd like to see more people test out the new auth method > > before deploying all of this to production. > > > > If you have the time, please try logging in to > > > > https://phab.qa.stg.fedoraproject.org/ > > > > I've seen some errors from ipsilon about "Transaction expired, or > > cookies not available", click on "Try to login again" and everything > > should work. > > > > If you run into problems, please let me know. There are a few accounts > > which will need tweaking by hand (phabricator username doesn't match > > FAS username so my script didn't work) but I wanted to make sure this > > was working for more than just me before finishing things up. > > After a bunch more fiddling, I think that auth is working correctly > now. I've also removed the monikra.me stuff for now and auth will work > directly against Fedora's auth systems. > > Keep in mind that the stg phab is using stg FAS so your credentials may > be different than production. Auth seems OK for me now, thanks. -- 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
O.T. F25 Brasero displays burn error, K3B does the job
Hi, try to copy a VCD or a picture CD with jpgs. Error see log appending. K3B does this job without error. If anyone of the Brasero developpers sees this thread, possibly he would be interested in the investigation of this problem. The error occurs at the "end" of the copy process. The copy should be done from a VCD into a CD in the same burning utility. The CD was made with a Windows program. Kind regards, log appending Log: Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1739) BraseroCdrdao called brasero_job_get_action BraseroCdrdao getting varg BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao called brasero_job_set_output_size_for_current_track BraseroCdrdao got varg: BraseroCdrdao stopping BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_session_output_size BraseroCdrdao output set (IMAGE) image = /home/joerg/muttiAlbum-.toc.bin toc = /home/joerg/muttiAlbum-.toc BraseroCdrdao called brasero_job_get_session_output_size BraseroCdrdao getting varg BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao called brasero_job_get_output_type BraseroCdrdao called brasero_job_get_image_output BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_set_use_average_rate BraseroCdrdao got varg: cdrdao read-cd --device /dev/sr0 --read-raw --datafile /home/joerg/muttiAlbum-.toc.bin -v 2 /home/joerg/muttiAlbum-.toc BraseroCdrdao Launching command BraseroCdrdao called brasero_job_get_fd_in BraseroCdrdao called brasero_job_get_fd_out BraseroCdrdao stderr: WARNING: Environment variable 'HOME' not defined- cannot read .cdrdao. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Cdrdao version 1.2.3 - (C) Andreas MuellerBraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: /dev/sr0: HL-DT-ST DVDRAM GUA0NRev: 1.00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x) BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao stderr: Reading toc and track data... BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao stderr: Track ModeFlags StartLength BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 1 DATA4 00:00:00( 0) 35:40:29(160529) BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Leadout DATA4 35:40:29(160529) BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: BraseroCdrdao stderr: PQ sub-channel reading (data track) is supported, data format is BCD. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Raw P-W sub-channel reading (data track) is supported. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Cooked R-W sub-channel reading (data track) is supported. BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: Copying data track 1 (MODE2_RAW): start 00:00:00, length 35:40:29 to "/home/joerg/muttiAlbum-.toc.bin"... BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_set_current_action BraseroCdrdao stderr: 00:01:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:02:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:03:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:04:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:05:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:06:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:07:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:08:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:09:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:10:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:11:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:12:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:13:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 00:14:00 BraseroCdrdao called . . . . . BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:34:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:35:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:36:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:37:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:38:00 BraseroCdrdao called brasero_job_get_action BraseroCdrdao stderr: 35:39:00
Re: Introduction
You're welcome Varun Singh... On Wed, Dec 14, 2016 at 6:27 PM, Sumantro Mukherjeewrote: > > > - Original Message - > > From: "Varun Singh" > > To: test@lists.fedoraproject.org > > Sent: Tuesday, December 13, 2016 1:56:19 PM > > Subject: Introduction > > > > Hello everyone, > > I'm Varun, a Computer Science Undergrad working around with Linux for > 1.5+ > > years. So far I've used CentOS, RHEL 7, Ubuntu, Manjaro, Fedora, Zorin, > > Mint, and Kali. Currently, I'm using Fedora 25. I joined the Fedora > Project > > as I'm enthusiastic about open source and I wish to contribute my > efforts to > > this community. > > > > I'm a blogger. I create and write articles for Technotification and been > > doing so since Dec '13. I have intermediate experience with System > > Administration on Red Hat based systems, Adobe Photoshop and Adobe > > Illustrator. > > > > I've created the account at FAS and I look forward to contributing to > Fedora > > QA, content writing and design. > > > > Thanks and regards, > > Varun Singh. > > > > ___ > > test mailing list -- test@lists.fedoraproject.org > > To unsubscribe send an email to test-le...@lists.fedoraproject.org > > > > > Hey Varun > > first of all welcome to Fedora QA. I have sponsored your request to FAS > group. You can start off by testing updates in [ > http://bodhi.fedoraproject.org/] for Fedora 24 and Fedora 25 . update > testing is where a tester tests a package and gives out a +1 Karma for PASS > and -1 Karma for FAIL. You can go to bodhi.fedoraproject.org where you > can sort the packages with Fedora Releases and tags viz "pending" & > "testing" . You can read much about update testing here [1]. You can also, > use fedora-easy-karma for giving out feedbacks. > > > you can start with Release Validation testing. In Release Validation all > you need to do is to check the nightly/TC/RC against certain criteria. For > example, let's take the latest Rawhide (Fedora_26_Rawhide_20161210.n.0), > you can run test cases which are mentioned [2] and submit your results in > the test matrix. > > Note that each of the test cases[3] will have "How to test" section which > will have the steps (to be executed sequentially) and if the results match > with the expected results you can mark it as pass by editing the wiki page > {{result|PASS|}} . Always make sure to check for "Associated > release criterion" which can be found on the top of test case page , if > your test case fails you can mark it fail by editing the wiki page > {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora. > > > You can always find the ‘current’ validation pages using these addresses: > > https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test > https://fedoraproject.org/wiki/Test_Results:Current_Base_Test > https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test > https://fedoraproject.org/wiki/Test_Results:Current_Server_Test > https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test > > [1]https://fedoraproject.org/wiki/QA:Updates_Testing > [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_ > Rawhide_20161210.n.0_Summary?rd=Test_Results:Current_Summary > [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc > [4]https://bugzilla.redhat.com/ > > > P.S. I have replied you off list for the contribution pathways for Design > and Writing. > > Thanks > Sumantro > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Introduction
- Original Message - > From: "Varun Singh"> To: test@lists.fedoraproject.org > Sent: Tuesday, December 13, 2016 1:56:19 PM > Subject: Introduction > > Hello everyone, > I'm Varun, a Computer Science Undergrad working around with Linux for 1.5+ > years. So far I've used CentOS, RHEL 7, Ubuntu, Manjaro, Fedora, Zorin, > Mint, and Kali. Currently, I'm using Fedora 25. I joined the Fedora Project > as I'm enthusiastic about open source and I wish to contribute my efforts to > this community. > > I'm a blogger. I create and write articles for Technotification and been > doing so since Dec '13. I have intermediate experience with System > Administration on Red Hat based systems, Adobe Photoshop and Adobe > Illustrator. > > I've created the account at FAS and I look forward to contributing to Fedora > QA, content writing and design. > > Thanks and regards, > Varun Singh. > > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Hey Varun first of all welcome to Fedora QA. I have sponsored your request to FAS group. You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 and Fedora 25 . update testing is where a tester tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to bodhi.fedoraproject.org where you can sort the packages with Fedora Releases and tags viz "pending" & "testing" . You can read much about update testing here [1]. You can also, use fedora-easy-karma for giving out feedbacks. you can start with Release Validation testing. In Release Validation all you need to do is to check the nightly/TC/RC against certain criteria. For example, let's take the latest Rawhide (Fedora_26_Rawhide_20161210.n.0), you can run test cases which are mentioned [2] and submit your results in the test matrix. Note that each of the test cases[3] will have "How to test" section which will have the steps (to be executed sequentially) and if the results match with the expected results you can mark it as pass by editing the wiki page {{result|PASS|}} . Always make sure to check for "Associated release criterion" which can be found on the top of test case page , if your test case fails you can mark it fail by editing the wiki page {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora. You can always find the ‘current’ validation pages using these addresses: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test https://fedoraproject.org/wiki/Test_Results:Current_Base_Test https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test https://fedoraproject.org/wiki/Test_Results:Current_Server_Test https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Rawhide_20161210.n.0_Summary?rd=Test_Results:Current_Summary [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [4]https://bugzilla.redhat.com/ P.S. I have replied you off list for the contribution pathways for Design and Writing. Thanks Sumantro ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
[Test-Announce] Fedora QA 25 Restrospection
Hey Testers The Retrospective page for Fedora 25 QA is now up : https://fedoraproject.org/wiki/Fedora_25_QA_Retrospective We use the retrospective page to track things that went well and things that didn't go so well during the Fedora 25 validation process, and for tracking ideas we have but don't have time to act on during the rush of doing validation (that's the wishlist). Please, add any feedback you have of this type to the retrospective page! There are instructions on the page for adding feedback. All feedback is useful, we'll take a look at all the items on the page and come up with specific recommendations for addressing them which we'll file as trac tickets and work on in the time before Fedora 26 validation starts up. Thanks Sumantro ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org