1354451 - Mozregression-gui can't switch to fx-team repository

Status: RESOLVED WONTFIX

(Testing :: mozregression, defect)

Description

[684sigma]

I found a problem in mozregression-gui 0.9.7 tool.
When I was trying to get regression range in bug 1353831, Mozregression-gui 0.9.7 couldn't  bisect in fx-team repository.
Here's how to reproduce the bug:

First scenario:
1. Start bisection to find regrsesion range in bug 1353831 between 2016-08-03 and 2016-08-04
2. Follow the steps listed in that bug to mark builds as good and bad

Result: mozregression doesn't switch from 'mozilla-central' repository to 'fx-team'
Expected: mozregression switches from 'mozilla-central' to 'fx-team', because it switches to 'mozilla-inbound' and 'autoland'


Second scenario:
1. Run a single build, select repository 'fx-team' and changeset '4e8b0579b51108c1d7c60bd1d70053136ec4521d'

Result: can't choose 'fx-team'
Expected: should be possible to test 'fx-team'

Comment 1

[684sigma]

I investigated this in case it's regression of mozregression, and it appears it is. Mozregression-gui 0.9.6 supports 'fx-team'.
Then I found commit
https://github.com/mozilla/mozregression/commit/3efabd6d2d0b2cd3dc907d165116eb3853afd14f
that removes 'fx-team' to fix a rare with 'autoland'. I think that it's not a good replacement.
William, your opinion?

Comment 2

[684sigma]

* to fix a rare bug with 'autoland'

Comment 3

[William Lachance (:wlach)]

Hi 684sigma :) The fx-team branch doesn't exist anymore and I believe the policy is to expire integration branch data after 4 months, so the data will shortly be gone. It's pretty clear what the culprit was in the linked bug (I NI'ed someone to try and get some movement). Autoland replaces fx-team as the integration branch of choice.

It is possible that for older bugs a mozilla-central regression range will be the best you can do.