diff options
author | ilovezfs <ilovezfs@web> | 2017-07-30 16:05:10 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2017-07-30 16:05:10 +0000 |
commit | c6858789e33f785edb1c7a7929b534e445849e07 (patch) | |
tree | 674e5d7f46ae0fb6623e86f184e1cade703e3aa8 | |
parent | ace60f5a6e206338e7a42efb9c0aecfd310a9c48 (diff) |
Added a comment: pipe: resource exhausted (Too many open files)
-rw-r--r-- | doc/bugs/Cannot_build_with_GHC_8.2.1/comment_2_0796d1dfcf7116c38451febb9701c857._comment | 67 |
1 files changed, 67 insertions, 0 deletions
diff --git a/doc/bugs/Cannot_build_with_GHC_8.2.1/comment_2_0796d1dfcf7116c38451febb9701c857._comment b/doc/bugs/Cannot_build_with_GHC_8.2.1/comment_2_0796d1dfcf7116c38451febb9701c857._comment new file mode 100644 index 000000000..cf83cd991 --- /dev/null +++ b/doc/bugs/Cannot_build_with_GHC_8.2.1/comment_2_0796d1dfcf7116c38451febb9701c857._comment @@ -0,0 +1,67 @@ +[[!comment format=mdwn + username="ilovezfs" + avatar="http://cdn.libravatar.org/avatar/f2b3954cf2ed0a551de9a49d3b6a64d0" + subject="pipe: resource exhausted (Too many open files)" + date="2017-07-30T16:05:10Z" + content=""" +Hi Joey, + +Yes, I can work around that particular failure by tweaking constraints. + +In particular, +--allow-newer=\"sandi:base\" --allow-newer=\"aws:time\" + +I also first need to \"cabal install Cabal<1.25\" because git-annex seems +to have a compatibility problem with Cabal-2.0.0.2. The error with +Cabal-2.0.0.2 is + +[[!format sh \"\"\" +Building executable 'git-annex' for git-annex-6.20170520.. + +Build/BuildVersion.hs:1:1: error: + File name does not match module name: + Saw: ‘Main’ + Expected: ‘Build.BuildVersion’ + | +1 | {- Outputs the version of git-annex that was built, for use by + | ^ +cabal: Leaving directory '.' +cabal: Error: some packages failed to install: +git-annex-6.20170520-3mbb3kAWTlXI0EMervIo66 failed during the building phase. +The exception was: +ExitFailure 1 +\"\"\"]] + +But, once I've installed the lower version of Cabal, and tweaked the +constraints for sandi and for aws, git-annex does build successfully. + +However, at that point a more serious issue comes up when I run \"git +annex test\" and here is the full log: +https://gist.github.com/ilovezfs/d430f589d87d7f7237591cd51b2b94cb + +Here is a snippet: +[[!format sh \"\"\" +From ../../.t/tmprepo53 + * [new branch] git-annex -> r2/git-annex + * [new branch] master -> r2/master + * [new branch] synced/master -> r2/synced/master +conflictor/subfile +conflictor.variant-cc12 +conflictor/subfile +conflictor.variant-cc12 +OK (3.27s) + conflict resolution symlink bit: OK + conflict resolution (uncommitted local file): FAIL (0.49s) + sync failed in r1 + conflict resolution (removed file): FAIL + Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files) + conflict resolution (nonannexed file): FAIL + Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files) + conflict resolution (nonannexed symlink): FAIL (0.03s) + git annex init failed + conflict resolution (mixed locked and unlocked file): FAIL + Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files) + map: FAIL + Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files) +\"\"\"]] +"""]] |