-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PackageEvaluator.jl] Your package CellularAutomata may have a testing issue. #4
Comments
Tagged newest version with tests. |
#5 should fix the new failure http://iainnz.github.io/packages.julialang.org/?pkg=CellularAutomata&ver=0.3 |
Thanks for the quick fix! I assume a new version has to be tagged again with these changes? |
Yes, PackageEvaluator only looks at tagged versions. |
Ok, I'll do that in a minute. Thanks for the help! |
Testing seems to work now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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, CellularAutomata, on...
'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.
The text was updated successfully, but these errors were encountered: