Open Bug 1857759 Opened 1 year ago Updated 1 year ago

Bisecting stops before the end without errors

Categories

(Testing :: mozregression, defect, P3)

Desktop
Windows 10
defect

Tracking

(Not tracked)

People

(Reporter: tbertels+bugzilla, Unassigned)

Details

Attachments

(3 files)

Attached file bisect.log

Using mozregression-gui 6.0.0

End of log:
2023-10-07T19:38:18.812000: INFO : Narrowed integration regression window from [3810447e, 906260e4] (21 builds) to [1e022917, 906260e4] (11 builds) (~3 steps left)

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1e022917b1abe226ddb2e5b87979f345e4da5a05&tochange=906260e46b192bed1b9c55bcbe14d8faeae543a0

https://hg.mozilla.org/mozilla-central/json-pushes?%20fromchange=1e022917b1abe226ddb2e5b87979f345e4da5a05&tochange=906260e46b192bed1b9c55bcbe14d8faeae543a0

Attached image error.png

Note that if I try to start a new bisection with the last range [1e022917, 906260e4], I get this error message, even though it does seem to contain pushlogs https://hg.mozilla.org/mozilla-central/json-pushes?%20fromchange=1e022917&tochange=906260e4

Attached image window.png

This is what the window looks like when the bisecting stops.

Attachment #9357258 - Attachment mime type: application/octet-stream → text/plain

Couple of things here:

  • The URL that you referenced in comment 1 contains a space between the ? and the query parameters, so you are actually getting unfiltered results in that case.
  • The URLs in the original bug report are using autoland pushlogs (i.e., repo is set to autoland for the bisection) which is why you get different bisection results there, than when getting the pushlog from mozilla-central.
  • It looks like because both changesets are part of the same merge push (to mozilla-central), the API returns no results, which is why it gives you that error at the end. Restart the bisection with the repo set to autoland and you should be able to retry from where you left off.

I don't know what caused the bisection to initially stop, but let me know if this is an issue that is still happening after changing the repo parameter. I was not able to reproduce on my machine, neither on Windows 10 nor on macOS.

Flags: needinfo?(tbertels+bugzilla)
Priority: -- → P3
  • Indeed... 🤐
  • Thanks, I didn't know I had to change that!
    I'm guessing the default repository is chosen based on the application? Unfortunately, the repository field doesn't appear to be a drop-down menu until we click in what first looks like a text field.

About the initial stop, I can reproduce it by disabling the network card before clicking on the result (Good - Bad).
(Note that I first tried to change my IP address, but then I get an error message and it just retries)
What is strange is that it says it's found a build and starts Firefox but doesn't show the result buttons before I re-enable the network card.
I guess it preloads the autoland builds?

Here's the relevant part of the bisect log I attached previously:

2023-10-07T17:19:07.759000: DEBUG : urllib3.connectionpool: Starting new HTTPS connection (1): firefox-ci-tc.services.mozilla.com:443
2023-10-07T17:19:08.013000: DEBUG : urllib3.connectionpool: https://firefox-ci-tc.services.mozilla.com:443 "GET /api/index/v1/task/gecko.v2.autoland.revision.26eb1010f7661d2835301326a6219d269e85c723.firefox.win64-pgo HTTP/1.1" 404 433
2023-10-07T17:19:08.014000: DEBUG : taskcluster.utils: Received HTTP Status:    404
2023-10-07T17:19:08.014000: DEBUG : taskcluster.utils: Received HTTP Headers: {'Server': 'openresty', 'Date': 'Sat, 07 Oct 2023 15:19:08 GMT', 'Content-Type': 'application/json; charset=utf-8', 'Content-Length': '433', 'Content-Security-Policy': "report-uri /__cspreport__;default-src 'none';frame-ancestors 'none';", 'x-content-type-options': 'nosniff', 'x-for-trace-id': 'e28ec5653fdb3c5f7821e690b3c3a334', 'x-for-request-id': 'f2c59b15-2480-4eb4-b95b-e79676937b41', 'Access-Control-Allow-Origin': '*', 'Access-Control-Max-Age': '900', 'Access-Control-Allow-Methods': 'OPTIONS,GET,HEAD,POST,PUT,DELETE,TRACE,CONNECT', 'Access-Control-Request-Method': '*', 'Access-Control-Allow-Headers': 'X-Requested-With,Content-Type,Authorization,Accept,Origin,Cache-Control', 'Cache-Control': 'no-store no-cache must-revalidate', 'ETag': 'W/"1b1-dN0xFYnlau8uf4GS3JMB5Bjpl/A"', 'Strict-Transport-Security': 'max-age=31536000', 'Via': '1.1 google', 'Alt-Svc': 'clear'}
2023-10-07T17:19:08.014000: DEBUG : nothing found via route 'gecko.v2.autoland.revision.26eb1010f7661d2835301326a6219d269e85c723.firefox.win64-pgo'
2023-10-07T17:19:08.020000: WARNING : Skipping build 26eb1010f766: Unable to find build info using the taskcluster route 'gecko.v2.autoland.shippable.revision.26eb1010f7661d2835301326a6219d269e85c723.firefox.win64-opt'
2023-10-07T17:19:08.030000: DEBUG : using taskcluster route 
Flags: needinfo?(tbertels+bugzilla)

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

For more information, please visit BugBot documentation.

Flags: needinfo?(zeid)
Severity: -- → S3
Flags: needinfo?(zeid)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: