Closed
Bug 468405
Opened 16 years ago
Closed 15 years ago
Connection timeouts when doing reasonable queries
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: samuel.sidler+old, Unassigned)
References
()
Details
Since the topcrash page is inaccurate (bug 461977), I've been using queries to see topcrash lists and do analysis on them. Unfortunately, for about a week, queries haven't been working. I'm getting a "Connection Interrupted" error. These aren't complex queries (or... they *weren't*...), so I'm not sure why. This basically blocks me from doing my job. The query I was using: Product: Firefox Branch: 1.9 Version: Firefox 3.0.4 Platform: Mac OS X Range: 1 week (default) While that query fails, I really need to not be able to specify the platform at all, so any fix for this bug needs to take out the "platform" part in testing.
Comment 1•16 years ago
|
||
http://crash-stats.mozilla.com/?do_query=1&product=Firefox&version=Firefox%3A3.0.4&query_search=signature&query_type=contains&query=&date=&range_value=7&range_unit=days As an alternative, for now.
Depends on: 432450
What's the difference between the original and the alternative? In other words, how does one, in general, change a query that times out to one that doesn't?
Comment 3•15 years ago
|
||
I find it's typically a matter of a few days difference less than a week, and a few days more than a week. In other words, 5, 6 or 7 days might work, but 9, 10 or more doesn't - on first pass. It tends to vary. And recently it seems to have gotten ever worse as noted in bug 474037. I've had very simple queries fail, for example clicking a signature on the results page of a search that was one week targeting just one release of thunderbird. similar to ss's example
Reporter | ||
Comment 4•15 years ago
|
||
This is fixed with the re-partitioning.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•