{"action":"opened","issue":{"url":"https://api.github.com/repos/arturadib/shelljs/issues/197","labels_url":"https://api.github.com/repos/arturadib/shelljs/issues/197/labels{/name}","comments_url":"https://api.github.com/repos/arturadib/shelljs/issues/197/comments","events_url":"https://api.github.com/repos/arturadib/shelljs/issues/197/events","html_url":"https://github.com/arturadib/shelljs/issues/197","id":63964431,"number":197,"title":"Problems with exec (sync)","user":{"login":"dominykas","id":505619,"avatar_url":"https://avatars.githubusercontent.com/u/505619?v=3","gravatar_id":"","url":"https://api.github.com/users/dominykas","html_url":"https://github.com/dominykas","followers_url":"https://api.github.com/users/dominykas/followers","following_url":"https://api.github.com/users/dominykas/following{/other_user}","gists_url":"https://api.github.com/users/dominykas/gists{/gist_id}","starred_url":"https://api.github.com/users/dominykas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dominykas/subscriptions","organizations_url":"https://api.github.com/users/dominykas/orgs","repos_url":"https://api.github.com/users/dominykas/repos","events_url":"https://api.github.com/users/dominykas/events{/privacy}","received_events_url":"https://api.github.com/users/dominykas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-24T10:39:45Z","updated_at":"2015-03-24T10:39:45Z","closed_at":null,"body":"This bums me out completely and I'll have to investigate this later so just dumping my notes here.\r\n\r\nI'm having issues with `shelljs.exec` on node 0.12 / io.js, see: https://travis-ci.org/dominykas/grunt-checkbranch/jobs/55620589#L651 vs https://travis-ci.org/dominykas/grunt-checkbranch/jobs/55620587#L360\r\n\r\nThe relevant test case: https://github.com/dominykas/grunt-checkbranch/blob/master/test/checkbranch.test.js#L88\r\n\r\nThe tests here are complicated - I have to test if my grunt command works via `exec`, and the command itself also calls `exec` (to get git data) itself, so that might be a clue. Or maybe not.\r\n\r\nI also can't reproduce this on my local mac - the relevant test passes like so:\r\n```\r\nExpecting to  be on 'master' branch.\r\nHEAD\r\n>> fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.\r\n>> Use '--' to separate paths from revisions, like this:\r\n>> 'git <command> [<revision>...] -- [<file>...]'\r\nFatal error: Failed to detect the current branch\r\n```\r\n\r\ni.e. I can see the output although there shouldn't be any...\r\n\r\nA similar test in a similar module passes just fine: https://github.com/dominykas/grunt-checkpending/blob/master/test/checkpending.test.js#L69\r\n\r\nThere might be unrelated other config issues (e.g. buster hijacks console), but just putting this out there for now - maybe someone has a better clue, since the failure does result in `shell.js: internal error`"}}