[jira] [Created] (PROTON-592) Python test function common _ready() fails on windows
Chuck Rolke created PROTON-592: -- Summary: Python test function common _ready() fails on windows Key: PROTON-592 URL: https://issues.apache.org/jira/browse/PROTON-592 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Environment: Windows ctest Reporter: Chuck Rolke Test code asserts READY\n that never works on windows. Fix by using READY + os.linesep -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-592) Python test function common _ready() fails on windows
[ https://issues.apache.org/jira/browse/PROTON-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018835#comment-14018835 ] ASF subversion and git services commented on PROTON-592: Commit 1600676 from c...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1600676 ] PROTON-592: Use os.linesep in assert test so test passes on Windows. Python test function common _ready() fails on windows - Key: PROTON-592 URL: https://issues.apache.org/jira/browse/PROTON-592 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Environment: Windows ctest Reporter: Chuck Rolke Test code asserts READY\n that never works on windows. Fix by using READY + os.linesep -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (PROTON-593) Scripts for running java examples contain old paths
Marcel Meulemans created PROTON-593: --- Summary: Scripts for running java examples contain old paths Key: PROTON-593 URL: https://issues.apache.org/jira/browse/PROTON-593 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.7 Reporter: Marcel Meulemans Priority: Trivial -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (PROTON-593) Scripts for running java examples contain old paths
[ https://issues.apache.org/jira/browse/PROTON-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Meulemans updated PROTON-593: Description: See attached patch. Trivial, I know, but avoids minor hassle :) Scripts for running java examples contain old paths --- Key: PROTON-593 URL: https://issues.apache.org/jira/browse/PROTON-593 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.7 Reporter: Marcel Meulemans Priority: Trivial Attachments: patch1.patch See attached patch. Trivial, I know, but avoids minor hassle :) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (PROTON-593) Scripts for running java examples contain old paths
[ https://issues.apache.org/jira/browse/PROTON-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Meulemans updated PROTON-593: Attachment: patch1.patch Scripts for running java examples contain old paths --- Key: PROTON-593 URL: https://issues.apache.org/jira/browse/PROTON-593 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.7 Reporter: Marcel Meulemans Priority: Trivial Attachments: patch1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (PROTON-594) In tree builds with cmake causes issues when running python based tests
Rajith Attapattu created PROTON-594: --- Summary: In tree builds with cmake causes issues when running python based tests Key: PROTON-594 URL: https://issues.apache.org/jira/browse/PROTON-594 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Rajith Attapattu Assignee: Rafael H. Schloming Fix For: 0.8 If we do an in-tree build it causes path issues when trying to run the python based tests against the java code. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-594) In tree builds with cmake causes issues when running python based tests
[ https://issues.apache.org/jira/browse/PROTON-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018873#comment-14018873 ] Rajith Attapattu commented on PROTON-594: - Rafi could you please create a new component for the cmake build system. I just temporarily assigned this JIRA to proton-c to create the JIRA as it doesn't allow to leave it blank. In tree builds with cmake causes issues when running python based tests --- Key: PROTON-594 URL: https://issues.apache.org/jira/browse/PROTON-594 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Rajith Attapattu Assignee: Rafael H. Schloming Fix For: 0.8 If we do an in-tree build it causes path issues when trying to run the python based tests against the java code. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (PROTON-595) Python test function MessengerApp.start fails on Windows
Chuck Rolke created PROTON-595:
--
Summary: Python test function MessengerApp.start fails on Windows
Key: PROTON-595
URL: https://issues.apache.org/jira/browse/PROTON-595
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.7
Environment: Windows ctest
Reporter: Chuck Rolke
The function uses Popen() where the first cmd arg is the name of a python file.
Windows doesn't honor the #! at the beginning of the file and then fails with
{noformat}
[Error 193] %1 is not a valid Win32 application
{noformat}
This code could also be improved by printing the exception error text along
with the path setting hint.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (PROTON-596) There is no equivalent to 'config.sh' for windows
Chuck Rolke created PROTON-596: -- Summary: There is no equivalent to 'config.sh' for windows Key: PROTON-596 URL: https://issues.apache.org/jira/browse/PROTON-596 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Environment: Proton on windows Reporter: Chuck Rolke ctest fails to find compiled C tests. Some environment settings are needed in addition to those supplied by cmake/ctest. Linux users have the luxury of config.sh to steer their environment correctly for tests built in proton/build. Windows users need the same. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-596) There is no equivalent to 'config.sh' for windows
[ https://issues.apache.org/jira/browse/PROTON-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019103#comment-14019103 ] ASF subversion and git services commented on PROTON-596: Commit 1600727 from c...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1600727 ] PROTON-596: Add config.bat environment settings for windows. * Bug-for-bug compatible with config.sh ** adds new paths after old paths ** uses fixed \build folder for builds * For use with debug builds only (pending conversion to cmake configure .in file) To use: cd proton call config.bat cd build ctest There is no equivalent to 'config.sh' for windows - Key: PROTON-596 URL: https://issues.apache.org/jira/browse/PROTON-596 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Environment: Proton on windows Reporter: Chuck Rolke ctest fails to find compiled C tests. Some environment settings are needed in addition to those supplied by cmake/ctest. Linux users have the luxury of config.sh to steer their environment correctly for tests built in proton/build. Windows users need the same. -- This message was sent by Atlassian JIRA (v6.2#6252)
