Open Bug 1631167 Opened 8 months ago Updated 6 months ago

mozregression GUI does not sanity check user-specified good/bad builds

Categories

(Testing :: mozregression, defect, P4)

defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: raysatiro, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

I'm using mozregression: 4.0.4.dev0+ga387b60.d20200417 and running the GUI from the repo:

pip install -e . && python gui/build.py run

Set bad build id to 20160923030450 and set good build id to 20160730030204.

Actual results:

Unlike the CLI which prefers classic mode first (sanity check the good and bad to make sure they are actually good and bad) the GUI does not do this, and seems to prefer no-first-check and goes right to bisecting. The first build it checks is right in the middle:

2020-04-18T01:09:05.863000: INFO : application_buildid: 20160827030436
2020-04-18T01:09:05.863000: INFO : application_changeset: c724ae8bb7b867b6bc65efa1049c0322457ff4b0
2020-04-18T01:09:05.863000: INFO : application_display_name: Nightly

Expected results:

I think the GUI should default to classic mode like the CLI does.

The priority flag is not set for this bug.
:wlach, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(wlachance)
Flags: needinfo?(wlachance)
Priority: -- → P4

The severity field is not set for this bug.
:wlach, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(wlachance)
Flags: needinfo?(wlachance)
You need to log in before you can comment on or make changes to this bug.