[
https://issues.apache.org/jira/browse/QPID-8517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318880#comment-17318880
]
Chris Richardson edited comment on QPID-8517 at 4/11/21, 4:56 PM:
------------------------------------------------------------------
Sincere apologies for the enormous amount of spam to the dev channel from this
issue today! It's a bit hard to test Travis without using the real thing
though. The good news is that it's not entirely in vain - I believe I've got
the CI build to do something sensible by only the 48th build of my feature
branch!
[https://www.travis-ci.com/github/apache/qpid-cpp/builds/222743206]
That build shows 2 parallel tasks, one building on Ubuntu bionic with a mixed
python2/3 environment and the other building on Focal (which is pure python3)
and failing due to this bug with a PR in flight: QPID-8516.
Note that I've added a line to .travis.yaml to print the available python
versions installed by the pyenv package in addition to the system ones, which
for focal still shows only python3 versions.
[~jdanek] I'm all for a docker solution if you think it's viable, otherwise I
think this setup will do the trick.
Caveat: since the build fails early due to QPID-8516 I'm not sure whether the
tests will fail, since they might need qpid-python (which is a python2
package?). I'll cherry-pick that fix into this branch, then we'll know where we
stand.
was (Author: crichardson):
Sincere apologies for the enormous amount of spam to the dev channel from this
issue today! It's a bit hard to test Travis without using the real thing
though. The good news is that it's not entirely in vain - I believe I've got
the CI build to do something sensible by only the 48th build of my feature
branch!
[https://www.travis-ci.com/github/apache/qpid-cpp/builds/222743206]
That build shows 2 parallel tasks, one building on Ubuntu bionic with a mixed
python2/3 environment and the other building on Focal (which is pure python3)
and failing due to this bug with a PR in flight: QPID-8516.
Note that I've added a line to .travis.yaml to print the available python
versions installed by the pyenv package in addition to the system ones, which
for focal still shows only python3 versions.
[~jdanek] I'm all for a docker solution if you think it's viable, otherwise I
think this setup will do the trick.
Caveat: since the build fails early due to QPID-8516 I'm not sure whether the
tests will fail, since they might need qpid-python (which is a python2
package?). I'll merge the PR for that fix and rebase this branch, then we'll
know where we stand.
> Run Travis CI separately under python2 and python3 evironments
> --------------------------------------------------------------
>
> Key: QPID-8517
> URL: https://issues.apache.org/jira/browse/QPID-8517
> Project: Qpid
> Issue Type: Improvement
> Affects Versions: qpid-cpp-1.39.0
> Environment: Travis/Xenial
> Reporter: Chris Richardson
> Priority: Major
> Fix For: qpid-cpp-1.40.0
>
>
> While mixed python versions are supported in the build system, it would be
> good to verify that the codebase can be built and unit tests run under both
> python2 and python3 environments.
> Travis can (?) be configured to do this in parallel by running the tests
> having installed the "python-dev" apt package (python2) or "python3-dev"
> package for python3 (Xenial).
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
