PackageEvaluator.jl is a script that runs nightly.
It attempts to load all Julia packages and run their tests (if available) on both the stable
version of Julia (0.3) and the nightly build of the unstable version (0.4).
The results of this script are used to generate a package listing
enhanced with testing results. This service also benefits package developers by notifying them if
their package breaks for some reason (caused by e.g. changes in Julia, changes in dependencies,
or broken binary dependencies.)
Currently PackageEvaluator attempts to find your test scripts using a heuristic, preferring the
standarized test/runtests.jl whenever present. Using test/runtests.jl allows people to test
your package using simply Pkg.test("DoubleDouble"), with any testing-only dependencies being
installed by looking at test/REQUIRE.
Your package doesn't appear to have a test/runtests.jl file. PackageEvaluator is going to move
away from auto-detecting tests and will instead only test packages with a test/runtests.jl
file. This change will take place in about a month.
You can:
Add the file and tag a new version. You may in fact have already added this file but not
tagged a new version. PackageEvaluator only tests your latest tagged verison, so you must tag
for the file to be detected.
Chose to do nothing. PackageEvaluator will stop attempting to test your package, and the testing
status will be reported as "not possible".
If you'd like help or more information, please just reply to this issue.
dpsanders
commented
8 years ago
PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their tests (if available) on both the stable version of Julia (0.3) and the nightly build of the unstable version (0.4). The results of this script are used to generate a package listing enhanced with testing results. This service also benefits package developers by notifying them if their package breaks for some reason (caused by e.g. changes in Julia, changes in dependencies, or broken binary dependencies.)
Currently PackageEvaluator attempts to find your test scripts using a heuristic, preferring the standarized
test/runtests.jlwhenever present. Usingtest/runtests.jlallows people to test your package using simplyPkg.test("DoubleDouble"), with any testing-only dependencies being installed by looking attest/REQUIRE.Your package doesn't appear to have a
test/runtests.jlfile. PackageEvaluator is going to move away from auto-detecting tests and will instead only test packages with atest/runtests.jlfile. This change will take place in about a month.You can:
If you'd like help or more information, please just reply to this issue.