Closed Bug 487751 Opened 17 years ago Closed 17 years ago

Try server not doing jemalloc? not setting WIN32_REDIST_DIR?

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Product:
Mozilla Messaging Graveyard
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

Details

Between the reported results in bug 485395 comment 13 et seq ("user: this Windows build won't even start! developer: huh, works fine on my machine") and what I can see from the builds (no mozcrt19.dll, but also no Microsoft.VC80.CRT.manifest, msvcm80.dll, msvcp80.dll and msvcr80.dll), it looks like the try server isn't setting --enable-jemalloc, but also either isn't setting WIN32_REDIST_DIR, or doesn't have the files there (or just doesn't work - personally, I've never been able to persuade it to actually copy them).
I can see that the try-server mozconfigs are indeed missing --enable-jemalloc, so I've added that. WIN32_REDIST_DIR is set, but pointing to somewhere that doesn't exist on this reference platform. It's actually nowhere in the RefPlatform documentation, but I've found a description of it on mdc, so it is now set correctly, and has the right files in it. Got to fire off a new try build to pick up these changes up.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.