Closed Bug 419648 Opened 17 years ago Closed 17 years ago

tryserver win32 builds fail since bug 415928 was landed

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 415928

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Ted suspects that because the try servers do not --enable-jemalloc that non-jemalloc win32 builds are broken. I'm trying a build with --enable-jemalloc to test that theory. Either way, this has brought up an important issue: the try server uses different mozconfig files than the nightlies. I think we should make it checkout the nightly mozconfig files and use those. There's no reason I can think of to have it use it's own.
Nick points out that there's some differences between these configs. For one, RUN_AUTOCONF_LOCALLY=1 is in the tryserver configs -- this is pretty important. Something like that _could_ be set as an env variable, but I don't think that's the right way to go about this. Maybe we just have to deal with keeping these configs in sync.
Adding --enable-jemalloc to the tryserver config didn't fix the problem. There's a bunch of other differences between the two -- I'm going to try a build using the nightly mozconfig next.
This build didn't work either. Gavin landed a fix in bug 415928 that Ted thinks will fix this. There's a build spinning right now to test it.
Latest win32 build built fine.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1) > Nick points out that there's some differences between these configs. For one, > RUN_AUTOCONF_LOCALLY=1 is in the tryserver configs -- this is pretty important. > Maybe we just have to deal with keeping these configs in sync. The tryserver mozconfigs are likely to always contain a superset of the settings in the nightly config though, right? Could you just checkout+include the nightly mozconfig in the tryserver config?
Yeah, that's a good idea. I totally forgot we could do that.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.