Closed Bug 343732 Opened 19 years ago Closed 19 years ago

boomer l10n died on 1.8 branch on July 3rd.

Categories

(Webtools Graveyard :: Tinderbox, defect)

PowerPC
macOS
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: coop)

References

()

Details

July 3rd, 5pm, MacOSX Darwin 7.9.0 boomer Clbr Tb-Release goes yellow and doesn't come back. It took MacOSX Darwin 7.9.0 boomer Clbr Fx-Release with it, thus we have no l10n builds for Mac. This is blocking the Firefox 2.0 b1 release.
Assignee: build → ccooper
Status: NEW → ASSIGNED
Looks like the machine got rebooted (or crashed and restarted) on July 3rd around 17:30. I've restarted tinderbox now. Not sure if it's pertinent, but the Tb log in question ends as follows: cd src; make export cd io; make export cc -o prfdcach.o -c -pipe -Wmost -fno-common -no-cpp-precomp -nostdinc -isy stem /Developer/SDKs/MacOSX10.2.8.sdk/usr/include/gcc/darwin/3.3 -isystem /Devel oper/SDKs/MacOSX10.2.8.sdk/usr/include -F/Developer/SDKs/MacOSX10.2.8.sdk/System /Library/Frameworks -O2 -g -fPIC -UDEBUG -DMOZILLA_CLIENT=1 -DNDEBUG=1 -DXP_UNI X=1 -DDARWIN=1 -DHAVE_BSD_FLOCK=1 -Dppc=1 -DXP_MACOSX=1 -DHAVE_STRERROR=1 -DFOR CE_PR_LOG -D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I/builds/tinde rbox/Tb-Mozilla1.8-l10n/Darwin_7.9.0_Clobber/mozilla/dist/include/nspr -I../../. ./pr/include -I../../../pr/include/private prfdcach.c ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ <more garbled garbage follows>
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Component: Tinderbox Configuration → Tinderbox
Product: mozilla.org → Webtools
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.