569178 - "Weeks to search" for signature links on topcrash report should at least be as long as the topcrash period

Status: RESOLVED DUPLICATE of bug 561920

(Socorro :: General, task)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

STR:

1) Load https://crash-stats.mozilla.com/topcrasher/byversion/Camino/2.1a1pre
2) Click on the "28 days" report option
3) Click on the "StartDraw" signature (currently #1 on the 28 days report)

ER: List of crash reports for "StartDraw"
AR: "No Data / This query or location currently has no data." - https://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&date=2010-05-27%2009%3A00%3A00&signature=StartDraw&version=Camino%3A2.1a1pre

What happened here is that the StartDraw crashes all occurred more than 2 weeks ago, but, even though I'm on the "28 days" report, the search link is only for the last two weeks of crashes (14 days, the default Topcrash view).  It would be useful if the 28 days topcrash report tried to search 4 weeks (I'm not sure if there's value in changing the < 14d reports to have < 2wk searches, though).

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This also shows up on the Topcrashers by Site/URL/Domain reports, which are fixed at 2 weeks, e.g. http://crash-stats.mozilla.com/topcrasher/byurl/Camino/2.0.3 currently says "Below are the top crash signatures by URL from 2010-07-27 to 2010-08-10".

However, when I expand http://caminobrowser.org/start, it lists crashes in nsXULElement::CreateSlots()

This signature link is http://crash-stats.mozilla.com/report/list?product=Camino&version=Camino%3A2.0.3&date=&range_value=1&range_unit=weeks&query_search=signature&query=nsXULElement::CreateSlots()&query_type=exact&do_query=1&signature=nsXULElement::CreateSlots()

Note the "&range_value=1&range_unit=weeks" part.  This query currently turns up no crashes, since bp-39c103bb-29b2-4da6-82f7-b5eeb2100802, bp-abcf0feb-06fa-4395-b019-155742100802, and bp-cd8458dd-c089-4a48-b95c-8b4d42100802 were all on August 2, more than 7 days ago.

Comment 2

[Wayne Mery (:wsmwk)]

is this the same issue?

straight up query that is longer than the non-admin minimum, like 8 weeks query https://crash-stats.mozilla.com/query/query?product=Thunderbird&version=ALL%3AALL&range_value=8&range_unit=weeks&date=11%2F10%2F2010+15%3A45%3A26&query_search=signature&query_type=exact&query=canonicalize&build_id=&process_type=any&hang_type=any&do_query=1 

click the signature in the results and you get  Unable to Complete Request

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #2)
> is this the same issue?

I think that's probably a different bug; I filed this one about going from a topcrash report with a 4-week range (topcrasher/byversion/$product/$version/28) and ending up on a valid (but empty) list of reports page for a 1-week range, because the range was altered/not matching when the topcrasher report's links were created.

In your case, the range was properly preserved, but the "fetch me the reports you told me exist for this range" step fails with some sort of server error when using a range > 4wks.

Comment 4

[Robert Kaiser]

Is this actually a dupe of bug 561920?

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #4)
> Is this actually a dupe of bug 561920?

Yes; unfortunately, I was unable to find that one in a search before filing this one.

Not sure which is the best way to dupe; there's more discussion here (although Wayne also reported a different bug in comment 2), but Austin's report may or may not be clearer…