Closed Bug 489183 Opened 11 years ago Closed 10 years ago

Run Ts tests against generated Places databases

Categories

(Testing :: General, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ddahl, Unassigned)

References

()

Details

the Places team has been collecting stats from users. We have been capturing # of bookmarks, places, annotations, tags, etc.

We can build a sample of a minimum, average, and maximum data sets at anytime.
alice - is this in the right component to get attention?
OS: Linux → All
Hardware: x86 → All
Depends on: 489513
bug 414660 is about making Talos changes to run Ts. i propose we use that for the Talos changes, and this bug about getting Places-specific Talos tests running.
Version: unspecified → Trunk
this bug basically should be about using the python places.sqlite generator in bug 480340 to create the dbs in the profiles that are fed to Talos in bug 414660.
If you can provide me with the "dirty profile" as required in the other bug I'd sure be grateful.  Does it need to be based upon pages that talos is cycling through as part of tp?
(In reply to comment #4)
> If you can provide me with the "dirty profile" as required in the other bug I'd
> sure be grateful.  Does it need to be based upon pages that talos is cycling
> through as part of tp?
I don't think it'll matter if talos is visiting the pages.  There is an issue however of using the same file all the time.  As entries get older, they'll end up getting expired more, so as time moves on, we'll be doing more and more work during talos runs expiring more.  I suspect we don't want to do that, so we basically need to generate the places.sqlite file every day or so, which isn't so nice...
How do we generate places files?  It might be possible to generate on the fly using buildbot if we have a method of creating them.
David has a python script in another bug (David, can you post that bug number here please?), but for our mega profiles, it takes a while to run.
Well, we could just generate a new one every night (assuming that the talos master has the spare cycles to do so) and then have it automagically pushed to the talos slaves each day.  How big are we talking?  Is download time also going to be a concern?  I don't want to weigh down my slaves too much.
I'm going to let David answer those questions as I don't know the full answer.  We also may not need to run talos on our monster profile, but more sensible ones we should be doing.
We have the option of creating 3 different files: a "max", "avg" and "min" places.sqlite. The max takes about 3+ plus hours to generate on my low-rent mac mini. I imagine we will do a lot of these tests with the "avg" file, which maybe will take an hour to generate.

The generation code is in this patch: https://bug480340.bugzilla.mozilla.org/attachment.cgi?id=374526

You can follow the directions in this file:  toolkit/components/places/tests/generator/places/builddb/generate.py

You will need to install Python 2.5, Django 1.0.2, urllib2, and simplejson

I have tested this on Linux and MacOS X
the Ts part of this is fixed. i'll file a new bug for Tp, instead of overloading this one.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Summary: Run Ts/Tp tests against generated Places databases → Run Ts tests against generated Places databases
Blocks: 527596
filed bug 527596 for Tp.
You need to log in before you can comment on or make changes to this bug.