[GRADLE-2782] Native platform integration throws exception on OpenSuse. Created: 28/May/13 Updated: 30/Dec/16 Resolved: 30/Dec/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Gradle Forums | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 4 |
| Description |
FAILURE: Build aborted because of an internal error. * What went wrong: Build aborted because of an unexpected internal error. Please file an issue at: [1]http://forums.gradle.org. * Try: Run with --debug option to get additional debug info. * Exception is: net.rubygrapefruit.platform.NativeException: Could not open terminal for stdout: could not get termcap entry at net.rubygrapefruit.platform.internal.TerminfoTerminal.init(TerminfoTerminal.java:49) at net.rubygrapefruit.platform.internal.WrapperTerminal.init(WrapperTerminal.java:41) at net.rubygrapefruit.platform.internal.AbstractTerminals.getTerminal(AbstractTerminals.java:35) at org.gradle.internal.nativeplatform.console.NativePlatformConsoleDetector.getConsole(NativePlatformConsoleDetector.java:42) at org.gradle.logging.internal.ConsoleConfigureAction.execute(ConsoleConfigureAction.java:32) at org.gradle.logging.internal.ConsoleConfigureAction.execute(ConsoleConfigureAction.java:27) at org.gradle.logging.internal.OutputEventRenderer.attachConsole(OutputEventRenderer.java:68) at org.gradle.logging.internal.DefaultLoggingManager.attachConsole(DefaultLoggingManager.java:149) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:168) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:139) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.Main.doAction(Main.java:48) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at org.gradle.launcher.Main.main(Main.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:50) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:32) at org.gradle.launcher.GradleMain.main(GradleMain.java:26) |
| Comments |
| Comment by kevin cline [ 24/Mar/14 ] |
|
This also occurs running gradle on CentOS 5 in an Emacs shell window. I was able to work around it with "export TERM=dumb" This is annoying. Gradle should have some fallback behavior if the terminal type is not found in termcap. |
| Comment by Andrew Ash [ 01/Jun/16 ] |
|
I'm seeing this issue in my CircleCI builds and have to export TERM=dumb to work around this build failure: ubuntu@box44:~$ ./gradlew check FAILURE: Build failed with an exception. * What went wrong: Could not open terminal for stdout: could not get termcap entry Is there any progress being made on this issue in the past couple years? |
| Comment by John R Scancella [ 05/Jul/16 ] |
|
I am trying to run gradle in Concourse CI and getting the same error. |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Biel Simon [ 28/Dec/16 ] |
|
This is sill an issue on gradle 2.13. I'm trying to execute gradle inside Concourse CI. Please fix it as soon as possible. |
| Comment by Biel Simon [ 28/Dec/16 ] |
|
Okay, this i no longer an issue in gradle 3.2.1. I am not aware of when this was exactly fixed but it's fine now. |
| Comment by Benjamin Muschko [ 30/Dec/16 ] |
|
Closing as it seems to be fixed with latest Gradle version (3.2.1). Unfortunately, I do not know which version fixes the issue. |