You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/04/08 09:23:00 UTC
[jira] [Commented] (QPID-8517) Run Travis CI separately under python2 and python3 evironments
[ https://issues.apache.org/jira/browse/QPID-8517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709860#comment-17709860 ]
ASF subversion and git services commented on QPID-8517:
-------------------------------------------------------
Commit da9e2200f0e6b0e7e04ed41a015051341b3502f8 in qpid-cpp's branch refs/heads/main from Jiri Daněk
[ https://gitbox.apache.org/repos/asf?p=qpid-cpp.git;h=da9e2200f ]
QPID-8610: add GitHub Actions workflow to build project and run ctest (#34)
Github Actions don't run on the PR, so I am monitoring it on my fork, https://github.com/jiridanek/qpid-cpp/actions/runs/4644235028
Using Focal (`runs-on: ubuntu-20.04`) for now, as it has the old requirements we need. Travis used to run Xenial, that worked even better, without workarounds for swig and ruby.
Python 2.7 is required ([QPID-8516](https://issues.apache.org/jira/browse/QPID-8516), [QPID-4982](https://issues.apache.org/jira/browse/QPID-4982), [QPID-8517](https://issues.apache.org/jira/browse/QPID-8517))
Linux environment requires swig3.0 and ruby2.6 to compile and work ([QPID-8606](https://issues.apache.org/jira/browse/QPID-8606), https://github.com/swig/swig/issues/1689)
The vcpkg version of Boost requires some changes to how dependencies are linked. What's in the PR now works on both Appveyor and Github Actions.
Caching is very important. Both installing boost with vcpkg on Windows and compiling the broker code takes a lot of time without cache. With cache, vcpkg is nearly instantaneous and broker compile takes only a few minutes on Linux, and few more on Windows. When using sccache, make or ninja CMake generators have to be used. MSBuild is not supported for `-DCMAKE_C_COMPILER_LAUNCHER` CMake option. This can be workarounded in the future by the usual trick of renaming `sccache.exe` to `cl.exe`.
Tests run very long. I am afraid to run them in parallel as part of this PR. I want to leave that for later. But it is going to be necessary, because the CI just takes way too much time otherwise.
Broker tests don't run on Windows and AFAIK they did not run there for a very long time.
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org