Hi,
Yes I could run them manually, but don't work when ran in test.sh.
On Fri, May 23, 2014 at 12:19 AM, Henrique Mendonça wrote:
> Hi
> Sorry I don't have time test it now but it's perhaps because it runs
> asynchronously?
> Can you run them manually or with the testAll.sh I mentioned before?
>
Hi
Sorry I don't have time test it now but it's perhaps because it runs
asynchronously?
Can you run them manually or with the testAll.sh I mentioned before?
On 22 May 2014 14:54, Chamila Wijayarathna wrote:
> Hi Henrique,
> By using alias, I could successfully ran nodejs clients and servers alo
Hi Henrique,
By using alias, I could successfully ran nodejs clients and servers alone,
but still when I ran test.sh, it gives empty log files for nodejs clients
and servers, any idea on how to run them using test.sh?
Thank You!
On Thu, May 22, 2014 at 9:27 PM, Henrique Mendonça wrote:
> Hi Cham
Hi Henrique,
I successfully executed it in that way.
Thank You!
On Thu, May 22, 2014 at 9:27 PM, Henrique Mendonça wrote:
> Hi Chamila,
>
> I've changed it on this commit because it was already using "node" in
> "make check", i.e.
> https://github.com/apache/thrift/blob/master/lib/nodejs/test/te
Hi Chamila,
I've changed it on this commit because it was already using "node" in "make
check", i.e.
https://github.com/apache/thrift/blob/master/lib/nodejs/test/testAll.sh
Depending on the OS version you use, you might have node or nodejs but you
can use a alias:
alias node="nodejs"
Best,
Henr
Hi,
When running node test server using "node ../lib/nodejs/test/server.js -p
binary -t buffered", it exists without listening. I observed that this
command has been changed from "nodejs" to "node" at [1]. I could run some
of these tests successfully before doing these changes. What is the reason
f
