Closed Bug 881557 Opened 13 years ago Closed 10 years ago

[socorro-crashstats] topcrash signatures should only consider "correlation OS"

Categories

(Socorro :: Webapp, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rhelmer, Unassigned)

References

Details

This should show the whole signature, and it also breaks correlations (which perhaps should be using a custom attribute)
Assignee: server-ops-webops → nobody
Component: WebOps: Socorro → Webapp
Product: Infrastructure & Operations → Socorro
QA Contact: nmaul
Assignee: nobody → rhelmer
Ah! I am wrong about the problem here - has nothing to do with truncation. The problem is that correlation reports in the UI are intended to identify the top OS for each signature and only show reports on that, and the /correlation/signature call from topcrasher report (which determines if a signature is valid or not) is currently passing all OSes, while the following call to /ccorrelation is only passing the "correlation OS". One way to fix this is to change the way rows are iterated over in the topcrash page.
Summary: [socorro-crashstats] signatures are truncated on topcrashers in title attribute → [socorro-crashstats] topcrash signatures should only consider "correlation OS"
Not actively working on this, I think it might be fixed in the django app though.
Assignee: rhelmer → nobody
(In reply to Robert Helmer [:rhelmer] from comment #3) > I think it might be fixed in the django app though. It's not fixed. On Firefox 22 Top Crashers and Crash Reports for a signature, there are no correlations for je_free | DefaultFreeEntry, RtlpAllocateHeap | CContext::PerformAmortizedRenderOperations(), @0x0 | CClientContextActivator::CreateInstance(IUnknown*, IActivationPropertiesIn*, IActivationPropertiesOut**), __RtlUserThreadStart | _RtlUserThreadStart, @0x0 | PRMJ_Now(), etc. while there are in correlation files.
Top Crasher has been completely rewritten and as far as I know the correlations tab works as expected now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.