-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unexplained "Process exited with code 1" #5
Comments
I have exactly the same problem. |
Not directly but I think 9.1 is better |
We also have been experiencing problems with the The TeamCity build always dies - at the same point, but without a helpful error message- just Unfortunately, the various problems with the TeamCity SBT runner mean that we'll have to stop using it, resort to a bash script instead. |
@rtyley I had the same problem and was able to work around it. Maybe this will help you. For some background, my TeamCity is configured with SBT Commands:
ui/test := {
val logger = streams.value.log("ui")
sys.process.Process("npm run test") ! logger match {
case 0 => // success
case x => sys.error(s"Process failed with exit code $x")
}
} When the external process fails, it prints useful information to stderr and exits with a non-zero exit code. But the TeamCity SBT runner terminates with an unexplained "Process exited with code 1", without logging any stderr. My workaround was to redirect all stderr to stdout using |
Wow, thanks @dwickern - that's really interesting! |
Please help! My sbt build step keeps failing in TeamCity 9. Here's the log:
The text was updated successfully, but these errors were encountered: