aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/Problems_running_make_on_osx/comment_17_62fccb04b0e4b695312f7a3f32fb96ee._comment
blob: 7c7200fb9e439d7991ca69d7af2d534653657077 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
 nickname="Jimmy"
 subject="comment 17"
 date="2011-02-13T10:46:54Z"
 content="""
Yeap, that did the trick. I just tested a few separate OSX 10.6.6 systems and the tests are better behaved now, only 3 failures now.

So the tests behave better (at least we don't get resource fork errors any more)
 
 * after the commit c319a3 without modifying the system limits (of 266 procs per user)
 * without the commit c319a3 and when I increase the system process limits to as much as OSX allows

On all the systems I tested on, I'm down to 3 failures now.

<pre>
### Failure in: 1:blackbox:3:git-annex unannex:1:with content
foo is not a symlink
### Failure in: 1:blackbox:4:git-annex drop:0:no remotes
drop wrongly succeeded with no known copy of file
Cases: 30  Tried: 20  Errors: 0  Failures: 2add foo ok
ok
Cases: 30  Tried: 24  Errors: 0  Failures: 2  Only 1 of 2 trustworthy copies of foo exist.
  Back it up with git-annex copy.
  Only 1 of 2 trustworthy copies of sha1foo exist.
  Back it up with git-annex copy.
  Bad file size; moved to /Users/jtang/develop/git-annex/.t/tmprepo/.git/annex/bad/WORM:1297594011:20:foo
  Bad file content; moved to /Users/jtang/develop/git-annex/.t/tmprepo/.git/annex/bad/SHA1:ee80d2cec57a3810db83b80e1b320df3a3721ffa
### Failure in: 1:blackbox:12:git-annex fsck:1
fsck failed to fail with content only available in untrusted (current) repository
Cases: 30  Tried: 26  Errors: 0  Failures: 3  Only 1 of 2 trustworthy copies of foo exist.
  Back it up with git-annex copy.
  The following untrusted locations may also have copies: 
  	90d63906-375e-11e0-8867-abb8a6368269  -- test repo
  Only 1 of 2 trustworthy copies of sha1foo exist.
  Back it up with git-annex copy.
  The following untrusted locations may also have copies: 
  	90d63906-375e-11e0-8867-abb8a6368269  -- test repo
Cases: 30  Tried: 30  Errors: 0  Failures: 3
</pre>

It's the same set of failures across all the OSX systems that I have tested on. Now I just need to figure out why there are still these three failures.
"""]]