JuliaCrypto / Nettle.jl

Julia wrapper around nettle cryptographic hashing/encryption library providing MD5, SHA1, SHA2 hashing and HMAC functionality, as well as AES encryption/decryption

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[PackageEvaluator.jl] Your package Nettle may have a testing issue.

IainNZ opened this issue · comments

This issue is being filed by a script, but if you reply, I will see it.

PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their test (if available) on both the stable version of Julia (0.2) and the nightly build of the unstable version (0.3).

The results of this script are used to generate a package listing enhanced with testing results.

The status of this package, Nettle, on...

  • Julia 0.2 is 'Tests fail, but package loads.' PackageEvaluator.jl
  • Julia 0.3 is 'Tests pass.' PackageEvaluator.jl

'No tests, but package loads.' can be due to their being no tests (you should write some if you can!) but can also be due to PackageEvaluator not being able to find your tests. Consider adding a test/runtests.jl file.

'Package doesn't load.' is the worst-case scenario. Sometimes this arises because your package doesn't have BinDeps support, or needs something that can't be installed with BinDeps. If this is the case for your package, please file an issue and an exception can be made so your package will not be tested.

This automatically filed issue is a one-off message. Starting soon, issues will only be filed when the testing status of your package changes in a negative direction (gets worse). If you'd like to opt-out of these status-change messages, reply to this message.

Thanks! This is actually a really neat notification, and found a bug that I wouldn't have otherwise found.

Ideally, I'd like these automatic posts to only include the information relevant to the error this package encountered. E.g. since this post shows that I had "Tests fail, but package loads", I don't need to see the information regarding "Package doesn't load", but there should definitely be a link to a webpage describing all the possible states that can appear here, for future reference/package maintainers that are trying to integrate all the different possible states across all their packages.

Yes indeed. From now on they'll be only on negative change, so I'll just display a message for the new status.
Should I close now?

I'll go ahead and close, thanks.