This address #15 by pulling the Docker image, running the built-in test, and comparing the
summarized output to what is expected. The travis_wait 20 sleep 1200 & hack in .travis.yml is necessary because travis otherwise fails during assembly due to the lack of console output for over 10min while constructing the target De Bruijn graph within the Kallisto [build] command.
Right now the build is failing due to the fact that dictionaries are unordered, but this should be fixed once the Docker image is updated with the two included sorted additions to bracerlib/tasks.py.
If you like this, going forward it probably makes sense that you open a (free for open source) travis-ci account and link to this repository so builds automatically occur after a push or pull request. Something similar could be implemented for tracer, and also include tracer's unit tests.
Hi @mstubb ,
This address #15 by pulling the Docker image, running the built-in test, and comparing the summarized output to what is expected. The
travis_wait 20 sleep 1200 &
hack in.travis.yml
is necessary because travis otherwise fails during assembly due to the lack of console output for over 10min while constructing the target De Bruijn graph within theKallisto [build]
command.Right now the build is failing due to the fact that dictionaries are unordered, but this should be fixed once the Docker image is updated with the two included
sorted
additions tobracerlib/tasks.py
.If you like this, going forward it probably makes sense that you open a (free for open source) travis-ci account and link to this repository so builds automatically occur after a push or pull request. Something similar could be implemented for tracer, and also include tracer's unit tests.
Best, Derek