Ronny Pfannschmidt
132f0006d3
enhance travis setuptools_scm situation
...
* add setuptools_scm to the development requirements
* print the own version at install time
* unshallow the repo and fetch all tags
2017-04-01 18:25:45 +02:00
Thomas Waldmann
740312f725
Merge branch '1.0-maint' into merge-1.0-maint
...
# Conflicts:
# requirements.d/development.txt
# tox.ini
2017-01-15 01:15:04 +01:00
Thomas Waldmann
555c6a95e4
add pip and setuptools to requirements file, fixes #2030
...
sometimes the system pip/setuptools is rather old and causes
warnings or malfunctions in the primary virtual env.
2017-01-14 23:23:36 +01:00
Marian Beermann
ecad0ed53a
Merge branch '1.0-maint' into merge/1.0-maint
...
# Conflicts: ... everywhere ...
# .travis.yml
# Vagrantfile
# borg/testsuite/key.py
# docs/changes.rst
# docs/quickstart.rst
# docs/usage.rst
# docs/usage/upgrade.rst.inc
# src/borg/archive.py
# src/borg/archiver.py
# src/borg/crypto.pyx
# src/borg/helpers.py
# src/borg/key.py
# src/borg/remote.py
# src/borg/repository.py
# src/borg/testsuite/archive.py
# src/borg/testsuite/archiver.py
# src/borg/testsuite/crypto.py
# src/borg/testsuite/helpers.py
# src/borg/testsuite/repository.py
# src/borg/upgrader.py
# tox.ini
2017-01-12 15:01:41 +01:00
Thomas Waldmann
853cfb703b
parallelizing tests via pytest-xdist
2017-01-06 05:48:50 +01:00
Thomas Waldmann
6290e70c80
partially remove virtualenv/pip version requirement, fixes #1738
...
Is needed only for python 3.2 support.
For normal development, we expect you have py34+ for borg 1.1.
For vagrant, it is still needed because of older VMs like wheezy (py32).
Not needed for Travis-CI any more, we moved to trusty VMs (py34) there.
2016-11-29 21:30:23 +01:00
Thomas Waldmann
19729d3983
requirements: use latest pytest-cov, not blocked by py32 any more
...
also: pytest-benchmark 3.x is released, just use latest
2016-01-24 15:16:05 +01:00
Thomas Waldmann
dabac6a4ed
use mock from stdlib, fixes #145
2016-01-24 14:57:48 +01:00
Thomas Waldmann
a237c1fb53
add virtualenv<14.0 to requirements so tox does not pull in a py32 incompatible one
2016-01-22 23:12:08 +01:00
Thomas Waldmann
2b8b31bca5
update pytest-benchmark requirement
...
it's released now. \o/
2015-11-22 15:39:31 +01:00
Thomas Waldmann
3d2a1da983
use latest pytest-benchmark
2015-11-07 16:13:24 +01:00
Thomas Waldmann
f8b536890b
use pytest-benchmark from pypi
2015-10-14 00:54:32 +02:00
Thomas Waldmann
08d96099f1
pytest-benchmark: use git master code, fixes py32 issues
2015-10-12 00:52:52 +02:00
Thomas Waldmann
a9b1e591ab
upgrade pytest-benchmark to a4
2015-10-11 16:25:43 +02:00
Thomas Waldmann
a5a6ba0d77
integrate pytest-benchmark, test create, extract, list, delete, info, check, help, fixes #146
...
Instead of "realistic data", I chose the test data to be either all-zero (all-ascii-zero to be precise)
or all-random and benchmark them separately.
So we can better determine the cause (deduplication or storage) in case we see some performance regression.
"help" is benchmarked to see the minimum runtime when it basically does nothing.
also:
- refactor archiver execution core functionality into exec_cmd() so it can be used more flexibly
- tox: usually we want to skip benchmarks, only run them if requested manually
- install pytest-benchmark - run tox with "-r" to have it installed into your .tox envs
2015-10-11 16:07:11 +02:00
Thomas Waldmann
5864bd76eb
fix test coverage / codecov.io, use xcode6.4
2015-08-08 18:31:41 +02:00
Roberto Polli
0b226aec7a
add development.txt and modify tox.ini
2015-07-25 15:39:42 +02:00
