Closed Bug 431494 Opened 16 years ago Closed 16 years ago

unit test boxes are not creating a fresh profile for each run

Categories

(Release Engineering :: General, defect, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Dolske, Assigned: coop)

References

Details

Attachments

(1 file)

Spun off from bug 425987, where a ginormous places.sqlite file was causing reftests to randomly fail due to timeouts and run slow.

Apparently these boxes are *supposed* to be nuking the profile after each run, but that's not happening. On qm-centos5-02, the profile appears to have been in use for almost a year.
Assignee: nobody → ccooper
Priority: -- → P1
There's a flag to createTestingProfile.py to do this that we're just not setting. Hopefully it will be as simple as that.
Status: NEW → ASSIGNED
Testing the change in the staging env now.
Passing with flying colors (green) in staging; places.sqlite *does* get removed with every run.
Attachment #318597 - Flags: review?(rcampbell)
Attachment #318597 - Flags: review?(rcampbell) → review+
Comment on attachment 318597 [details] [diff] [review]
[checked in] Clobber the old profile dir on each iteration.

Unit test production master reconfig-ed with this change.
Attachment #318597 - Attachment description: Clobber the old profile dir on each iteration. → [checked in] Clobber the old profile dir on each iteration.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Release Engineering: Maintenance → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.