| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[skip ci]
|
|\ |
|
| |
| |
| |
| | |
[skip ci]
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
+ On MINGW-git, daemon exists but if invoked as 'git daemon', DAEMON
CANNOT DIE!
+ So, launch `git-daemon` on Apveyor, but
- remote TCs fail due to paths problems.
+ Updated README instructions on Windows.
+ Restore disabled remote TCs on Windows.
+ Disable failures on daemon-tests only the last moment
(raise SkipTest) so when ready, it will also pass.
|
|/
|
|
| |
[travisci skip]
|
|
|
|
|
|
| |
This has been the case for Windows as well, and is now
made official.
Certain tests already fail on windows, for example.
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
Fixes #508
|
|
|
|
|
|
| |
They don't seem to work anymore.
[skip ci]
|
|
|
|
|
|
|
|
| |
They do not get updated for some reason, generally the
site is not quite production ready it seems, or is by
now overwhelmed.
[skip ci]
|
|
|
|
| |
Fixes #478
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main point is that from now on, tests are required to add
new features. If the fix is minor enough, not having a test
is probably alright.
That distinction is not represented in the contribution guide
as more tests are better - people should prefer to have a test
whenever they contribute anything.
My motivation to finally do this is the sad realization that
I grow too unconfident about the quality of some contributions
without having tests that proof they are valid. It's not enough
to not break anything that exists, as the current test-suite is
certainly not perfect either.
|
|
|
|
|
|
| |
More information in the respective issue.
Fixes #453
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Coveralls was disabled a while ago because it would prevent merging
PRs from the phone.
|
| |
|
|
|
|
| |
We are not too good, but nothing to shy away from.
|
|
|
|
| |
Because there are none.
|
|
|
|
|
|
| |
Currently, people put it onto the mailing list and on stack overflow
[ci skip]
|
|
|
|
|
|
| |
That way they are protected from regression.
Fixes #239
|
|
|
|
|
|
| |
GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations.
Related to #239
|
|
|
|
| |
[ci skip]
|
| |
|
| |
|
|
|
|
| |
And to trigger travis to build and work ...
|
|
|
|
| |
More to come, especially when it's about strings
|
|
|
|
|
| |
There is more work to do though, as many imports are still incorrect.
Also, there are still print statements
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
README.md
requirements.txt
setup.py
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tox https://pypi.python.org/pypi/tox is a thin wrapper around virtualenv
which let you craft a fresh python environement to execute command in.
It creates the env with virtualenv, install dependencies, run python
setup.py install in it and then execute whatever command you want it to
do and report status.
To do so I simply:
- listed tests dependencies in test-requirements.txt (which are just
nose and mock)
- provide a tox.ini file which describe how to install the dependencies
and execute nosetests
- added the module 'coverage' to the list of test dependencies
To run tests simply:
pip install tox && tox
That will execute the test command 'nosetests' using python2.6 and then
python 2.7.
The additional env 'cover' can be run using: tox -ecover.
|
| |
| |
| |
| |
| | |
More and more packages are listing their dependencies in
requirements.txt which make it trivial to maintain and install them.
|
|/ |
|
|
|
|
| |
Relative dates are not that precise, so instead of 3 years ago
set it the last release date to July 2011.
|
| |
|
|
|
|
| |
[skip ci]
|
| |
|
|
|