SSH runner failure: TERM environment variable not set.

Yesterday, I upgraded gitlab-ci-multi-runner to version 1.10.2. Since this upgrade, my GitLab CI SSH tasks have been failing with the error TERM environment variable not set, and exit code 1. Other builds (virtualbox, shell) are not affected. There are two different SSH servers, both running CoreOS.

I have turned on debugging, and the failure appears to be happening before my script gets a chance to run:

Running with gitlab-ci-multi-runner 1.10.2 (d171b73)
Using SSH executor...
+ set -eo pipefail
+ set +o noclobber
+ :
+ eval 'echo "Running on $(hostname) via gitlabci-xenial..."
'
+++ hostname
++ echo 'Running on c02 via gitlabci-xenial...'
+ exit 0
++ clear
Running on c02 via gitlabci-xenial...
TERM environment variable not set.
ERROR: Build failed: Process exited with: 1. Reason was:  ()

I upgraded directly from version 1.8.1 to 1.10.2. However, I have determined that the error occurs starting in 1.9.0.

$ gitlab-runner --version # Last working version
Version:      1.8.6
Git revision: 8b65fb3
Git branch:   1-8-stable
GO version:   go1.7.4
Built:        Wed, 25 Jan 2017 13:30:40 +0000
OS/Arch:      linux/amd64

$ gitlab-runner --version # First broken version
Version:      1.9.0
Git revision: 82714ae
Git branch:   1-9-stable
GO version:   go1.7.4
Built:        Thu, 22 Dec 2016 16:35:13 +0000


$ gitlab-runner --version # Latest version
Version:      1.10.2
Git revision: d171b73
Git branch:   1-10-stable
GO version:   go1.7.4
Built:        Wed, 25 Jan 2017 23:41:34 +0000
OS/Arch:      linux/amd64