tracker shows wrong results

Bug #303129 reported by marco.pallotta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Undecided
Unassigned

Bug Description

Often tracker shows wrong results. In fact it happened that the same search, done two time almost at the same time (the second done as soon as the first finished) shows different results.
I attach two screenshots of what I say.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :
Revision history for this message
marco.pallotta (marco-pallotta) wrote :
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

A similar issue happens again today. Tracker only showed email related results but after logging out and logging in again all worked ok..

Revision history for this message
marco.pallotta (marco-pallotta) wrote :

Also today happens the same thing I posted on 22-12-2008 (logging out and logging in fixed the tracker issue).

Revision history for this message
Martyn Russell (martyn-lanedo) wrote :

I think I know the issue you are talking about. I think 0.6.92 resolves this issue.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :

Martyn have you noticed this issue you too?

Revision history for this message
Martyn Russell (martyn-lanedo) wrote :

Marco, I can't say I have seen it, I know 1 or 2 people have reported such an issue, but I have failed to see how to reproduce it with TRUNK/0.6.92 and above. We have changed a lot of things in this area in the past month or so. Namely:

 - We now calculate stats based on DB functions with COUNT instead of an INSERT to manually store statistics.
 - We now calculate stats based on volumes being mounted or not (before if you unmounted a volume, it would still report them).
 - We now don't report stats for 0 count items
 - We now have a cache for stats to improve performance while indexing (1 minute cache before renewal and of course we get updates from the indexer when it is finished too so we don't have to do it after we are finished).

I would like to know if this issue is still apparent in 0.6.92. I can't reproduce it at least.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.