Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up Travis CI #7

Closed
brettcannon opened this issue Aug 22, 2016 · 2 comments
Closed

Set up Travis CI #7

brettcannon opened this issue Aug 22, 2016 · 2 comments

Comments

@brettcannon
Copy link
Member

With caching turn on in the .travis.yml file, the base set of benchmarks should complete for a single run before Travis times out and kills the VM. That would be enough to make sure simple things like the django -> django_template rename breakage don't occur again.

@vstinner
Copy link
Member

For tests, I'm using --debug-single-sample command line option: it asks to only run each benchmark once using a single worker process (or maybe even no worker process at all, depending on the benchmark is run).

  • "python3 bench.py run --debug-single-sample" => 14 seconds (10 benchmarks)
  • "python3 bench.py run --debug-single-sample -b all" => 28 seconds (44 benchmarks)

The purpose of tests is to check that running benchmarks work, not to check the results.

@vstinner
Copy link
Member

Done: see .travis.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants