596705 - start using MOZ_SYMBOLS_EXTRA_BUILDID for one of the mac builds (0.7.x buildbots only)

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect, P4)

Description

[[e-mail] (:bhearsum)]

Now that we have two different Mac builds, we need to start using MOZ_SYMBOLS_EXTRA_BUILDID on branches where we build both. Otherwise, there's a small, but real, chance that we'll collide in naming the symbols' .txt file on the symbol server.

...or maybe we don't care because the old ppc+i386 build is going away.

Filed for posterity nonetheless.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Where did you notice this ? We're doing this for macosx64 builds already, or at least should be.

Comment 2

[[e-mail] (:bhearsum)]

I noticed it on the 4.0b6 builds, actually:
[ffxbld@dm-symbolpush01 symbols_ffx]$ ls *4.0b6-*
firefox-4.0b6-Darwin-20100913221327-symbols.txt
firefox-4.0b6-Darwin-20100913221842-symbols.txt
firefox-4.0b6-Darwin-20100914072643-symbols.txt
firefox-4.0b6-Darwin-20100914073111-symbols.txt
firefox-4.0b6-Linux-20100913220446-symbols.txt
firefox-4.0b6-Linux-20100913222219-linux64-symbols.txt
firefox-4.0b6-Linux-20100914072313-symbols.txt
firefox-4.0b6-Linux-20100914072643-linux64-symbols.txt
firefox-4.0b6-WINNT-20100913231938-symbols.txt
firefox-4.0b6-WINNT-20100914083612-symbols.txt


...which means that we're missing it in mozilla2/config.py:
http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2/config.py#l228

Comment 3

[Aki Sasaki (not active)]

Do we have any more branches that build both?