tests: run populate with /dev/null as input

The test driver runs commands in a shell whose input is the console it
talks through, /dev/hvc0, which is a terminal.  ssh -t, which
writeDeploy's allocateTTY passes for remote targets, allocates a terminal
then, and reads the console, so the deploy-*-allocateTTY scenarios of
remote and sudo targets hang.  Populate and writeDeploy read nothing, so
their input is /dev/null, and ssh allocates no terminal, as these
scenarios expect.

0 files changed, 0 insertions, 0 deletions