Oh, it makes sense that GPG is getting activated when you try to do a local publish, but it should build/publish locally fine without it.
A lot of our tests are somewhat randomized and thus have some small chance of failure on a bad seed. Most of them have fixed seeds so that they reproduce and don't fail. Its possible that we missed this one (or that there is a real error with it). If it runs fine on its own but not when run as a suite for you, it is possible it is using a shared random object between tests and we may need to make it test-specific or the like. I'll take a look at it.
With regards to the "no tests found", generally this is fixed by changing the pattern for matching class names to run unit tests. We use the convention of ending the class name with Test, so something like matching *Test.class should help work in Eclipse.