juju test fails to run, unhelpful error

'juju test -e local' gets me further, so I suspect I don't have some magic environment variable set pointing to the single environment in my environments.yaml.

I've run into this as well with 1.23 with multiple environments, can't figure out what I'm missing or the true error is. Both of these environments bootstrap, deploy with no issues. I can test to an openstack env however.

$ juju test
juju-test INFO : Starting test run on local using Juju 1.23.3
juju-test CRITICAL: 'local does not exist in /home/jill/.juju/environments.yaml'
ERROR subprocess encountered error code 1

$ juju charm test -e amazon
juju-test INFO : Starting test run on amazon using Juju 1.23.3
juju-test CRITICAL: 'amazon does not exist in /home/jill/.juju/environments.yaml'
ERROR subprocess encountered error code 1

$ cat /home/jill/.juju/environments.yaml

default: local
default-series: trusty

environments:
    local:
        type: local

    amazon:
        type: ec2
        region: us-west-2
---snip---

After purging/reinstalling juju I received the below much more helpful error:

$ juju charm test -e local
juju-test INFO : Starting test run on local using Juju 1.23.3
juju-test CRITICAL: while parsing a block mapping
  in "<string>", line 1, column 1:
    default: local
    ^
expected <block end>, but found '<block mapping start>'
  in "<string>", line 16, column 3:
      jillr-canonistack:

My environments.yaml had 4-space indents for environments which were not working with charmtools, and 2-spaced for working envs (very sloppy on my part). Juju doesn't have seem to any issue with this, but 'charm test' apparently does. After fixing everything to 2-space indenting testing with my local provider is fine.