Closed Bug 865146 Opened 11 years ago Closed 10 years ago

no related bug in crash stats after adding signature or filing crash bugs between 0H UTC and 0H PT (7H UTC)

Categories

(Socorro :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: scoobidiver, Unassigned)

References

Details

It's a long standing issue.

From time to time, even after waiting several hours, the connection between bugs with new added signatures and crash stats is not made.

See for instance bug 865080, bug 865106, and bug 865110 for new filed bugs, bug 864125 and bug 848913 for added signatures in existing bugs.

In order to workaround that, you need to remember which bugs you changed the signature and add or remove a space in the signature.
Rob, any idea what's going on there?
It seems to happen every mornings between around 2:00 and 7:00AM UTC.
I am not sure of the begin time but 7:00AM UTC (0:00 PDT) is relatively accurate for the end time.
Summary: no related bug in crash stats after adding signature or filing crash bugs from time to time → no related bug in crash stats after adding signature or filing crash bugs every morning
AFAIK, Lonnen has been working on the bug<->signature association stuff, he should be able to look into this.
For the begin time, it's before 0:42AM UTC. My guess is 0:00 UTC (17:00 PDT).

So there's a kind of limbo between 0:00 UTC and 0:00 PDT.
Scoobidiver -- thanks for looking into this. I don't see an obvious cause and won't be able to look into it further for a while, but these notes will be good for when I have time to circle back around.
I think it was caused by the switch of crash stats from PT to UTC.
Summary: no related bug in crash stats after adding signature or filing crash bugs every morning → no related bug in crash stats after adding signature or filing crash bugs between 0H UTC and 0H PT (7H UTC)
Depends on: 957301
This should be fixed by bug 957301. If the problem persists, let's start with a new bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.