Anaconda exception handling testing

[Kamil Paral]

> On Mon, 17 Sep 2012 18:36:21 +0200
> Vratislav Podzimek <vpodzime at redhat.com> wrote:
> 
> <snip>
> 
> > The underlaying code raises an exception in a separate thread and
> > with a stack containing non-ascii characters (worst case scenario
> > designed from the bugs in exception handling seen so far). It also
> > produces a unique stack trace so that new bug is filed every time
> > exception handling and bug reporting in anaconda is tested.
> 
> Isn't that going to greatly increase the number of bugs filed against
> anaconda and work against the duplicate detection in ABRT/libreport?
> I
> didn't think that there were that many problems with improperly
> detected
> duplicates.

Hey, this is just for us manually triggering exceptions, for QA purposes. It replaces 'traceback' boot option that was available in F17. Of course it is expected that we close such fake reports afterwards.

Thanks, Vratislav, for your efforts. I'll adjust our test cases.