Current coverage is 90.12% (diff: 100%)

Merging #230 into master will not change coverage

@@             master       #230   diff @@
==========================================
  Files            32         32          
  Lines          1013       1013          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits            913        913          
  Misses           82         82          
  Partials         18         18          

Powered by Codecov. Last update 19c1fb3...396bdfa

Thanks for your contribution!

In regards to your other problem, what version of Go are you using and what OS?

These are my code versions (I'm running arch GNU/Linux):

» go version
go version go1.7.1 linux/amd64
» glide -v
glide version 0.12.3

Here's the strange output I get:

» cd ~/go/src/github.com/opencontrol/compliance-masonry
» glide up --all-dependencies
[INFO]  Downloading dependencies. Please wait...
[INFO]  --> Fetching updates for github.com/onsi/gomega.
...
[INFO]  --> Fetching updates for github.com/golang/protobuf.
[ERROR] Could not find /home/fen/.glide/cache/src/https-golang.org-x-sys/unix: open /home/fen/.glide/cache/src/https--home-fen-.glide-cache-src-https-golang.org-x-sys-unix: no such file or directory
[ERROR] Dependency golang.org/x/sys/unix (/home/fen/.glide/cache/src/https-golang.org-x-sys/unix) failed to resolve: open /home/fen/.glide/cache/src/https--home-fen-.glide-cache-src-https-golang.org-x-sys-unix: no such file or directory.
[ERROR] Failed to retrieve a list of test dependencies: open /home/fen/.glide/cache/src/https--home-fen-.glide-cache-src-https-golang.org-x-sys-unix: no such file or directory

Any suggestions as to how to debug are greatly appreciated.

I've been playing a bit with freedonia and now want to add links to tests that can provide evidence of compliance implementations, ideally templated for a particular operating system such that they can be tailored for a particular installation. Suggestions as to how to go about this are also greatly appreciated.

Thanks for blazing this trail!

Could you also run go env and share that output?

Is there a reason you want to update the dependencies? (e.g. is there a dependency that's broken / needs an update?) That glide up command is optional in the CONTRIBUTING.md doc and will update the current deps.