Closed Bug 425012 Opened 16 years ago Closed 15 years ago

delete firefox unittest mozconfig files once they are no longer needed

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rcampbell, Unassigned)

References

Details

Currently, unittest configs are stored along with the buildbot master config in mozilla/tools/buildbot-configs/testing/unittest. These should be pulling from the same location as build with test-specific options added in.
Priority: -- → P3
We're changing unittests, so we no longer build-before-testing, and instead will only use just pre-existing builds. 

In that situation, would we even need any mozconfig for unittests anymore, or could we just delete mozilla/tools/buildbot-configs/testing/unittest?
OS: Mac OS X → All
Hardware: x86 → All
(In reply to comment #2)
> We're changing unittests, so we no longer build-before-testing, and instead
> will only use just pre-existing builds. 
> 
> In that situation, would we even need any mozconfig for unittests anymore, or
> could we just delete mozilla/tools/buildbot-configs/testing/unittest?

We can get rid of the unittest mozconfigs once bug 383136 lands. I'm going to morph this bug based on that.
Depends on: 383136
Summary: unittest machines should pull from same mozconfigs as build → delete firefox unittest mozconfig files once they are no longer needed
Rob: is this about cleaning up the configs from CVS? I'm happy to simply WONTFIX this if that's the case given bug 383136 and our move to hg.
yeah, surely this is stale by now. Let me close that for you!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.