TEST CASE
--------------
1) Put the attached crash report (re /bin/sleep with the CoreDump field corrupted) in /var/crash/
2) Run ubuntu-bug /var/crash/_bin_sleep.1000.crash
3) View the details of the crash and observe an UnreportableReason indicating that the "problem report is damaged"
4) Leave "Send an error report" checked and click continue
5) Observe a _bin_sleep.1000.upload in /var/crash/
With the version of the package from -proposed a .upload file will not be created.
REGRESSION POTENTIAL
----------------------------------
It's possible that _MarkForUpload will be set to False in more cases than it should be thereby preventing crashes from being sent to the Error Tracker. So it might also be good to SEGV a process and ensure that a .crash and .upload file are created.
TEST CASE _bin_sleep. 1000.crash 1000.upload in /var/crash/
--------------
1) Put the attached crash report (re /bin/sleep with the CoreDump field corrupted) in /var/crash/
2) Run ubuntu-bug /var/crash/
3) View the details of the crash and observe an UnreportableReason indicating that the "problem report is damaged"
4) Leave "Send an error report" checked and click continue
5) Observe a _bin_sleep.
With the version of the package from -proposed a .upload file will not be created.
REGRESSION POTENTIAL ------- ------- ------- ------
-------
It's possible that _MarkForUpload will be set to False in more cases than it should be thereby preventing crashes from being sent to the Error Tracker. So it might also be good to SEGV a process and ensure that a .crash and .upload file are created.