1507954 - Unhandled exception in docker-worker when image tarball is 0 bytes

Status: RESOLVED WONTFIX

(Taskcluster :: Workers, defect)

Description

[Nick Alexander :nalexander [he/him]]

While testing Bug 1501720, I triggered

https://tools.taskcluster.net/groups/d9Oh8KubSaCh6lv1U-E8LA/tasks/UWEy4QjMRd2wuJje55kuKw/details

it looks like the worker hung, but before it did :dustin checked the papertrail logs and found:

2:01 PM Nov 16 20:02:11 docker-worker.aws-provisioner.us-west-1b.ami-a45db0c7.c5-9xlarge.i-0b0bdd2b46af77751 docker-worker: {"type":"Uploading public/image.tar.lz4","source":"uploadToS3","taskId":"UWEy4QjMRd2wuJje55kuKw","runId":0,"artifactName":"public/image.tar.lz4"}
2:01 PM Nov 16 20:02:11 docker-worker.aws-provisioner.us-west-1b.ami-a45db0c7.c5-9xlarge.i-0b0bdd2b46af77751 docker-worker: Unhandled rejection at [object Promise].
2:01 PM Nov 16 20:02:11 docker-worker.aws-provisioner.us-west-1b.ami-a45db0c7.c5-9xlarge.i-0b0bdd2b46af77751 docker-worker: Error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?

That's an unhandled exception that we should address.