Closed Bug 1857845 Opened 1 year ago Closed 1 year ago

Mozregression Fenix http.client.RemoteDisconnected exception

Categories

(Testing :: mozregression, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: felix.bau, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/120.0

Steps to reproduce:

Start Mozregression 6.0.0

Actual results:

2023-10-09T05:57:59.618000: DEBUG : redo: retry: Caught exception:
Traceback (most recent call last):
File "urllib3\connectionpool.py", line 790, in urlopen
File "urllib3\connectionpool.py", line 536, in _make_request
File "urllib3\connection.py", line 461, in getresponse
File "http\client.py", line 1375, in getresponse
File "http\client.py", line 318, in begin
File "http\client.py", line 287, in _read_status
http.client.RemoteDisconnected: Remote end closed connection without response

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "requests\adapters.py", line 486, in send
File "urllib3\connectionpool.py", line 844, in urlopen
File "urllib3\util\retry.py", line 470, in increment
File "urllib3\util\util.py", line 38, in reraise
File "urllib3\connectionpool.py", line 790, in urlopen
File "urllib3\connectionpool.py", line 536, in _make_request
File "urllib3\connection.py", line 461, in getresponse
File "http\client.py", line 1375, in getresponse
File "http\client.py", line 318, in begin
File "http\client.py", line 287, in _read_status
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "redo_init_.py", line 170, in retry
return action(*args, **kwargs)
File "C:\Program Files (x86)\mozregression-gui_internal\mozregression\network.py", line 60, in _default_get
return _get(*args, **kwargs)
File "requests\sessions.py", line 602, in get
File "requests\sessions.py", line 589, in request
File "requests\sessions.py", line 703, in send
File "requests\adapters.py", line 501, in send
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2023-10-09T05:57:59.618000: DEBUG : redo: sleeping for 0.84s (attempt 1/3)
2023-10-09T05:57:59.830000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/fenix/nightly/2023/05/2023-05-07-16-03-42-fenix-114.0a1-android-arm64-v8a/ HTTP/1.1" 200 None
2023-10-09T05:58:00.463000: DEBUG : redo: attempt 2/3
2023-10-09T05:58:00.463000: DEBUG : redo: retry: calling _default_get with args: ('https://archive.mozilla.org/pub/fenix/nightly/2023/05/2023-05-07-04-03-22-fenix-114.0a1-android-arm64-v8a/',), kwargs: {'auth': None}, attempt #2
2023-10-09T05:58:00.703000: DEBUG : urllib3.connectionpool: https://archive.mozilla.org:443 "GET /pub/fenix/nightly/2023/05/2023-05-07-04-03-22-fenix-114.0a1-android-arm64-v8a/ HTTP/1.1" 200 None
2023-10-09T05:58:00.706000: DEBUG : got valid_builds [(0, {'build_url': 'https://archive.mozilla.org/pub/fenix/nightly/2023/05/2023-05-07-16-03-42-fenix-114.0a1-android-arm64-v8a/fenix-114.0a1.multi.android-arm64-v8a.apk'}), (1, {'build_url': 'https://archive.mozilla.org/pub/fenix/nightly/2023/05/2023-05-07-04-03-22-fenix-114.0a1-android-arm64-v8a/fenix-114.0a1.multi.android-arm64-v8a.apk'})]
2023-10-09T05:58:00.706000: DEBUG : Update build info from {'build_url': 'https://archive.mozilla.org/pub/fenix/nightly/2023/05/2023-05-07-16-03-42-fenix-114.0a1-android-arm64-v8a/fenix-114.0a1.multi.android-arm64-v8a.apk'}

Expected results:

I hope the log above is enough to figure what went wrong.

Either adb via usb had a short disconnect or the apk file wasn't available on the server on first try?

Did this only happen once, and were you able to successfully retry? It looks like a temporary network error. It would help if you had the full command that you were using at the time as well as part of the bug.

Flags: needinfo?(felix.bau)

ups, steps to reproduce didn't say that this happened during bisection.

yes, it happened only once
I used the GUI actually (on Windows 10)
Feel free to close this as not reproducible if it doesn't make sense to add code for catching these exceptions.
Next time something like this happens I'll provide the info you just requested and I'll try to reproduce it.

Flags: needinfo?(felix.bau)
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.