You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Matthias Weßendorf (JIRA)" <ji...@apache.org> on 2011/04/18 13:42:05 UTC
[jira] [Created] (NPANDAY-407) Wrong Unit test (on Mac) for status
return from "command not found"
Wrong Unit test (on Mac) for status return from "command not found"
-------------------------------------------------------------------
Key: NPANDAY-407
URL: https://issues.apache.org/jira/browse/NPANDAY-407
Project: NPanday
Issue Type: Bug
Components: Development Setup
Affects Versions: 1.3.1-incubating
Reporter: Matthias Weßendorf
Attachments: NPANDAY-407.diff
Running the testTooLongCommandName() test on Mac fails.
The reson is that Mac (bash gnu) returns code 127 (command not found).
The "generated" command is this:
/bin/bash -c xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
and since the xxxxxxxxx.... is not available - the test fails.
Looks like on Windows this is return code 1 (I was expecting that on Ubuntu this fails as well - perhaps has not been tested?)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-407) Wrong Unit test (on Mac) for
status return from "command not found"
Posted by "Matthias Weßendorf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021031#comment-13021031 ]
Matthias Weßendorf commented on NPANDAY-407:
--------------------------------------------
On Mac the 'gnu bash' is used. And the value 127 is used for 'command not found':
"If a command is not found, the child process created to execute it returns a status of 127."
(see: http://www.gnu.org/software/bash/manual/bashref.html#Exit-Status)
> Wrong Unit test (on Mac) for status return from "command not found"
> -------------------------------------------------------------------
>
> Key: NPANDAY-407
> URL: https://issues.apache.org/jira/browse/NPANDAY-407
> Project: NPanday
> Issue Type: Bug
> Components: Development Setup
> Affects Versions: 1.3.1-incubating
> Reporter: Matthias Weßendorf
> Attachments: NPANDAY-407.diff
>
>
> Running the testTooLongCommandName() test on Mac fails.
> The reson is that Mac (bash gnu) returns code 127 (command not found).
> The "generated" command is this:
> /bin/bash -c xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> and since the xxxxxxxxx.... is not available - the test fails.
> Looks like on Windows this is return code 1 (I was expecting that on Ubuntu this fails as well - perhaps has not been tested?)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-407) Wrong Unit test (on Mac) for status
return from "command not found"
Posted by "Matthias Weßendorf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated NPANDAY-407:
---------------------------------------
Attachment: NPANDAY-407_NEW.diff
new version...
> Wrong Unit test (on Mac) for status return from "command not found"
> -------------------------------------------------------------------
>
> Key: NPANDAY-407
> URL: https://issues.apache.org/jira/browse/NPANDAY-407
> Project: NPanday
> Issue Type: Bug
> Components: Development Setup
> Affects Versions: 1.3.1-incubating
> Reporter: Matthias Weßendorf
> Attachments: NPANDAY-407.diff, NPANDAY-407_NEW.diff
>
>
> Running the testTooLongCommandName() test on Mac fails.
> The reson is that Mac (bash gnu) returns code 127 (command not found).
> The "generated" command is this:
> /bin/bash -c xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> and since the xxxxxxxxx.... is not available - the test fails.
> Looks like on Windows this is return code 1 (I was expecting that on Ubuntu this fails as well - perhaps has not been tested?)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-407) Wrong Unit test (on Mac) for status
return from "command not found"
Posted by "Matthias Weßendorf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated NPANDAY-407:
---------------------------------------
Attachment: NPANDAY-407.diff
a correction for the test...
> Wrong Unit test (on Mac) for status return from "command not found"
> -------------------------------------------------------------------
>
> Key: NPANDAY-407
> URL: https://issues.apache.org/jira/browse/NPANDAY-407
> Project: NPanday
> Issue Type: Bug
> Components: Development Setup
> Affects Versions: 1.3.1-incubating
> Reporter: Matthias Weßendorf
> Attachments: NPANDAY-407.diff
>
>
> Running the testTooLongCommandName() test on Mac fails.
> The reson is that Mac (bash gnu) returns code 127 (command not found).
> The "generated" command is this:
> /bin/bash -c xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> and since the xxxxxxxxx.... is not available - the test fails.
> Looks like on Windows this is return code 1 (I was expecting that on Ubuntu this fails as well - perhaps has not been tested?)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-407) Wrong Unit test (on Mac) for status
return from "command not found"
Posted by "Lars Corneliussen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen resolved NPANDAY-407.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1-incubating
patch applied in trunk
> Wrong Unit test (on Mac) for status return from "command not found"
> -------------------------------------------------------------------
>
> Key: NPANDAY-407
> URL: https://issues.apache.org/jira/browse/NPANDAY-407
> Project: NPanday
> Issue Type: Bug
> Components: Development Setup
> Affects Versions: 1.3.1-incubating
> Reporter: Matthias Weßendorf
> Fix For: 1.3.1-incubating
>
> Attachments: NPANDAY-407.diff, NPANDAY-407_NEW.diff
>
>
> Running the testTooLongCommandName() test on Mac fails.
> The reson is that Mac (bash gnu) returns code 127 (command not found).
> The "generated" command is this:
> /bin/bash -c xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> and since the xxxxxxxxx.... is not available - the test fails.
> Looks like on Windows this is return code 1 (I was expecting that on Ubuntu this fails as well - perhaps has not been tested?)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira