Closed
Bug 1450933
Opened 6 years ago
Closed 6 years ago
Intermittent Windows Mochitest Exception for Taskcluster resource-unavailable, log ends with Result: SUCCEEDED
Categories
(Taskcluster :: General, enhancement)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1394557
People
(Reporter: henrietta_maior, Unassigned)
Details
Exception log: https://treeherder.mozilla.org/logviewer.html#?job_id=171596784&repo=mozilla-central Push: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=4a3275936ddf871103b53e00608e2b8d5aee7e69&selectedJob=171596784 Taskcluster: https://tools.taskcluster.net/groups/ZqSzBMmXSrWXdhHzHiFOKA/tasks/WxEVDHl5R32SdpmYQPkFYw/runs/0 ^ here we can see that the exception's reason is: resource-unavailable
Updated•6 years ago
|
Summary: Intermittent Windows Mochitest Exception for Taskcluster resource-unavailable → Intermittent Windows Mochitest Exception for Taskcluster resource-unavailable, log ends with Result: SUCCEEDED
Comment 1•6 years ago
|
||
Hm, I don't know what resource-unavailable means. Pete, is this a new windows-7 thing?
Flags: needinfo?(pmoore)
Comment 2•6 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] pronoun: he from comment #1) > Hm, I don't know what resource-unavailable means. Pete, is this a new > windows-7 thing? This looks like a case of bug 1394557 which will be solved by the rollout today of bug 1399401. From the server logs I see: > 2018/04/03 11:01:08 Uploading artifact: logs/log_info.log > 2018/04/03 11:01:08 Request > 2018/04/03 11:01:08 PUT /WxEVDHl5R32SdpmYQPkFYw/0/public/logs/log_info.log?AWSAccessKeyId=AKIAJQESBGXODWDRTZUA&Content-Type=text%2Fplain&Expires=1522755079&Signature=P2tq6gTln%2Bko3lW6Hcs3uz1vsu8%3D HTTP/1.1 > Host: taskcluster-public-artifacts.s3-us-west-2.amazonaws.com > User-Agent: Go-http-client/1.1 > Content-Length: 3653590 > Content-Type: text/plain > Accept-Encoding: gzip > 2018/04/03 11:01:27 1 put requests issued to https://taskcluster-public-artifacts.s3-us-west-2.amazonaws.com/WxEVDHl5R32SdpmYQPkFYw/0/public/logs/log_info.log?AWSAccessKeyId=AKIAJQESBGXODWDRTZUA&Content-Type=text%2Fplain&Expires=1522755079&Signature=P2tq6gTln%2Bko3lW6Hcs3uz1vsu8%3D > 2018/04/03 11:01:27 Response > 2018/04/03 11:01:27 HTTP/1.1 400 Bad Request > Connection: close > Transfer-Encoding: chunked > Content-Type: application/xml > Date: Tue, 03 Apr 18 11:01:28 GMT > X-Amz-Id-2: meVD+/YnLlKM4EFZ9mCZI1NAmozlC0ldhPOkyT5scQvbxBrNYI1aSK1QlaLbCV4HrS6X8ywV02TDBoQSVyqYVAaoaQ8pFhuP > X-Amz-Request-Id: 904E69AB23D9AE47 > 17b > <?xml version="1.0" encoding="UTF-8"?><Error><Code>RequestTimeout</Code><Message>Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.</Message><RequestId>904E69AB23D9AE47</RequestId><HostId>meVD+/YnLlKM4EFZ9mCZI1NAmozlC0ldhPOkyT5scQvbxBrNYI1aSK1QlaLbCV4HrS6X8ywV02TDBoQSVyqYVAaoaQ8pFhuP</HostId></Error> > 0 This is likely due to bug
Flags: needinfo?(pmoore)
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•