Closed Bug 678182 Opened 13 years ago Closed 13 years ago

stop cloning tools for unittest runs

Categories

(Release Engineering :: General, defect, P4)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 712205

People

(Reporter: catlee, Unassigned)

Details

(Whiteboard: [unittest][buildfaster:p5])

I think we only need tools for the reboot script. We could wget it from build.m.o instead, like we do for talos.
don't we also use tools for unittest for the clobber script(s) and its deps?
unittest runs should be cleaning out their build directory each time, so don't run clobberer. they do run purge_builds, but that could be removed too since all test runs share the same directory.
(In reply to Chris AtLee [:catlee] from comment #2)
> unittest runs should be cleaning out their build directory each time, so
> don't run clobberer. they do run purge_builds, but that could be removed too
> since all test runs share the same directory.

Just for point of reference, SeaMonkey machines need to keep running purge_builds, since our low amount of machines we have to run tests and builds on the same slave pool, so it needs the ability to purge other builds from the machine while it runs tests.

That need not necessarily block this work, but I'd like to keep it able to be working without having to fork the code entirely.
Priority: -- → P4
Whiteboard: [unittest][buildfaster:p?]
Whiteboard: [unittest][buildfaster:p?] → [unittest][buildfaster:?]
Whiteboard: [unittest][buildfaster:?] → [unittest][buildfaster:p5]
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.