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.
Where did you notice this ? We're doing this for macosx64 builds already, or at least should be.
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
Summary: start using MOZ_SYMBOLS_EXTRA_BUILDID for one of the mac builds → start using MOZ_SYMBOLS_EXTRA_BUILDID for one of the mac builds (0.7.x buildbots only)
Do we have any more branches that build both?
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.