The pkg.julialang.org checks slightly different things from the travis tests. In particular, while the travis tests run only when there is a change to the package code, these tests run nightly, and catch any package breakage due to changes to Julia, or any of your package dependencies.
If your dependencies are easy to install on linux, then I'm sure Ian will be happy to discuss installing them on the server. Alternatively, some packages can be marked "Untestable" rather than broken, if their dependencies are difficult to acquire. Packages with proprietary commercial dependencies are marked this way, for example. Either way, you can raise an issue at https://github.com/IainNZ/PackageEvaluator.jl/issues to discuss the specifics for your package. Regards - Avik On Thursday, 22 January 2015 14:51:16 UTC, Josh Langsfeld wrote: > > This is a fairly minor topic, but thought I'd bring it up anyway. I > noticed the pkg.julialang.org listings generate pass/fail info for the > package tests by running the tests locally rather than hooking into Travis. > This is a problem for me as my Travis script involves installing > dependencies, and so it will always list as "Tests fail" as things > currently are. > > Is there a way to have it display the travis build status instead? > > Thanks, > Josh >
