559226 - Find better way to communicate inability to access deferred crashes to User

Status: RESOLVED WORKSFORME

(Socorro :: General, task)

Description

[Ryan Snyder [:ryansnyder] [:rsnyder] [:rysny]]

In about:crashes, I have 7 crash reports, but I can only access 2 via Crash Reporter.

bp-41effee2-6bae-41ec-9f02-47ab82100301	3/1/10	3:48 PM
0A004B3E-C92F-408D-96DD-753FF16C07A6	1/30/10	3:27 PM
bp-a145ffcc-422a-4ff7-b439-ecf412100123	1/23/10	4:15 PM
bp-08127b6b-fac4-4129-ad48-d00892100123	1/23/10	4:05 PM
bp-3fc26b94-8823-4f51-aaa5-1ffba2091214	12/14/09 11:47 AM
bp-9af20ddf-2ef6-4559-88f9-bb3132090412	4/12/09	8:23 AM
bp-6dc03671-31ed-4d84-8ff8-029f72090311	3/11/09	6:51 PM

Of the 5 crash reports that cannot be found only 1 resolves an appropriate error message at http://crash-stats.mozilla.com/about/throttling.  It would be nice to communicate a similar error message to users rather than attempting to access the report and receiving the message "Oh Noes! This archived report could not be located."

We also may want to consider being a little more verbose on the pending status screen where we only state, "Please Wait...  Fetching this archived report will take 30 seconds to 5 minutes."  I'm expecting to receive a report within 5 minutes, not a "can't find this report" message.

Comment 1

[Rob]

I agree, I have two Reports from last year and can not access either one. I wait and wait but eventually they are not accessible. 

I did a bit of Googling around to see what the problem might be, then I searched for a similar Bug and found this BR.

This page: http://code.google.com/p/socorro/source/browse/trunk/webapp-php/application/views/report/pending.php?r=1409 has an alternate message that could be displayed:

"Oh Noes! /n This archived report has expired because it is greater than 3 years of age."

IF the Reports are being expired sooner (say 6 months) could that message be changed from "3 Years" to an appropriate number?

Can we not be told _quickly_ that our Report actually exists, _then_ wait and actually receive our Report? 

Why wait 30 seconds, then 30 seconds more, then again, and again, and then "No Soup for You!". Give us a prompt rejection (like the "Soup Nazi").

Rob

Comment 2

[Rob]

Bump: 10 Months and this still occurs with _older_ Reports but works for my _newest_ Report.

Works:  bp-e0b814c8-f331-4124-8c7a-1befb2110223		2/23/2011	18:52
Broken: bp-03f1bba6-fe3f-4d38-ad8e-a5b052110204 	2/4/2011	22:15

Was this FIXED between 2/4/2011 and 2/23/2011 ?

If it continues to work then this is a WFM. I suggest waiting for more confirmations or until one of the two of us posts here again. 

Will "Crash Me Now" produce a _valid_ Test on the WEBSITE (as opposed to 'on the BROWSER')?  I could run that if it would produce a valid Test (on the Website).

Thanks to whomever fixed it, if it is fixed,
Rob

Comment 3

[Rob]

Something is screwed up on the Website.

Indeed the second one in Comment 2 I can not access, but a few others (that I checked) that are older are accessible.

The brokenness is that actually accessing Crash Reports seems to create NEW ones with DIFFERENT Data, yet I do NOT get a "Crash Reporter" pop-up nor am I crashing ! I did not crash twice a few minutes ago (@ 19:14 and 19:12).


URL: about:crashes

Report ID       		 	Date Submitted
  
bp-98061aed-f8da-4783-82c6-b820c2110225	2/25/2011	19:14
bp-16fc1333-48fe-44c9-abf9-1f9142110225	2/25/2011	19:12
bp-e0b814c8-f331-4124-8c7a-1befb2110223	2/23/2011	18:52
bp-03f1bba6-fe3f-4d38-ad8e-a5b052110204	2/4/2011	22:15
bp-296983a6-9d32-4184-b0bb-976a62101231	12/31/2010	18:11
...


Rob

Comment 4

[(not currently active) Ted Mielczarek]

This is not the website, this is just the confusing way we present things in about:crashes. Crashes that failed to submit for some reason will be listed there, and clicking on them will re-submit them and take you to the submitted report. As a side effect, it will update the timestamp to when it was re-submitted. That's filed as bug 516455.

Comment 5

[Rob]

(In reply to comment #4)
> This is not the website, this is just the confusing way we present things in
> about:crashes. Crashes that failed to submit for some reason will be listed
> there, and clicking on them will re-submit them and take you to the submitted
> report. As a side effect, it will update the timestamp to when it was
> re-submitted. That's filed as bug 516455.

In that event _I_ consider this WFM and if you know the patch that fixed it then it can be "FIXED" instead of "WFM", but _I_ am not the "Reporter".

Ryan, any comments?

Comment 6

[Ryan Snyder [:ryansnyder] [:rsnyder] [:rysny]]

I think most of my original concerns have been take care of.  I've gone through a list of my recent crashes in my browser and they're all either resolving properly or redirecting me to the Throttle Info page.  Will resolve as WFM.  Thanks guys.