x/build/cmd/gomote: 'gomote ssh' on plan9 can't see files installed by 'gomote put'

What did you do?

~$ gomote create plan9-386
user-bcmills-plan9-386-0

~$ gomote put14 user-bcmills-plan9-386-0

~$ gomote push user-bcmills-plan9-386-0
# […]

~/go/src$ gomote run user-bcmills-plan9-386-0 /bin/pwd
/tmp/workdir

~/go/src$ gomote run user-bcmills-plan9-386-0 /bin/ls /tmp/workdir
/tmp/workdir/go
/tmp/workdir/go1.4

~$ gomote ssh user-bcmills-plan9-386-0
$ ssh -p 2222 user-bcmills-plan9-386-0@farmer.golang.org # auth using https://github.com/bcmills.keys
# […]
# `gomote push` and the builders use:
# - workdir: /tmp/workdir
# - GOROOT: /tmp/workdir/go
# - GOPATH: /tmp/workdir/gopath
# - env: GO_BUILDER_NAME=plan9-386 GO_TEST_TIMEOUT_SCALE=2
# Happy debugging.
# […]

cpu% ls /tmp/workdir
ls /tmp/workdir
ls: /tmp/workdir: '/tmp/workdir' file does not exist
cpu%

What did you expect to see?

The files reported by gomote run […] /bin/ls /tmp/workdir are also visible when running ls /tmp/workdir under gomote ssh.

What did you see instead?

The files placed by gomote put14 and gomote push are not visible to the gomote ssh process.

@bradfitz tells me that the the ssh and buildlet processes don't share that part of the filesystem namespace.

@0intro, any ideas?