Conversation
Signed-off-by: Yuri Shkuro <ys@uber.com>
as I suspected, some of the (tchannel-related) tests are failing
|
I wish I could help, but getting this module to build/test on Windows seems to be its very own challenge. :( |
@yurishkuro Why did you close this? |
I don't have time to investigate / finish it (not sure it's even possible without serious refactoring). |
I don't really understand how that failure would be caused by the xorshift upgrade. I can now build and test the project locally with an upgraded xorshift just fine. Can you explain to me how to reproduce the failure you saw? The CI failure seemed to only be in a single run and I can't really make sense of it. What's the actual failure here? What is the lowest NodeJS Version that must be supported? |
So to my understanding, those are the crossdock tests that fail, which can be run with |
Feel free to make another PR if you think you can make it work. The CI failure was here: https://travis-ci.org/github/jaegertracing/jaeger-client-node/builds/655565023 Uber still uses Node 0.10 for some critical services, that's why we keep compatibility. I agree it's annoying. |
I created a PR at #442 |
* feat(plugin-dns): add lookup patches ref: jaegertracing#423 add docs add example include promise patch for lookup Signed-off-by: Olivier Albertini <olivier.albertini@montreal.ca> * fix: add mayurkale22 recommendations
Resolves #422