Closed Bug 951664 Opened 11 years ago Closed 8 years ago

make.exe crashes on win64 rev2 machines on Thunderbird release l10n repacks

Categories

(Thunderbird :: Build Config, defect)

x86_64
Windows Server 2008
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WORKSFORME
Thunderbird 27.0

People

(Reporter: rail, Unassigned)

References

Details

Attachments

(1 file)

Attached image bed42c12.png
Build logs indicate time out (http://ftp.mozilla.org/pub/mozilla.org/thunderbird/candidates/27.0b1-candidates/build1/logs/release-comm-beta-win32_repack_1-bm85-build1-build0.txt.gz) but actually when you run the command manually you get a crash like on the attached screen shot.
Looks like make vs pymake issue, moving to the proper component.
Component: Platform Support → Build Config
Product: Release Engineering → Thunderbird
QA Contact: coop
Target Milestone: --- → Thunderbird 27.0
any good ideas guys
My current theories are:

1) Try pymake on staging, see if we hit the same issues as before, if we do:
1a) try and fix them again
1b) move comm-central under mozilla-central
2) See if gmake 4 will work

I think 1 is more likely, not sure which between 1a and 1b would be best.
That is, unless anyone else has any ideas as to what's happening here.
I thought we unsupported GNU make < 4 on Windows for all job types a long time ago. Or did we never get pymake working with l10n repacks.

Switch to pymake or glandium's special builds of GNU make 4 (preferably the latter, since that's the long-term solution).
(In reply to Gregory Szorc [:gps] from comment #5)
> I thought we unsupported GNU make < 4 on Windows for all job types a long
> time ago. Or did we never get pymake working with l10n repacks.

AFAIK, pymake *is* used for l10n repacks. *Firefox* l10n repacks.
 
> Switch to pymake or glandium's special builds of GNU make 4 (preferably the
> latter, since that's the long-term solution).

The long-term solution is actually a pristine gnu make 4, so i'd actually advise against the special build and use pymake instead.
Is this still a thing?
And if so, after 3 years still a blocker?  (as it is currently categorized)
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #7)
> Is this still a thing?
> And if so, after 3 years still a blocker?  (as it is currently categorized)

If TB 50 beta release Windows repacks didn't have any problems, I should think this can be resolved.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: