Object success has no method 'push'

[MK]

I downloaded http://s3.amazonaws.com/four.livejournal/20091117/node-v0.1.18.tar.gz.

./configure
make
make test

The tests fail... see below... I don't want to do a make install until
the tests pass... any ideas?

TypeError: Object success has no method 'push'
at EIOPromise.addListener (node.js:199:23)
at EIOPromise.addErrback (node.js:279:7)
at readChunk (node.js:118:9)
at EIOPromise.<anonymous> (node.js:122:4)
Command: build/default/node /home/kipsuper/dev/node/test/mjsunit/test-
file-cat-noexist.js
=== release test-http-malformed-request ===
Path: mjsunit/test-http-malformed-request
node.js:199
this._events[type].push(listener);
^
TypeError: Object success has no method 'push'
at EIOPromise.addListener (node.js:199:23)
at EIOPromise.addErrback (node.js:279:7)
at readChunk (node.js:118:9)
at EIOPromise.<anonymous> (node.js:122:4)
Command: build/default/node /home/kipsuper/dev/node/test/mjsunit/test-
http-malformed-request.js
[00:01|% 100|+ 0|- 45]: Done
make: *** [test] Error 1

[Kip Lawrence]

FYI. I also clone the latest git repository and get the same problem when doing a make test.

The errors also happen when I try the example from the website.

% node example.js

-Kip

[Iván -DrSlump- Montes]

I'm also having this issue with the last release and also with the
master branch. The server is VPS (Dreamhost) 64bit Debian Etch. Any
idea about what can be the problem?

All the tests fail with the same exception:

TypeError: Object success has no method 'push'

at [object Object].addListener (node.js:173:26)
at [object Object].addErrback (node.js:277:17)
at readChunk (node.js:658:12)
at [object Object].<anonymous> (node.js:662:7)
at [object Object].emitSuccess (node.js:241:15)
at node.js:511:29
at node.js:995:9

Here is the output from configure:

Checking for program g++,c++             : ok /usr/bin/g++
Checking for program cpp                 : ok /usr/bin/cpp
Checking for program ar                  : ok /usr/bin/ar
Checking for program ranlib              : ok /usr/bin/ranlib
Checking for g++                         : ok
Checking for program gcc,cc              : ok /usr/bin/gcc
Checking for gcc                         : ok
Checking for library dl                  : ok
Checking for library execinfo            : not found
Checking for gnutls >= 2.5.0             : fail
--- libeio ---
Checking for library pthread             : ok
Checking for function pthread_create     : ok
Checking for function pthread_atfork     : ok
Checking for futimes(2)                  : ok
Checking for readahead(2)                : ok
Checking for fdatasync(2)                : ok
Checking for pread(2) and pwrite(2)      : fail
Checking for sendfile(2)                 : ok
Checking for sync_file_range(2)          : fail
--- libev ---
Checking for header sys/inotify.h        : not found
Checking for header sys/epoll.h          : ok
Checking for function epoll_ctl          : ok
Checking for header port.h               : not found
Checking for header poll.h               : ok
Checking for function poll               : ok
Checking for header sys/event.h          : not found
Checking for header sys/queue.h          : ok
Checking for function kqueue             : not found
Checking for header sys/select.h         : ok
Checking for function select             : ok
Checking for header sys/eventfd.h        : not found
Checking for SYS_clock_gettime           : ok
Checking for library rt                  : ok
Checking for function clock_gettime      : ok
Checking for function nanosleep          : ok
Checking for function ceil               : ok
---- deps/udns ----
configure... udns package
checking for C compiler... gcc
checking whenever C compiler (gcc) is GNU CC... yes
checking whenever the C compiler (gcc -Wall -W -O2 -pipe)
           can produce executables... yes
checking for ranlib... ranlib
checking for getopt()... yes
checking for inet_pton() && inet_ntop()... yes
checking for socklen_t... yes
checking for libraries needed for socket and connect... ok (none needed)
checking for IPv6... yes
checking for poll()... yes
creating config.h... unchanged
creating Makefile... ok
creating config.status... ok
all done.
'configure' finished successfully (3.089s)

regards,
/imv

[Micheil Smith]

Can you give the full test output, based on latest HEAD?

Thanks,
Micheil.

> --
> You received this message because you are subscribed to the Google Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
>

[Iván -DrSlump- Montes]

Sure, find it attached.

thanks,
/imv

[Ryan Dahl]

On Fri, Nov 20, 2009 at 12:08 PM, MK <kip.la...@gmail.com> wrote:
> I downloaded http://s3.amazonaws.com/four.livejournal/20091117/node-v0.1.18.tar.gz.
>
> ./configure
> make
> make test
>
> The tests fail... see below... I don't want to do a make install until
> the tests pass... any ideas?

Strange. I don't know why this is failing. Can you try to debug it?

Does the attached patch help?

[Iván -DrSlump- Montes]

Hi,

Unfortunately the patch didn't work. I'll try to get some help to
debug it later on.

thanks,
/imv

[Iván -DrSlump- Montes]

I'm a total newbie with gdb, so don't be too harsh with me :)

First I tried with the normal build but gdb couldn't generate a backtrace:

$ gdb --args node test/mjsunit/test-next-tick.js
GNU gdb 6.4.90-debian
This GDB was configured as "x86_64-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /home/drslump_admin/tmp/ry-node-d04e16e/node
test/mjsunit/test-next-tick.js
[Thread debugging using libthread_db enabled]
[New Thread 140694372927200 (LWP 20256)]
[New Thread 1091025248 (LWP 20260)]

TypeError: Object success has no method 'push'

at [object Object].addListener (node.js:173:26)
at [object Object].addErrback (node.js:277:17)

at readChunk (node.js:668:12)
at [object Object].<anonymous> (node.js:672:7)

at [object Object].emitSuccess (node.js:241:15)
at node.js:511:29

at node.js:1005:9

Program exited with code 01.
(gdb) backtrace
No stack.

----

Then I build the debug version and to my surprise it works!

$ ./configure --debug
$ ./make
$ ./node_g test/mjsunit/test-readdir.js
readdir /home/drslump_admin/tmp/ry-node-d04e16e/test/mjsunit/fixtures
[
"b",
"nested-index",
"test_ca.pem",
"x.txt",
"echo.js",
"print-chars.js",
"throws_error.js",
"multipart.js",
"a.js",
"test_key.pem",
"test_cert.pem",
"cycles"
]
exit

----

regards,
/imv

[Iván -DrSlump- Montes]

Since the debug build is working and I've been completely useless
trying to debug what the problem is with the normal one... may I ask
what are the implications of using the debug build?

It won't have to support much load, I'm just using it to run some
javascript validation functions and offering an http interface to
them.

thanks,
/imv

On Mon, Feb 8, 2010 at 9:55 PM, Iván -DrSlump- Montes

[Iván -DrSlump- Montes]

Good news, with the latest version (0.1.31) the problem seems to be fixed :)

regards,
/imv

On Thu, Feb 18, 2010 at 9:23 PM, Iván -DrSlump- Montes