Closed IainNZ closed 10 years ago
INFO: Installing AWS v0.1.8
INFO: Installing BinDeps v0.2.12
INFO: Installing Calendar v0.4.1
INFO: Installing Codecs v0.1.0
INFO: Installing CommonCrawl v0.0.0
INFO: Installing GZip v0.2.12
INFO: Installing HTTPClient v0.1.4
INFO: Installing ICU v0.4.0
INFO: Installing Iterators v0.1.2
INFO: Installing LibCURL v0.1.3
INFO: Installing LibExpat v0.0.4
INFO: Installing PublicSuffix v0.0.1
INFO: Installing URIParser v0.0.2
INFO: Building ICU
INFO: Building LibCURL
INFO: Package database updated
ERROR: mkdir: File exists
in mkdir at file.jl:40
in mkdir at file.jl:38
in include at boot.jl:244
in include_from_node1 at loading.jl:128
while loading /home/idunning/pkgtest/.julia/v0.3/CommonCrawl/test/test.jl, in expression starting on line 5
INFO: Package database updated
Looks like it might be fixed though? Bump in METADATA?
It needs to be bumped in METADATA, but I don't think that will fix this issue. The tests require valid AWS credentials to be run successfully. It also involves quite a bit of data transfer out of S3.
Should we exclude this package from PackageEvaluator instead?
Sounds good, I'll do it now
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, CommonCrawl, 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.