Re: Proposal for enhancement of criterion
Because there was no suggestions, I've made changes. [1] is non-blockig now. And I have amended criterion in [2]. [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system [2] https://fedoraproject.org/wiki/Fedora_17_Alpha_Release_Criteria On Tue, 2012-01-31 at 09:48 -0800, Adam Williamson wrote: On Tue, 2012-01-31 at 07:15 -0500, Petr Schindler wrote: Especially saving failures to disk is important for installation without net access. There are test cases [1], [2] and [3] for testing this feature. [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla [2] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_disk [3] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system Ah, that's part of my last-reply-but-one. :) I think certainly adding local disk at Alpha is reasonable. I'm not so sure about supporting saving to a remote system via ssh at Alpha. Ok, I would propose to change test case [1] to non-blocking. I think it could be enough to support saving reports only to disk and bugzilla. So I propose criterion: The installer must be able to report failures to Bugzilla and local disk, with appropriate information included [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system That seems reasonable to me. Anyone else have any thoughts on this? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proposal for enhancement of criterion
From: Adam Williamson awill...@redhat.com To: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Sent: Tuesday, January 31, 2012 1:47:55 AM Subject: Re: Proposal for enhancement of criterion On Mon, 2012-01-30 at 11:35 -0500, Petr Schindler wrote: I propose to enhance alpha criterion The installer must be able to report failures to Bugzilla, with appropriate information included to The installer must be able to report failures to Bugzilla, remote system and local disk, with appopriate information included Especially saving failures to disk is important for installation without net access. There are test cases [1], [2] and [3] for testing this feature. [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla [2] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_disk [3] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system Ah, that's part of my last-reply-but-one. :) I think certainly adding local disk at Alpha is reasonable. I'm not so sure about supporting saving to a remote system via ssh at Alpha. Ok, I would propose to change test case [1] to non-blocking. I think it could be enough to support saving reports only to disk and bugzilla. So I propose criterion: The installer must be able to report failures to Bugzilla and local disk, with appropriate information included [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proposal for enhancement of criterion
On Tue, 2012-01-31 at 07:15 -0500, Petr Schindler wrote: Especially saving failures to disk is important for installation without net access. There are test cases [1], [2] and [3] for testing this feature. [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla [2] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_disk [3] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system Ah, that's part of my last-reply-but-one. :) I think certainly adding local disk at Alpha is reasonable. I'm not so sure about supporting saving to a remote system via ssh at Alpha. Ok, I would propose to change test case [1] to non-blocking. I think it could be enough to support saving reports only to disk and bugzilla. So I propose criterion: The installer must be able to report failures to Bugzilla and local disk, with appropriate information included [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system That seems reasonable to me. Anyone else have any thoughts on this? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proposal for enhancement of criterion
On Mon, 2012-01-30 at 11:35 -0500, Petr Schindler wrote: I propose to enhance alpha criterion The installer must be able to report failures to Bugzilla, with appropriate information included to The installer must be able to report failures to Bugzilla, remote system and local disk, with appopriate information included Especially saving failures to disk is important for installation without net access. There are test cases [1], [2] and [3] for testing this feature. [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla [2] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_disk [3] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system Ah, that's part of my last-reply-but-one. :) I think certainly adding local disk at Alpha is reasonable. I'm not so sure about supporting saving to a remote system via ssh at Alpha. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
