1176708 - Results of Nightly-bisection not showing the dates anymore

Status: RESOLVED FIXED

(Testing :: mozregression, defect)

Description

[Elbart]

0.30:
 0:06.27 LOG: MainThread Bisector INFO Last good revision: 3c26bef95d54 (2015-06-15)
 0:06.27 LOG: MainThread Bisector INFO First bad revision: ce863f9d8864 (2015-06-16)
 0:06.28 LOG: MainThread Bisector INFO Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3c26bef95d54&tochange=ce863f9d8864


0.31+:
 0:21.12 LOG: MainThread Bisector INFO Last good revision: 3c26bef95d54
 0:21.12 LOG: MainThread Bisector INFO First bad revision: ce863f9d8864
 0:21.12 LOG: MainThread Bisector INFO Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3c26bef95d54&tochange=ce863f9d8864

Comment 1

[Julien Pagès (:parkouss)]

Hey Jonathan, would you be interested for this bug ?

Comment 2

[jonathan.pigree]

Hey why not.

Comment 3

[jonathan.pigree]

This bug seems obsolete to me. The result looks like this now:
 4:58.03 LOG: MainThread Bisector INFO Newest known good nightly: 2014-12-11
 4:58.03 LOG: MainThread Bisector INFO Oldest known bad nightly: 2014-12-15

But now it is the commit sha1 which is missing? Is it a bug?

Comment 4

[Julien Pagès (:parkouss)]

Jonathan, this is about the text displayed at the end of the bisection. you can make it appear pretty fast if you hit CTRL-C while downloading the first build:

(mozregression)[jp@parkouss mozregression-mozilla]$ mozregression -g 2015-08-01 -b 2015-08-05
/home/jp/.mozregression.cfg loaded
 0:04.51 LOG: MainThread Bisector INFO Downloading build from: https://archive.mozilla.org/pub/mozilla.org/firefox/nightly/2015/08/2015-08-03-03-02-07-mozilla-central/firefox-42.0a1.en-US.linux-x86_64.tar.bz2
^C=== Downloaded 2% =====

Interrupted.
 0:07.67 LOG: Dummy-9 Bisector INFO Last good revision: aeb85029c3b3
 0:07.67 LOG: Dummy-9 Bisector INFO First bad revision: f3b757156f69
 0:07.67 LOG: Dummy-9 Bisector INFO Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=aeb85029c3b3&tochange=f3b757156f69

 0:07.67 LOG: Dummy-9 Bisector INFO To resume, run:
 0:07.67 LOG: Dummy-9 Bisector INFO mozregression --good=2015-08-01 --bad=2015-08-05 --app=firefox  --bits=64

Comment 5

[jonathan.pigree]

Oh great. I finally see what you were talking about. You have to quit mozregression with ctrl+c to see this.

Comment 6

[Elbart]

(In reply to jonathan.pigree from comment #3)
> This bug seems obsolete to me. The result looks like this now:
>  4:58.03 LOG: MainThread Bisector INFO Newest known good nightly: 2014-12-11
>  4:58.03 LOG: MainThread Bisector INFO Oldest known bad nightly: 2014-12-15
> 
> But now it is the commit sha1 which is missing? Is it a bug?

The date is only shown when you prematurely "exit" a nightly-bisection, as you did in your example.

When you're down to the range being between to consecutive nightlies, you only get the has, e.g.

Was this nightly build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry
', 'back' or 'exit' and press Enter): g
 2:03.37 LOG: MainThread Bisector INFO Narrowed nightly regression window from [
2015-08-03, 2015-08-05] (2 days) to [2015-08-04, 2015-08-05] (1 days) (~0 steps
left)
 2:03.37 LOG: MainThread Bisector INFO Got as far as we can go bisecting nightli
es...
 2:03.39 LOG: MainThread Bisector INFO Last good revision: 5b54831761b1
 2:03.39 LOG: MainThread Bisector INFO First bad revision: f3b757156f69
 2:03.39 LOG: MainThread Bisector INFO Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5b54831761b1&tocha
nge=f3b757156f69

Comment 7

[jonathan.pigree]

Okay. Thanks. Julien. Now I can investigate.

Comment 8

[Julien Pagès (:parkouss)]

Yep, thanks Elbart for the precision. So to make things clear, this is printed when nightly bisection ends. So another easy way to get there is to just use a one day range for the dates (this implies that the nigthly bisection is finished, and mozregression will then try to bisect inbounds):

(mozregression)[jp@parkouss mozregression-mozilla]$ mozregression -g 2015-08-01 -b 2015-08-02
/home/jp/.mozregression.cfg loaded
 0:04.19 LOG: MainThread Bisector INFO Got as far as we can go bisecting nightlies...
 0:04.19 LOG: MainThread Bisector INFO Last good revision: aeb85029c3b3
 0:04.19 LOG: MainThread Bisector INFO First bad revision: 32712cd01159
 0:04.19 LOG: MainThread Bisector INFO Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=aeb85029c3b3&tochange=32712cd01159

Comment 9

[Elbart]

When using "skip" (i.e. crashing nightly build with a certain setting), you could still reach the end of nightly-bisection with a range >1d.

Comment 10

[jonathan.pigree]

Hey, thanks for all the tips. Will try to capitalize on all this. I managed to make this work but not in all cases. So it still needs some work.

Comment 11

[Julien Pagès (:parkouss)]

Jonathan is busy with other stuff right now. So let's see if someone else is interested for this bug. :)

Comment 12

[Julien Pagès (:parkouss)]

mikeling, maybe you would be interested to work on this bug ?

Comment 13

[MikeLing]

Attachment: PR for bug 1176708

Comment 14

[Julien Pagès (:parkouss)]

Comment on attachment 8678547 [details] [review]
PR for bug 1176708

Thanks Mikeling!

Merged manually in https://github.com/mozilla/mozregression/commit/77acf563f4e1ef189c516833eef2ae47a5c2438b.

Comment 15

[Julien Pagès (:parkouss)]

Will be included in next release.