Open Bug 1334853 Opened 5 years ago
mozregression --launch BUILDID used near-build instead of exact
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170126004004 Steps to reproduce: Using mozregression from git master (gui-0.9.6) to launch a specific buildid but it launches a near build instead of the one I want. mozregression --repo mozilla-inbound --launch 20161222030652 Actual results: It launches build 20161222151452 and not 20161222030652. 0:03.13 INFO: Running mozilla-inbound build built on 2016-12-23 01:29:22.068000, revision 698b5719 ... 0:04.88 INFO: application_buildid: 20161222151452 0:04.88 INFO: application_changeset: 698b5719c9ee8cefe0a894c37c1ef865e34d0769 0:04.88 INFO: application_name: Firefox 0:04.88 INFO: application_repository: https://hg.mozilla.org/integration/mozilla-inbound 0:04.88 INFO: application_version: 53.0a1 Expected results: It should have launched 20161222030652. I recently did a bisect that was traced to that build and if I run it by commit it works: mozregression --launch 96cf05faacfe6ba130553323bde9f0bb80298c8a 0:03.12 INFO: Running mozilla-inbound build built on 2016-12-22 12:39:17.707000, revision 96cf05fa ... 0:04.83 INFO: application_buildid: 20161222030652 0:04.83 INFO: application_changeset: 96cf05faacfe6ba130553323bde9f0bb80298c8a 0:04.83 INFO: application_name: Firefox 0:04.83 INFO: application_repository: https://hg.mozilla.org/integration/mozilla-inbound 0:04.83 INFO: application_version: 53.0a1
You need to log in before you can comment on or make changes to this bug.