[
https://issues.apache.org/jira/browse/DISPATCH-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke resolved DISPATCH-1098.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Fixed at Commit 18c73a
> Fedora 28 python3-only test issues
> ----------------------------------
>
> Key: DISPATCH-1098
> URL: https://issues.apache.org/jira/browse/DISPATCH-1098
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.2.0
> Reporter: Chuck Rolke
> Priority: Major
> Fix For: 1.4.0
>
> Attachments: Dockerfile-DISPATCH-1098, build-1098.sh, run-1098.sh
>
>
> Building a Fedora 28, python-3-only (no python 2), proton and dispatch leads
> to some test issues.
> * `which python` is empty
> * `which unit2` is empty
> h4. Define python
> CMake finds python OK and builds proton and dispatch with the correct python
> version. But the tests don't work. _python_ appears to be a python 2
> construct. In a python 3 system the executable is installed as python3.
> Python can be defined with the alternatives command
> {{alternatives --install /usr/bin/python python /usr/bin/python3 1}}
> h4. Define unit2
> The self test runner in dispatch expects an executable named _unit2_. _Unit2_
> is a python 2 executable and in python 3 the equivalent program is named
> _unit2-3_. The dispatch build scheme should always use _unit2_ and thiis can
> be accomplished for python 3 with:
> {{alternatives --install /usr/bin/unit2 unit2 /usr/bin/unit2-3 1}}
> h4. Proposal
> Dispatch self test should use naked _python_ and _unit2_ commands. An check
> in the dispatch build could disable tests and warn about them being disabled
> similar to how a missing unittest2 is handled. See
> https://issues.apache.org/jira/browse/DISPATCH-919
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
