1195524 - mozregression can longer find inbound builds

Status: RESOLVED INVALID

(Testing :: mozregression, defect)

Description

[Chris Peterson [:cpeterson]]

mozregression no longer seems to be able to find inbound builds that should exist because they are only a couple days old. I am using mozregression 0.41.

mozregression --good-rev 3f135a8ead22 --bad-rev 8cba870a352c

0:00.78 LOG: MainThread Bisector INFO Getting inbound builds between 3f135a8ead22 and 8cba870a352c
0:01.57 LOG: MainThread Bisector INFO No inbound data found.

Comment 1

[Julien Pagès (:parkouss)]

Hmm, with the debug option:

mozregression --good-rev 3f135a8ead22 --bad-rev 8cba870a352c --log-mach-level debug
/home/jp/.mozregression.cfg loaded
 0:00.41 LOG: MainThread Bisector INFO Getting inbound builds between 3f135a8ead22 and 8cba870a352c
 0:01.74 LOG: MainThread Build Finder DEBUG Found 1 pushlog entries using `https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?fromchange=3f135a8ead22&tochange=8cba870a352c`
 0:01.74 LOG: MainThread Bisector INFO No inbound data found.

looking at https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?fromchange=3f135a8ead22&tochange=8cba870a352c there is no results. (mozregression say it found one pushlog entry because the result of json-pushes is inclusive from one side only - http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmo/pushlog.html#query-parameters)

So it seems to me that there is not enough data to bisect. Though the error is not clear, I will look into that.

Comment 2

[Julien Pagès (:parkouss)]

Well, looking more into it, it seems that

https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?changeset=8cba870a352

and

https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?changeset=3f135a8ead22

give the same results, because they are in the same push. So this will be the same inbound build, and mozregression can only bisect builds (that are generated by pushes).

Comment 3

[Chris Peterson [:cpeterson]]

Thanks for investigating, Julien. It looks like this is my misunderstanding, not a mozregression problem. :)

On mozilla-central, this changeset range looks like it includes merges from inbound, b2ginbound, and fx-team. So it makes sense that this changeset range on mozilla-inbound would only include that one inbound push.

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3f135a8ead22&tochange=8cba870a352c