Merge remote branch 'branchable/master'
This commit is contained in:
commit
4a3a80f432
2 changed files with 114 additions and 0 deletions
|
@ -0,0 +1,66 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
|
||||
nickname="Jimmy"
|
||||
subject="comment 9"
|
||||
date="2011-02-09T09:12:52Z"
|
||||
content="""
|
||||
[a0826293][] fixed the last problem, there is coreutils available in macports, if they are installed you get the gnu equivalents but they are prefixed with a g (e.g. gchmod instead of chmod), I guess not everyone will have these install or prefer these on [[install/OSX]]
|
||||
|
||||
Some more tests fail now...
|
||||
|
||||
<pre>
|
||||
Testing 1:blackbox:3:git-annex unannex:1:with content
|
||||
### Failure in: 1:blackbox:3:git-annex unannex:1:with content
|
||||
foo is not a symlink
|
||||
Testing 1:blackbox:4:git-annex drop:0:no remotes
|
||||
### Failure in: 1:blackbox:4:git-annex drop:0:no remotes
|
||||
drop wrongly succeeded with no known copy of file
|
||||
Testing 1:blackbox:4:git-annex drop:1:with remote
|
||||
Testing 1:blackbox:4:git-annex drop:2:untrusted remote
|
||||
Testing 1:blackbox:5:git-annex get
|
||||
Testing 1:blackbox:6:git-annex move
|
||||
Testing 1:blackbox:7:git-annex copy
|
||||
### Failure in: 1:blackbox:7:git-annex copy
|
||||
move --to of file already there failed
|
||||
Testing 1:blackbox:8:git-annex unlock/lock
|
||||
### Error in: 1:blackbox:8:git-annex unlock/lock
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:9:git-annex edit/commit:0
|
||||
### Error in: 1:blackbox:9:git-annex edit/commit:0
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:9:git-annex edit/commit:1
|
||||
### Error in: 1:blackbox:9:git-annex edit/commit:1
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:10:git-annex fix
|
||||
### Error in: 1:blackbox:10:git-annex fix
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:11:git-annex trust/untrust/semitrust
|
||||
### Error in: 1:blackbox:11:git-annex trust/untrust/semitrust
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:12:git-annex fsck:0
|
||||
### Error in: 1:blackbox:12:git-annex fsck:0
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:12:git-annex fsck:1
|
||||
### Error in: 1:blackbox:12:git-annex fsck:1
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:12:git-annex fsck:2
|
||||
### Error in: 1:blackbox:12:git-annex fsck:2
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:13:git-annex migrate:0
|
||||
### Error in: 1:blackbox:13:git-annex migrate:0
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:13:git-annex migrate:1
|
||||
### Error in: 1:blackbox:13:git-annex migrate:1
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Testing 1:blackbox:14:git-annex unused/dropunused
|
||||
### Error in: 1:blackbox:14:git-annex unused/dropunused
|
||||
forkProcess: resource exhausted (Resource temporarily unavailable)
|
||||
Cases: 30 Tried: 30 Errors: 11 Failures: 3
|
||||
test: failed
|
||||
make: *** [test] Error 1
|
||||
</pre>
|
||||
|
||||
On a side note, I think I found another bug in the testing. I had tested in a virtual machine in archlinux (a very recent updated version) Please see the report here [[tests fail when there is no global .gitconfig for the user]]
|
||||
|
||||
[a0826293]: http://git.kitenet.net/?p=git-annex;a=commit;h=7a0826293e0ac6c0000f49a1618c1c613b909aa1
|
||||
"""]]
|
|
@ -0,0 +1,48 @@
|
|||
Make test fails when git doesn't know what identity to give to commits
|
||||
|
||||
<pre>
|
||||
|
||||
Testing 1:blackbox:0:git-annex init
|
||||
Cases: 30 Tried: 7 Errors: 0 Failures: 0
|
||||
*** Please tell me who you are.
|
||||
|
||||
Run
|
||||
|
||||
git config --global user.email "you@example.com"
|
||||
git config --global user.name "Your Name"
|
||||
|
||||
to set your account's default identity.
|
||||
Omit --global to set the identity only in this repository.
|
||||
|
||||
fatal: empty ident <jtang@lenny.localdomain> not allowed
|
||||
### Failure in: 1:blackbox:0:git-annex init
|
||||
init failed
|
||||
Testing 1:blackbox:1:git-annex add:0
|
||||
Cases: 30 Tried: 8 Errors: 0 Failures: 1
|
||||
*** Please tell me who you are.
|
||||
</pre>
|
||||
|
||||
I guess most users testing git-annex probably have a .gitconfig sitting in their home directories already so the above never cropped up. This failure was initially found in a clean and fresh install of a virtual machine with archlinux and repeated again on my archlinux laptop.
|
||||
|
||||
Update: I pulled the master on my rhel5 test machine and moved my .gitconfig out of the way, the tests passes and continues but I still get a "warning message" from git.
|
||||
|
||||
<pre>
|
||||
Testing 1:blackbox:3:git-annex unannex:1:with content
|
||||
Cases: 30 Tried: 12 Errors: 0 Failures: 0[master fce0cde] content removed from git annex
|
||||
Committer: Jimmy Tang <jtang@removed.removed.tcd.ie>
|
||||
Your name and email address were configured automatically based
|
||||
on your username and hostname. Please check that they are accurate.
|
||||
You can suppress this message by setting them explicitly:
|
||||
|
||||
git config --global user.name "Your Name"
|
||||
git config --global user.email you@example.com
|
||||
|
||||
After doing this, you may fix the identity used for this commit with:
|
||||
|
||||
git commit --amend --reset-author
|
||||
|
||||
2 files changed, 1 insertions(+), 2 deletions(-)
|
||||
delete mode 120000 foo
|
||||
</pre>
|
||||
|
||||
I guess it also depends a bit on how git figures out who it is is committing and how the machine in question is configured with hostnames and domain names.
|
Loading…
Add table
Reference in a new issue