Closed Bug 473514 Opened 17 years ago Closed 17 years ago

OS X 10.5.2 mozilla-central l10n nightly for fa failing because autoconf-2.13 not in path

Categories

(Release Engineering :: General, defect, P1)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ehsan.akhgari, Assigned: bhearsum)

References

(
URL
)

Details

I've been seeing this a few times lately. It hasn't been consistent (sometimes the build succeeds) but anyway I thought I'd bring some attention to it. I don't know if this is specific to fa or happens with other locales as well. Example logs: http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-fa/1231673963.1231673979.18094.gz http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-fa/1231843786.1231843797.27856.gz http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-fa/1231902058.1231902070.25129.gz
Probably one of the slaves does not have autoconf symlinked properly.
Blocks: 465868
could this be caused by one of the new mac slaves recently moved into production pool?
Assignee: nobody → catlee
Priority: -- → P1
Yes, probably.
Assignee: catlee → bhearsum
I just logged onto moz2-darwin9-slave06 and 07 and these symlinks appear to have been created on Dec. 30. However, moz2-darwin9-slave05 says this, too, and I know for fact that it was created long before that. Did somebody create these symlinks after the nightlies finished yesterday? I'll keep an eye an out for these slaves when the nightlies start running this morning.
bm-xserve19 was missing the symlink. I've added it now, so this machine shouldn't have any more problems.
I don't see any failures such of this in the latest set of nightlies. This should be fixed now.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.