From the logs, it looks like the worker attempted to upload the artifact with exponential backoff algorithm for 15 minutes, before giving up: ``` [taskcluster 2020-07-20T23:36:49.591Z] Uploading artifact public/test_info/wpt_raw.log from file build\blobber_upload_dir\wpt_raw.log with content encoding "gzip", mime type "text/plain" and expiry 2021-07-20T21:58:48.435Z [taskcluster:error] Error uploading artifact: S3 returned status code 400 which could be an intermittent issue - see https://bugzilla.mozilla.org/show_bug.cgi?id=1394557 [taskcluster 2020-07-20T23:51:59.223Z] Uploading artifact public/test_info/wptreport.json from file build\blobber_upload_dir\wptreport.json with content encoding "gzip", mime type "application/octet-stream" and expiry 2021-07-20T21:58:48.435Z ``` I suspect this was a networking/connectivity issue from the Windows 7 worker, talking to S3, as noted in bug 1394557, S3 returns a 400 HTTP status code due to connection inactivity, which could happen if there was a network blip that lasted 15 minutes. I suspect this was a one-time thing during high load / poor performance of something in between the worker and s3. If it doesn't happen again, I'd suggest closing this bug and consider it a flake.
Bug 1654126 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
From the logs, it looks like the worker attempted to upload the artifact with exponential backoff algorithm for 15 minutes, before giving up: ``` [taskcluster 2020-07-20T23:36:49.591Z] Uploading artifact public/test_info/wpt_raw.log from file build\blobber_upload_dir\wpt_raw.log with content encoding "gzip", mime type "text/plain" and expiry 2021-07-20T21:58:48.435Z [taskcluster:error] Error uploading artifact: S3 returned status code 400 which could be an intermittent issue - see https://bugzilla.mozilla.org/show_bug.cgi?id=1394557 [taskcluster 2020-07-20T23:51:59.223Z] Uploading artifact public/test_info/wptreport.json from file build\blobber_upload_dir\wptreport.json with content encoding "gzip", mime type "application/octet-stream" and expiry 2021-07-20T21:58:48.435Z ``` I suspect this was a networking/connectivity issue from the Windows 7 worker, talking to S3, as noted in bug 1394557, S3 returns a 400 HTTP status code due to connection inactivity, which could happen if there was a network blip that lasted 15 minutes. I suspect this was a one-time thing during high load / poor performance of something in between the worker and s3. If it doesn't happen again, I'd suggest closing this bug and consider it a flake. The worker acted appropriately, in that it tried for 15 minutes to publish the artifact, before giving up.