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

Roddie Kieley resolved PROTON-2174.
-----------------------------------
    Fix Version/s: proton-c-0.31.0
       Resolution: Fixed

As per the noted commits I added 1000ms to the TestHeartbeat test as it 
appeared that the previously given timeout of 400ms was too short for the 
travis vm to execute successfully. Also needed to implement a "workaround" by 
doing a brew update due to a brew bundle issue caused by a recent change on the 
brew distribution side - see .travis.yml for the update and the link.

> [go] go-test TestHeartbeat fails with latest macOS image
> --------------------------------------------------------
>
>                 Key: PROTON-2174
>                 URL: https://issues.apache.org/jira/browse/PROTON-2174
>             Project: Qpid Proton
>          Issue Type: Test
>          Components: go-binding
>            Reporter: Roddie Kieley
>            Assignee: Roddie Kieley
>            Priority: Major
>             Fix For: proton-c-0.31.0
>
>
> After a recent update to pick up the latest macOS image, now using Xcode 
> 11.3, we see a new failure during this [travis-ci 
> run|https://travis-ci.org/apache/qpid-proton/jobs/641271619]. 
> {quote}
> 26: === RUN   TestHeartbeat
> 26: --- FAIL: TestHeartbeat (0.45s)
> 26:     electron_test.go:325: connection failed to time out
> {quote}
> This looks virtually the same as failures seen prior to the move to go 
> modules as discussed in this PROTON-2105 
> [comment|https://issues.apache.org/jira/browse/PROTON-2105?focusedCommentId=16962578&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16962578]
> Testing locally on macOS 10.14 with Xcode 10.2 shows no TestHeartbeat 
> failures over 100 continuous attempts. Further investigation required.



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