[ 
https://issues.apache.org/jira/browse/DISPATCH-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jiri Daněk resolved DISPATCH-1712.
----------------------------------
    Resolution: Implemented

I'm not doing the Aarch64 job just yet. When I tried it, it kept getting stuck 
on Travis, which would be hard to debug. It might be suspected that the 
dispatch code is relying on some x86_64 behaviors for threading, and it 
deadlocks on less constrained architecture... but the Travis failures cannot be 
debugged well enough to figure out the true nature and the cause.

It would be also difficult to keep the job green in the future, since Aarch64 
is not the focus the project, and I am already struggling with the macOS job.

> Extend the Travis CI with Ubuntu Focal, and Clang
> -------------------------------------------------
>
>                 Key: DISPATCH-1712
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1712
>             Project: Qpid Dispatch
>          Issue Type: Test
>          Components: Tests
>    Affects Versions: 1.12.0
>            Reporter: Jiri Daněk
>            Assignee: Jiri Daněk
>            Priority: Major
>             Fix For: 1.13.0
>
>
> Dispatch is currently running all its CI jobs on Travis CI using Ubuntu 
> Xenial, AMD64, and GCC. It would make sense to me to extend the coverage.
> Ubuntu Focal contains newer versions of software. The CI may find 
> incompatibilities there.
> Aarch64 is weakly-ordered, so it may reveal some concurrency bugs. Travis has 
> it available https://docs.travis-ci.com/user/multi-cpu-architectures/
> Clang may print different diagnostics than gcc, and on aarch64 it supports 
> alternate algorithm for asan, which reports on overlapping but different set 
> of invalid memory accesses than regular asan 
> https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to