Turn off the buildbot-based Gip tests on the B2G release branches

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
3 years ago
2 months ago

People

(Reporter: RyanVM, Assigned: RyanVM)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
Right up front, this is only being proposed for the B2G release branches, i.e. b2g32/b2g34/b2g37. The Taskcluster-based jobs running on trunk/master will not be affected.

At this point, Gip is still running across all trees, but hidden by default. We are constantly dealing with buildbot limitations caused by the number of different test suites we have to support. Therefore, one suggestion that came up was to fully turn off the buildbot-based Gip tests on the B2G release branches.

In the case of debug, they've been busted for basically ever and it seems highly unlikely anybody is going to start paying attention to them now all of a sudden. In the case of opt, it seems unlikely we're going to spend any time watching them at this point as QA resources are shifted to v2.5. Also, presumably any Gip -> Gij test migration work will be happening on trunk/master and will not be backported to older releases.

Johan, Naoki suggested that you make the final call on this. Does the above sound reasonable to you? I think that at a bare minimum, we should turn off debug, but I don't see much reason to keep opt around either at this point.
Flags: needinfo?(jlorenzo)
Let's deactivate them on the old branches (b2g37 and below). Like you said, no back port will happen, but each of the branches you mentioned is code complete. The risk of having a regression caught by Gip is low.
Blocks: 1186188
Flags: needinfo?(jlorenzo)
(Assignee)

Comment 2

3 years ago
Created attachment 8637193 [details] [diff] [review]
kill Gip on buildbot

Builders removed
- b2g_ubuntu64_vm mozilla-b2g32_v2_0 debug test gaia-ui-test
- b2g_ubuntu64_vm mozilla-b2g32_v2_0 opt test gaia-ui-test
- b2g_ubuntu64_vm mozilla-b2g34_v2_1 debug test gaia-ui-test
- b2g_ubuntu64_vm mozilla-b2g34_v2_1 opt test gaia-ui-test
- b2g_ubuntu64_vm mozilla-b2g34_v2_1s debug test gaia-ui-test
- b2g_ubuntu64_vm mozilla-b2g34_v2_1s opt test gaia-ui-test
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 debug test gaia-ui-test-accessibility
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 debug test gaia-ui-test-functional-1
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 debug test gaia-ui-test-functional-2
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 debug test gaia-ui-test-functional-3
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 debug test gaia-ui-test-unit
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 opt test gaia-ui-test-accessibility
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 opt test gaia-ui-test-functional-1
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 opt test gaia-ui-test-functional-2
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 opt test gaia-ui-test-functional-3
- b2g_ubuntu64_vm mozilla-b2g37_v2_2 opt test gaia-ui-test-unit
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r debug test gaia-ui-test-accessibility
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r debug test gaia-ui-test-functional-1
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r debug test gaia-ui-test-functional-2
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r debug test gaia-ui-test-functional-3
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r debug test gaia-ui-test-unit
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r opt test gaia-ui-test-accessibility
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r opt test gaia-ui-test-functional-1
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r opt test gaia-ui-test-functional-2
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r opt test gaia-ui-test-functional-3
- b2g_ubuntu64_vm mozilla-b2g37_v2_2r opt test gaia-ui-test-unit
Attachment #8637193 - Flags: review?(catlee)

Updated

3 years ago
Attachment #8637193 - Flags: review?(catlee) → review+
(Assignee)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.