https://tools.taskcluster.net/task-inspector/#r562_LryQU6VdaxfDM5afw/0 { "provisionerId": "aws-provisioner-v1", "workerType": "b2gtest", "schedulerId": "-", "taskGroupId": "r562_LryQU6VdaxfDM5afw", "routes": [], "retries": 1, "created": "2015-07-07T15:44:58.028Z", "deadline": "2015-07-07T16:44:58.028Z", "expires": "2016-07-07T16:44:58.028Z", "scopes": [], "payload": { "image": "quay.io/djmitche/desktop-build:0.0.19", "command": [ "/bin/bash", "-c", "cd /home/worker/ && ./bin/checkout-sources.sh && ./workspace/build/src/testing/taskcluster/scripts/misc/repackage-jdk.sh" ], "env": { "GECKO_HEAD_REPOSITORY": "https://bitbucket.org/djmitche/mozilla-central", "GECKO_HEAD_REV": "83649d738a90", "VERSION": "7u79-2.5.5-0ubuntu0.14.04.2" }, "artifacts": { "public": { "type": "directory", "path": "/home/worker/artifacts", "expires": "2015-07-02T14:58:41.058Z" } }, "maxRunTime": 6000 }, "metadata": { "name": "Repackage JDK", "description": "Repackage the JDK/JRM from Ubuntu packages", "owner": "dustin@mozilla.com", "source": "http://tools.taskcluster.net/task-creator/" }, "tags": {}, "extra": {} }

This is the log output. It "hangs" at this point, after tar has logged the last thing I expect it to log ("VERSION" is lexically the last file in the directory): the live log continues to spin in the browser, but nothing further is logged. Eventually, the claim expires, and a new run begins.

The script isn't anything fancy; tar is the last thing it invokes. Is the docker-worker crashing on artifact upload?

Gary is seeing the container die. I just noted that "expires": "2015-07-02T14:58:41.058Z" is in the past. Perhaps that's causing the container to fail while processing artifacts.

@dustin, Bugs in artifact upload are known to cause docker-worker to hang. I think Edgar has a PR pending with a fix for this.

https://tools.taskcluster.net/task-inspector/#CRzI92fVTiiRtREjXDaCZQ/0 succeeded with the correct expires. So yes, I think this is bug 1181179

Technically there is two bugs: 1) we should reject if artifact.expires < task.deadline 2) we should not hang if there is an error during artifact upload Anyways, PR is pending for (2), so no need to track it.