Closed Bug 838789 Opened 11 years ago Closed 11 years ago

Release builds trigger tests too many times

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: bhearsum)

Details

Attachments

(2 files)

Looking at http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/None-candidates/buildNone/logs/?C=M;O=D I thought we were triggering two or three sets of the same test suite, but looking at https://secure.pub.build.mozilla.org/buildapi/pending for the ones that haven't been picked up yet, I see that we're actually triggering five.

That's far too many, considering how never anyone actually looks at them. Does help explain why we always get a huge backlog of jobs for other branches throughout the entire day when there's a release build, though.
We should dial this down to 1 time. I almost want to turn them off completely, but that seems wrong...
Assignee: nobody → bhearsum
Attachment #712433 - Flags: review?(rail)
Attachment #712433 - Flags: review?(rail) → review+
Attachment #712433 - Flags: checked-in+
Attached patch same for mobileSplinter Review
Just noticed this new file.
Attachment #712512 - Flags: review?(rail)
Attachment #712512 - Flags: review?(rail) → review+
But because of bug 836162 you would have been okay missing it, since for now at least we're actually triggering mobile tests zero times.
Attachment #712512 - Flags: checked-in+
The first patch is in production, this is fixed (considering the second one is actually no-op).
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
in production
Second portion is also in production.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: