Closed Bug 1198728 Opened 9 years ago Closed 9 years ago

Stop scheduling gaia_ui_tests (Gip) on b2g_desktop across all branches

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(firefox43 fixed)

RESOLVED FIXED
Tracking Status
firefox43 --- fixed

People

(Reporter: ahal, Assigned: ahal)

Details

Attachments

(1 file)

On treeherder, the Gip tests have been hidden and mostly broken for many months. Recently, I made a change to marionette-client that broke them even further. After talking to jlorenzo, mwargers and jgriffin it seems like we should just remove them across all branches. As it currently stands, no one is looking at them and they are wasting machine resources.
There are some flame_kk_gaia_ui_tests_* variants in the tests directory, e.g:
https://dxr.mozilla.org/mozilla-central/source/testing/taskcluster/tasks/tests/flame_kk_gaia_ui_test_functional.yml

These don't seem to be run anywhere. Greg, you have your name in the blame.. do you know if these files are safe to remove as well? Or are they running somewhere I can't find in treeherder?
Flags: needinfo?(garndt)
Please do not remove those files.  They currently fun against flame device imags in our remote device lab.  They are reporting to treeherder staging only right now until we have more time to look at them and green them up.  Thank you for asking about them though!
Flags: needinfo?(garndt)
Thanks! I'll get you to review to make sure I don't mess anything up :).
Bug 1198728 - Stop scheduling gaia-ui-tests (Gip) on b2g_desktop across all branches, r=garndt
Attachment #8652871 - Flags: review?(garndt)
Summary: Stop scheduling gaia_ui_tests (Gip) across all branches → Stop scheduling gaia_ui_tests (Gip) on b2g_desktop across all branches
Comment on attachment 8652871 [details]
MozReview Request: Bug 1198728 - Stop scheduling gaia-ui-tests (Gip) on b2g_desktop across all branches, r=garndt

https://reviewboard.mozilla.org/r/17305/#review15403

This looks good to me, I don't see anything obvious breaking.  if you want, you can push to try and make sure that those jobs don't get scheduled based on the changes made to the try job_flags.yml
Attachment #8652871 - Flags: review?(garndt) → review+
Here's a try run:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2bc35908264f&exclusion_profile=false

Didn't get scheduled as desired. The other branches can't get tested on try, so I'll go ahead and land.
RyanVM points out that these are still scheduled via buildbot on older mozilla-b2g-* branches. Might as well get those too while we're at it.
Whiteboard: [leave-open]
Nvm, turns out they're already disabled there.
Whiteboard: [leave-open]
https://hg.mozilla.org/mozilla-central/rev/09db020e5dbe
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: