[GRADLE-1400] Missing environment variables under windows cause tests to fail with unexpected exception Created: 25/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9-rc-2, 0.9.2
Fix Version/s: None

Type: Bug
Reporter: Spencer Allain Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Anything similar to the below line will cause testing to fail at runtime (assuming JUnit or TestNG was selected and there are unit tests to actually run – so the task doesn't get skipped)

test { environment = ['FOO':'foo'] }

Since this completely removes any default environment variables, it produces the below error message with no indication as to why something went wrong.

org.gradle.util.UncheckedException: java.lang.Error: Failed to create temporary
file for jnidispatch library: java.io.IOException: Access is denied
at org.gradle.util.UncheckedException.asUncheckedException(UncheckedExce

In this case, it's because %TEMP% is missing and jansi depends upon JNA, which fails to function properly.

Specifying %TEMP% gets things farther, but it still fails without an indication that it is because fundamental environment variables are missing.

Ideally gradle would check to ensure that any necessary environment variables are set before continuing, and print out error messages indicating what actually is missing.

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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:54:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.