https://build.mozilla.org/clobberer/index.php?master=http%253A%252F%252Fproduction-master03.build.mozilla.org%253A8010%252F&slave=moz2-linux64-slave08&builddir=tm-lnx64-dbg&branch=tracemonkey&buildername=Linux+x86-64+tracemonkey+leak+test+build says ... tracemonkey-linux64-debug:1295135899:philringnalda@gmail.com ... which is nice and all, but as http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1295142562.1295142927.26433.gz&fulltext=1 (which should have picked up that clobber) says, /builds/slave/tracemonkey-linux64-debug doesn't exist, skipping because it only has a /builds/slave/tm-lnx64-dbg.

...and clobberer never issues clobber requests for the short names... Seeing the same on the SeaMonkey buildbot/clobberer system.

So...the way clobberer works, there's a 1-1 mapping of "Pretty name", which is displayed in the UI, and "ID", which is stored in the "name" part of each checkbox. So when we build the page, we're ending up with the IDs that are associated with the old, longly named, build directories. Simple fix is to wipe the clobberer DB of these, or completely. Going to look for a permanent fix before going that route.

(In reply to comment #2) > So...the way clobberer works, there's a 1-1 mapping of "Pretty name", which is > displayed in the UI, and "ID", which is stored in the "name" part of each > checkbox. So when we build the page, we're ending up with the IDs that are > associated with the old, longly named, build directories. Simple fix is to wipe > the clobberer DB of these, or completely. > > Going to look for a permanent fix before going that route. The permanent fix is not obvious, so I cleaned out the entire DB. There's a backup, in case we need it.

Lowering severity, returning to the pool.

I'd like to see this become part of a larger clobberer rewrite.

Turns out release clobberer is still broken even after the purge.

After some investigation, I think the release clobberer issues are different than this bug, so I filed bug 628671 on it.

John, something to keep in mind and/or resolve when your clobberer rewrite is done?

Yes - in the rewrite, I'm planning to have buildername be the primary key so duplicate builders will be impossible.