delta/python-packages/gitpython.git/git/test, branch 2.1.7

Merge branch 'master' into master

2017-09-28T13:44:55+00:00

Merge branch 'master' into master

2017-09-28T13:17:25+00:00

Merge branch 'master' into adding_setup_for_git_executable

2017-09-28T13:13:15+00:00

Merge pull request #654 from vathpela/worktrees

2017-09-28T13:02:53+00:00

worktrees: make non-packed refs also work correctly.

Fix test_docs

2017-09-28T12:37:52+00:00

It's not portable to test for a secific author name

worktrees: make non-packed refs also work correctly.

2017-08-22T21:12:54+00:00

Turns out aec58a9 did the right thing for /packed/ refs, but didn't work
correctly on /unpacked/ refs.  So this patch gives unpacked refs the
same treatment.

Without the fix here, the test added will cause this traceback:

======================================================================
ERROR: Check that we find .git as a worktree file and find the worktree
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/pjones/devel/github.com/GitPython/git/test/lib/helper.py", line 92, in wrapper
    return func(self, path)
  File "/home/pjones/devel/github.com/GitPython/git/test/test_repo.py", line 938, in test_git_work_tree_dotgit
    self.assertIsInstance(repo.heads['aaaaaaaa'], Head)
  File "/home/pjones/devel/github.com/GitPython/git/util.py", line 893, in __getitem__
    raise IndexError("No item found with id %r" % (self._prefix + index))
IndexError: No item found with id 'aaaaaaaa'

Woops.

Things I've learned:
- test_remote doesn't work currently if you start on a branch.  I think
  it never did?
- Because of 346424da, all *sorts* of stuff in the test suite doesn't
  work if you name your development branch "packed-refs"
  (This seems like a bug...)

Signed-off-by: Peter Jones

test if it accepts environment variables in commands

2017-07-19T22:57:07+00:00

Renamed refresh to setup and removed alias function & added unittest

2017-07-09T20:07:31+00:00

Renamed to simplify and avoid issue with nose tests trying to use
`setup` as a setup for testing. Unittest implements basic test for
refreshing with a bad git path versus a good git path.

Update changelog and improve docs on skipped test

2017-07-01T11:59:17+00:00

[skip ci]

Try to ignore test on windows as it fails for the wrong reasons

2017-07-01T11:59:17+00:00

Here is the error log we see:

======================================================================
ERROR: test_git_submodules_and_add_sm_with_new_commit (git.test.test_submodule.TestSubmodule)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\projects\gitpython\git\test\lib\helper.py", line 92, in wrapper
    return func(self, path)
  File "C:\projects\gitpython\git\test\test_submodule.py", line 709, in test_git_submodules_and_add_sm_with_new_commit
    smm.git.commit(m="new file added")
  File "C:\projects\gitpython\git\cmd.py", line 425, in 
    return lambda *args, **kwargs: self._call_process(name, *args, **kwargs)
  File "C:\projects\gitpython\git\cmd.py", line 877, in _call_process
    return self.execute(call, **exec_kwargs)
  File "C:\projects\gitpython\git\cmd.py", line 688, in execute
    raise GitCommandError(command, status, stderr_value, stdout_value)
GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git commit -m new file added
  stderr: '
*** Please tell me who you are.