-
Notifications
You must be signed in to change notification settings - Fork 43
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
echo command fails on Windows (testProjectExec unit tests) #422
Comments
@gocursor - it would be a great help to have your insights on this. I don't have a Windows machine, so this is much harder for me to fix. Can you figure out what command can be used to do something like cc @advayDev1 Probably the easiest test to work with is
|
i guess http://stackoverflow.com/questions/515309/what-does-cmd-c-mean |
That did the trick. I'm close to getting those tests to pass now. On Tue, Aug 25, 2015 at 11:07 PM Advay Mengle [email protected]
|
Major: - Fix j2objc-contrib#402 - Windows 37 unit tests failures - Fix j2objc-contrib#422 - echo command fails on Windows - Disabled only failing test on Windows: j2objc-contrib#374 Minor: - Fake OS specific file and path separators - Explicit setFakeOS methods, e.g. setFakeOSWindows() - Default to using native OS rather than fake OS for most unit tests - Small number of unit tests use fakeOSName - ‘inTestMustFakeOS’ setting removed
Major: - Fix j2objc-contrib#402 - Windows 37 unit tests failures - Fix j2objc-contrib#422 - echo command fails on Windows - Disabled only failing test on Windows: j2objc-contrib#374 Minor: - Fake OS specific file and path separators - Explicit setFakeOS methods, e.g. setFakeOSWindows() - Default to using native OS rather than fake OS for most unit tests - Small number of unit tests use fakeOSName - ‘inTestMustFakeOS’ setting removed
Major: - Fix j2objc-contrib#402 - Windows 37 unit tests failures - Fix j2objc-contrib#422 - echo command fails on Windows - Disabled only failing test on Windows: j2objc-contrib#374 Minor: - Fake OS specific file and path separators - Explicit setFakeOS methods, e.g. setFakeOSWindows() - Default to using native OS rather than fake OS for most unit tests - Small number of unit tests use fakeOSName - ‘inTestMustFakeOS’ setting removed
Major: - Fix j2objc-contrib#402 - Windows 37 unit tests failures - Fix j2objc-contrib#422 - echo command fails on Windows - Disabled only failing test on Windows: j2objc-contrib#374 Minor: - Fake OS specific file and path separators - Explicit setFakeOS methods, e.g. setFakeOSWindows() - Default to using native OS rather than fake OS for most unit tests - Small number of unit tests use fakeOSName - ‘inTestMustFakeOS’ setting removed
The
echo
command is used in a number of unit tests, particularly the testProjectExec unit tests in UtilsTest.groovy. This command isn't supported on Windows. The tests are currently disabled on Windows but should be enabled once an alternative is established to theecho
command. Current exception:org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'echo''
The text was updated successfully, but these errors were encountered: