Perform tasks concurrently over multiple copies of your repo.
The name pando comes from the clonal colony of "multiple" trees that are actually one single organism. It is latin for "I spread out".
HERE BE DRAGONS. This extension is in the early stages of development and may cause data loss or worse. Only use if you're very comfortable with git and have backups.
There may also be backwards incompatible changes for each version.
Will be easily installable from crates.io once it's more mature.
bash
git clone (repo url here)
cd cargo-pando
cargo install --path .
Upgrading
bash
git pull origin master
cargo install --path . --force
.travis.yml, or just using all the installed ones.target/pando per toolchain, e.g. target/pando/1.31.0. Note that this is destructive.
The configured target dir in your cargo config is respected.rustup run TOOLCHAIN_HERE cargo test or some other action in each copy of the repo-- in parallel.
For example, cargo +1.31.0 test in target/pando/1.31.0/working_dir.Output is logged to target/pando/TOOLCHAIN_HERE/output, and each line is printed next to the progress bar for the checkout.
If your tests rely on external resources, keep in mind they won't be in the expected location.
If there are exclusive resources, you'll have to synchronize access yourself.
More parallelism doesn't always make things faster, especially since compilation can be IO intensive as well as CPU intensive.
See cargo pando help for more details.
Test the working directory against the toolchains listed in .travis.yml:
bash
cargo pando test
Test against every installed toolchain except the default,
limiting it to 2 cargo tests at any given time:
bash
cargo pando --all test -j 2
Test each specified toolchain, but only doc tests:
bash
cargo pando -t stable -t beta test -- --doc
If you want to run a single command across all of the checkouts at once,
use print, cut, and xargs:
bash
cargo pando print | cut -f 2 | xargs ls
Run an arbitrary command against each checkout,
substituting the name of the toolchain where applicable:
bash
cargo pando each echo the toolchain '{}' has been copied
If the command does not lend itself well to the single line given
by the progress bars, xargs can help again:
bash
cargo pando print | cut -f 1 | xargs -L 1 -P 2 echo the toolchain is
Test the given toolchain against the index (stage) of your repo.
Useful if you're incrementally adding changes to a commit and you want to check that your work in progress still works.
bash
cargo pando --index -t stable test
See how much space the pando directory is taking up:
bash
du -sh target/pando
Get rid of it!
bash
rm -rf target/pando
(I can't remember what those last two were about. Oh well.)