[ 
https://issues.apache.org/jira/browse/PROTON-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155683#comment-17155683
 ] 

ASF GitHub Bot commented on PROTON-2219:
----------------------------------------

jiridanek commented on pull request #246:
URL: https://github.com/apache/qpid-proton/pull/246#issuecomment-656846444


   If I can figure out what's causing python-tox-test to fail and fix that, I'd 
prefer to commit this, using clang 9 to work around the other issue. This PR 
used to run fine in CI when I submitted it (except for the clang 10 thing), and 
only broke in the meantime.
   
   Leaving unfinished PRs languish seems to be only a recipe for misery down 
the line, trying to put them back into shape.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> Upgrade .travis.yml to test on a good cross-section of available Ubuntu 
> versions
> --------------------------------------------------------------------------------
>
>                 Key: PROTON-2219
>                 URL: https://issues.apache.org/jira/browse/PROTON-2219
>             Project: Qpid Proton
>          Issue Type: Test
>          Components: build
>    Affects Versions: proton-c-0.31.0
>            Reporter: Jiri Daněk
>            Assignee: Jiri Daněk
>            Priority: Major
>
> With Ubuntu 20.04 Focal available in Travis, it is possible to spread the 
> jobs over both current and older Ubuntu releases, and current and newer 
> compilers.
> The sanitizer jobs should profit from recent gcc and clang, and the 
> benchmarks job printout will be better with newer libbenchmark, all of those 
> are available in Focal.



--
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