[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Help testing latest abrt-0.0.10-12.fc12



On Mon, 2009-11-02 at 18:56 -0500, Clyde E. Kunkel wrote:
> On 11/02/2009 02:27 PM, James Laska wrote:
> > Greetings,
> >
> > Jiri Moskovcak has asked for help testing the latest ABRT packages for
> > Fedora 12.
> 
> <snip>
> >
> >       1. Confirm the fix for
> >          https://bugzilla.redhat.com/show_bug.cgi?id=531347
> >       2. Kill a c/c++ application and see if abrt catches it -
> >          https://fedoraproject.org/wiki/QA:Testcase_ABRT_CCPP
> 
> Caught the crash, downloaded needed files for the report but refused to 
> report saying that the bugzilla reporter plugin not properly 
> configured.a  Strange since I had configured it properly and used it 
> successfully.  Gave me an opportunity to populate the bz reporter fields 
> and I did, but lost the entries somewhere saying field empty.  Here is 
> what appeared on the terminal:
> # abrt-gui
> Update >>Starting report creation...<<
> Our job for UUID 6e47676889724d39ebfb1e04e43281a441dec920 is done.
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Update >>Starting report creation...<<
> Update >>Checking for duplicates...<<
> Update >>Bug is already reported: 532441<<
> Update >>Logging into bugzilla...<<
> Warning >>Report(): Empty login and password. Please check Bugzilla.conf<<
> Update >>Reporting via 'Bugzilla' was not successful: Empty login and 
> password. Please check Bugzilla.conf<<
> Update >>Creating a report...<<
> 
> So, looked in Bugzilla.conf and the entries were blank.  Filled them in 
> and retried, same results.
> 
> 
> 
> >       3. Introduce an unhandled python exception, and see if it catches
> >          it - https://fedoraproject.org/wiki/QA:Testcase_ABRT_python
> 
> got the crash...abrt didn't budge.

I've tweaked the instructions in the test case a bit.  It shouldn't
affect your result, but you might take a look at the changes.  Make sure
the file you modified is provided by a Fedora package.

Jiri: Anything else you can think of that might affect the outcome of
the python crash test?

> >       4. Report a crash to bugzilla -
> >          https://fedoraproject.org/wiki/QA:Testcase_ABRT_Bugzilla
> 
> Hmmmm....now working.  Went back to 2 and resend and now it works.
> 
> 
> Here is what I think happened:  the testing instructions for each case 
> say "service abrt restart".   This was not working and I didn't tumble 
> to the fact that the instructions should have said "service abrtd 
> restart".  Once I did that then reporting worked.  Repeated 3 properly 
> and it still doesn't work.

Thanks for the suggestion Clyde.  I've updated the cases to use 'service
abrtd restart'.

Thanks,
James

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]