[
https://issues.apache.org/jira/browse/PROTON-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247693#comment-16247693
]
Andrew Stitcher commented on PROTON-1636:
-----------------------------------------
I'm now seeing regular failures in ruby-test-container:
{noformat}
16: 1) Failure:
16: ContainerTest#test_auto_stop
[/home/travis/build/astitcher/qpid-proton/proton-c/bindings/ruby/tests/test_container.rb:95]:
16: Expected nil to be truthy.
16:
{noformat}
> Fairly Consistent (but intermittent) hangs in ruby-example-test using Travis
> CI
> -------------------------------------------------------------------------------
>
> Key: PROTON-1636
> URL: https://issues.apache.org/jira/browse/PROTON-1636
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
> Affects Versions: proton-c-0.18.0
> Environment: Travis CI:
> Ubuntu 1404 with lots of changes
> Reporter: Andrew Stitcher
> Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> This is pretty annoying as it makes the build fail about 50% of the time for
> me and so it looks like the change just made failed the build.
> {noformat}
> Start 14: ruby-example-test
> 14: Test command: /home/travis/.rvm/rubies/ruby-2.4.1/bin/ruby
> "example_test.rb" "-v"
> 14: Test timeout computed to be: 1500
> 14: Run options: -v --seed 7224
> 14:
> 14: # Running:
> 14:
> 14: ExampleTest#test_client_server = 0.30 s = .
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on:
> https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
> The build has been terminated
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
