1395999 - Win 7 ref test failing on OCC configured hardware

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Mark Cornmesser [:markco] OOO 2024/04/15]

From: https://tools.taskcluster.net/groups/L2a4nxuLQ32DZKO-LylsJQ/tasks/L2a4nxuLQ32DZKO-LylsJQ/details

Fetch https://queue.taskcluster.net/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip into memory
retry: attempt #2 caught SSLError exception: ('The read operation timed out',)
retry: Failed, sleeping 60 seconds before retrying
retry: Calling fetch_url_into_memory with args: (), kwargs: {'url': 'https://queue.taskcluster.net/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip'}, attempt #3

Comment 1

[Mark Cornmesser [:markco] OOO 2024/04/15]

I am able to wget the file without issue. 
The current Python version is 2.7.11 .

Comment 2

[Mark Cornmesser [:markco] OOO 2024/04/15]

dustin: Any ideas?

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Sep 01 02:05:26 taskcluster-queue heroku/router: at=info method=GET path="/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip" host=queue.taskcluster.net request_id=c0ad0f92-9bd8-4974-af86-f95d5f463b6d fwd="63.245.214.82" dyno=web.3 connect=0ms service=237ms status=303 bytes=609 protocol=https 
Sep 01 02:05:26 taskcluster-queue heroku/router: at=info method=GET path="/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip" host=queue.taskcluster.net request_id=524a0c9c-504c-4331-b209-70a57c76c294 fwd="63.245.214.82" dyno=web.17 connect=0ms service=225ms status=303 bytes=609 protocol=https 
Sep 01 02:06:34 taskcluster-queue heroku/router: at=info method=GET path="/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip" host=queue.taskcluster.net request_id=0b2ad30b-19c0-4d9f-b747-db96e8542768 fwd="63.245.214.82" dyno=web.25 connect=0ms service=231ms status=303 bytes=609 protocol=https 
Sep 01 02:08:08 taskcluster-queue heroku/router: at=info method=GET path="/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip" host=queue.taskcluster.net request_id=3ae8d2cd-eb8f-42e3-88a7-4eb42c9f0199 fwd="63.245.214.82" dyno=web.23 connect=0ms service=228ms status=303 bytes=609 protocol=https 
Sep 01 02:10:41 taskcluster-queue heroku/router: at=info method=GET path="/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip" host=queue.taskcluster.net request_id=854939f8-580c-404d-a105-7834f7d8e542 fwd="63.245.214.82" dyno=web.20 connect=0ms service=225ms status=303 bytes=609 protocol=https 
Sep 01 02:15:14 taskcluster-queue heroku/router: at=info method=GET path="/v1/task/bzdWOVcoQ4GR_89xpMVBnQ/artifacts/public/build/target.crashreporter-symbols.zip" host=queue.taskcluster.net request_id=18a6c085-b075-41bc-a054-dd839426ce28 fwd="63.245.214.82" dyno=web.5 connect=1ms service=255ms status=303 bytes=609 protocol=https 

I see the requests for that file in the queue.  That 303 would have been to cloud-mirror, and I can't find anything in the logs there.  This looks like just an S3 timeout or trouble getting to S3?