[
https://issues.apache.org/jira/browse/THRIFT-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361920#comment-14361920
]
Jens Geyer commented on THRIFT-3039:
------------------------------------
Probably not, I installed a lot of stuff into that VM to get everything running
(more or less) smoothly. I probably had to repeat those steps to create a
matching docker container. Or is there some way to convert an existing
VirtualBox VM into a Docker container?
Also my guess is that simply the timing is bad in the test scripts, I had
similar problems with (IIRC) Ruby, there is still an open ticket for this. I
haven't tried yet, but maybe simply increasing the timeouts will make it work.
At least that's what I did with those Ruby tests to get it working here. In
general, I'm not such a big fan of such constructions, because they are prone
to race conditions by definition. OTOH I understand that there have to be some
limits to make sure the test does not get stuck completely.
> one of the tests fails repeatedly, probably timing problem
> ----------------------------------------------------------
>
> Key: THRIFT-3039
> URL: https://issues.apache.org/jira/browse/THRIFT-3039
> Project: Thrift
> Issue Type: Bug
> Components: Node.js - Library
> Environment: openSUSE running in VM with rather limited hardware (may
> be an important factor here)
> Reporter: Jens Geyer
>
> {{make check}} fails repeatedly at one of the nodejs tests, with this message:
> {code}
> Testing http Client/Server with protocol json and transport framed --ssl
> TAP version 13
> # NodeJS Style Callback Client Tests
> ok 1 testString: no callback error
> ok 2 testString
> ok 3 testString: no callback error
> ok 4 testString
> ok 5 testString: no callback error
> ok 6 testString
> ok 7 testString: no callback error
> ok 8 testString
> ok 9 testByte: no callback error
> ok 10 testByte
> ok 11 testByte: no callback error
> ok 12 testByte
> ok 13 testByte: no callback error
> ok 14 testByte
> ok 15 testByte: no callback error
> ok 16 testByte
> ok 17 testI32: no callback error
> ok 18 testI32
> ok 19 testDouble: no callback error
> ok 20 testDouble
> ok 21 testDouble: no callback error
> ok 22 testDouble
> ok 23 testEnum: no callback error
> ok 24 testEnum
> ok 25 testI64: no callback error
> ok 26 testI64
> ok 27 testI64: no callback error
> ok 28 testI64
> ok 29 testI64: no callback error
> ok 30 testI64
> ok 31 testI64: no callback error
> ok 32 testI64
> ok 33 testI64: no callback error
> ok 34 testI64
> ok 35 testTypedef: no callback error
> ok 36 testTypedef
> ok 37 testMap: no callback error
> ok 38 testMap
> ok 39 testSet: no callback error
> ok 40 testSet
> ok 41 testList: no callback error
> ok 42 testList
> ok 43 testStringMap: no callback error
> ok 44 testStringMap
> ok 45 testMapMap: no callback error
> ok 46 testMapMap
> Server test failed to complete after 3 seconds
> not ok 47 test exited without ending
> ---
> operator: fail
> ...
> {code}
> followed by
> {code}
> npm ERR! Test failed. See above for more details.
> npm ERR! not ok code 0
> Makefile:581: recipe for target 'check' failed
> make[2]: *** [check] Error 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
