21323 - Bloaty: tinderbox trapped in profile mgr until profile created

Status: VERIFIED FIXED

(SeaMonkey :: General, defect, P1)

Description

[Chris McAfee]

Tinderbox bloat test gets stuck in the profile manager until
a profile is created.  I fixed tinderboxes by hand
for this now, but next purge of profiles on a build
will make this test fail again.

There is a -CreateProfile commandline option, we could
use this to create/detect a "tinderbox" profile at startup.
m13.

Comment 1

[Warren Harris]

You should put this in the crash-on-startup test so that the bloat test can
assume that the profile is already there.

Also, the tinderbox script should skip the bloat test if the crash-on-startup
test fails.

Comment 2

[Chris McAfee]

This is what's making shrike/clobber report zero,
it's stuck in the profile manager.  For that build,
the app starts up Ok by-hand, tinderbox
insists on going to the profile manager.  Let me file
another bug for that so we can track this.

Comment 3

[Chris Waterson]

Uh, why don't we just go run the app -once- by hand on the machine, as the user
that's actually doing the build (cltbld?), so that a profile gets created?

Comment 4

[Chris McAfee]

I believe you will have to repeat this process every time
you clean the tree out.  Note in bug 22052, even running by
hand is failing for some reason.

Comment 5

[Chris Waterson]

Deleting the build tree will kill the component registry, but it shouldn't kill
the user's registry. I can do a clobber build, and never see the profile manager
come back to life. Maybe something else is happening?

Comment 6

[Chris McAfee]

Now check this out, all tinderbox builds run as "cltbld", yet
I had to go do the profile hack for Each Build.  ??  I should have
had to do this exactly once based on your description.  There's
something about profile manager that I don't understand.

Comment 7

[racham]

Are you wiping out mozregistry.dat (or the equivalent ~/.mozilla/registry or
Preferences:Mozilla Registry) by chance ? That will make the profile manager to
come into the picture.

If you just have one 5.0 profile, just like in the past, we should be launched
into the browser directly.

Comment 8

[Chris McAfee]

tinderbox builds run as "cltbld", ~/.mozilla/registry is not
being deleted, but ? many builds are running as the same user,
possibly at the same time, on different platforms, could this
be part of the clobber-shows-zeros problem?

Comment 9

[don]

*** Bug 22052 has been marked as a duplicate of this bug. ***

Comment 10

[Chris McAfee]

Not fixing this for m13.

Comment 11

[Chris McAfee]

Not beta, m16

Comment 12

[Chris McAfee]

fixed, we check for .mozilla/prefs.js, if not found
we create a profile, "mozProfile" is default, configurable
in tinder-config.pl.

Comment 13

[(not reading, please use [e-mail] instead)]

chris, ~/.mozilla/prefs.js?  or ~/.mozilla/mozProfile/prefs.js

Comment 14

[Chris McAfee]

typo, .mozilla/<profile>/prefs.js, where <profile>
gets set via the script.

Comment 15

[leger]

Adding verifyme keyword.

Comment 16

[leger]

Working fine with Linuc 2000-03-22-06 build.  marking Verified.