Closed Bug 699478 Opened 14 years ago Closed 12 years ago

Don't try to create snippets for Darwin_x86_64-gcc3 for build# > 1

Categories

(Release Engineering :: Release Automation, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: coop, Unassigned)

References

()

Details

(Whiteboard: [release-process-improvement][automation][updates])

During 8.0b6 build2, the release-mozilla-beta-updates builder failed on the create_buildN_snippets step with the following errors: Error reading from /builds/slave/rel-m-beta-updates/build/temp/firefox/8.0b5-8.0b6/aus2.test/Firefox/8.0/Darwin_x86_64-gcc3/20111026191032/af/betatest/complete.txt [Errno 2] No such file or directory: '/builds/slave/rel-m-beta-updates/build/temp/firefox/8.0b5-8.0b6/aus2.test/Firefox/8.0/Darwin_x86_64-gcc3/20111026191032/af/betatest/complete.txt' Error reading from /builds/slave/rel-m-beta-updates/build/temp/firefox/8.0b5-8.0b6/aus2.test/Firefox/8.0/Darwin_x86_64-gcc3/20111026191032/ak/betatest/complete.txt [Errno 2] No such file or directory: '/builds/slave/rel-m-beta-updates/build/temp/firefox/8.0b5-8.0b6/aus2.test/Firefox/8.0/Darwin_x86_64-gcc3/20111026191032/ak/betatest/complete.txt' ... I asked about it on IRC: [1:34pm] bhearsum: we don't create snippets for that build target anymore, so that's fine [1:34pm] bhearsum: i'm surprised it's even looking for them for that build target... This didn't bite us on build1, so I'm guessing this build target is only sneaking in for respins (build# > 1).
Priority: -- → P3
Product: mozilla.org → Release Engineering
Found in triage... is this even still an issue?
Component: Other → Release Automation
We only run create_buildN_snippets for build > 1, as coop says. And we must have fixed this along the way because we didn't hit it for either 23.0.1 build2 or 24.0b1 build2.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
I verified we only have Darwin_x86_64-gcc3-u-i386-x86_64 and Darwin_x86-gcc3-u-i386-x86_64 for those releases.
You need to log in before you can comment on or make changes to this bug.