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

[IainNZ]

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, RandomMatrices, on...

• Julia 0.2 is 'Package doesn't load.'
• Julia 0.3 is 'Package doesn't load.'

'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.

[IainNZ]

INFO: Installing ArrayViews v0.4.4
INFO: Installing BinDeps v0.2.12
INFO: Installing Catalan v0.0.1
INFO: Installing Distributions v0.4.7
INFO: Installing GSL v0.1.1
INFO: Installing ODE v0.1.0
INFO: Installing PDMats v0.2.0
INFO: Installing Polynomial v0.1.1
INFO: Installing RandomMatrices v0.0.0
INFO: Installing StatsBase v0.4.0
INFO: Installing URIParser v0.0.2
INFO: Building GSL
INFO: Package database updated
ERROR: Could not find the GNU Scientific Library.
Please ensure that libgsl is installed on your system and is available on the system path.
 in error at error.jl:21
 in include at boot.jl:244 (repeats 2 times)
 in reload_path at loading.jl:152
 in _require at loading.jl:67
 in require at loading.jl:54
 in include at boot.jl:244
 in reload_path at loading.jl:152
 in _require at loading.jl:67
 in require at loading.jl:51
 in include at boot.jl:244
 in include_from_node1 at loading.jl:128
while loading /home/idunning/pkgtest/.julia/v0.3/GSL/src/ConvertGSL.jl, in expression starting on line 49
while loading /home/idunning/pkgtest/.julia/v0.3/GSL/src/GSL.jl, in expression starting on line 6
while loading /home/idunning/pkgtest/.julia/v0.3/RandomMatrices/src/RandomMatrices.jl, in expression starting on line 3
while loading /home/idunning/pkgtest/.julia/v0.3/RandomMatrices/testusing.jl, in expression starting on line 1
INFO: Package database updated

Should I exclude from automatic testing?

[jiahao]

What I should do is remove the dependency on GSL.

[IainNZ]

Now seeing on newly tagged version:

ERROR: permutation_calloc not defined
 in schedule_and_wait at task.jl:251
 in consume at task.jl:162
 in expectation at /home/idunning/pkgtest/.julia/v0.3/RandomMatrices/src/HaarSymbolic.jl:142
 in expectedtrace at /home/idunning/pkgtest/.julia/v0.3/RandomMatrices/src/HaarSymbolic.jl:276
 in include at ./boot.jl:245
 in include_from_node1 at ./loading.jl:128
 in include at ./boot.jl:245
 in include_from_node1 at loading.jl:128
 in process_options at ./client.jl:285
 in _start at ./client.jl:354

[jiahao]

In principle I have fixed the GSL-dependency issue

[IainNZ]

Wooah, RandomMatrices doesn't even appear on pkg.julialang.org...

[jiahao]

Probably my fault for neglecting it for so long

[IainNZ]

That normally happens when the package can't even be installed, i.e. some fails in Pkg.add. Checking the internal logs:

##### Current package: RandomMatrices
      !!!!!! evalPkg failed

so thats awkward. I wonder: did the last tagged sha point to a commit in the repo? The other thing that can cause that is somehow the dependencies being unsatisfiable (e.g. installing Julia 0.4 only package on Julia 0.3, which is expected to fail)

[jiahao]

I might have bunged up the tagging of v0.0.3 - I did it through the web interface to trigger the DOI assignment by Zenodo. I just did that again for v0.1.0.