Skip to content


Subversion checkout URL

You can clone with
Download ZIP


windows x86: test failures on master #4094

piscisaureus opened this Issue · 1 comment

2 participants

=== release test-debugger-client ===
Path: simple/test-debugger-client
>>> new node process: 6672
>>> starting debugger session
>>> connecting...ready!
>>> new node process: 7856
>>> starting debugger session
>>> connecting...ready!
>>> new node process: 3232
>>> starting debugger session
>>> connecting...ready!
requesting version
>>> killing node process 6672

requesting scripts
got 14 scripts
>>> killing node process 7856

eval 2+2
Command: D:\node4\Release\node.exe D:\node4\test\simple\test-debugger-client.js
--- TIMEOUT ---
=== release test-debugger-repl ===
Path: simple/test-debugger-repl
There was an internal error in Node's debugger. Please report this bug.
./node debug --port=13683 D:\node4\test\fixtures/breakpoints.js
Error: This socket is closed.
Command: D:\node4\Release\node.exe D:\node4\test\simple\test-debugger-repl.js
=== release test-listen-fd-ebadf ===
Path: simple/test-listen-fd-ebadf
Command: D:\node4\Release\node.exe D:\node4\test\simple\test-listen-fd-ebadf.js
=== release test-tls-session-cache ===
Path: simple/test-tls-session-cache
unknown option -no_ticket
usage: s_client args

 -host host     - use -connect instead
 -port port     - use -connect instead
 -connect host:port - who to connect to (default is localhost:4433)
 -verify depth - turn on peer certificate verification
 -cert arg     - certificate file to use, PEM format assumed
 -certform arg - certificate format (PEM or DER) PEM default
 -key arg      - Private key file to use, in cert file if
                 not specified but cert file is.
 -keyform arg  - key format (PEM or DER) PEM default
 -pass arg     - private key file pass phrase source
 -CApath arg   - PEM format directory of CA's
 -CAfile arg   - PEM format file of CA's
 -reconnect    - Drop and re-make the connection with the same Session-ID
 -pause        - sleep(1) after each read(2) and write(2) system call
 -showcerts    - show all certificates in the chain
 -debug        - extra output
 -msg          - Show protocol messages
 -nbio_test    - more ssl protocol testing
 -state        - print the 'ssl' states
 -nbio         - Run with non-blocking IO
 -crlf         - convert LF from terminal into CRLF
 -quiet        - no s_client output
 -ign_eof      - ignore input eof (default when -quiet)
 -ssl2         - just use SSLv2
 -ssl3         - just use SSLv3
 -tls1         - just use TLSv1
 -dtls1        - just use DTLSv1
 -mtu          - set the MTU
 -no_tls1/-no_ssl3/-no_ssl2 - turn off that protocol
 -bugs         - Switch on all SSL implementation bug workarounds
 -serverpref   - Use server's cipher preferences (only SSLv2)
 -cipher       - preferred cipher to use, use the 'openssl ciphers'
                 command to see what is available
 -starttls prot - use the STARTTLS command before starting TLS
                 for those protocols that support it, where
                 'prot' defines which one to assume.  Currently,
                 only "smtp", "pop3", "imap", and "ftp" are supported.
 -engine id    - Initialise and use the specified engine
 -rand file:file:...

  throw new assert.AssertionError({
AssertionError: 1 == 0
    at ChildProcess.<anonymous> (D:\node4\test\simple\test-tls-session-cache.js:87:14)
    at ChildProcess.EventEmitter.emit (events.js:96:17)
    at Process.ChildProcess._handle.onexit (child_process.js:698:12)
    at process._makeCallback (node.js:248:20)
Command: D:\node4\Release\node.exe D:\node4\test\simple\test-tls-session-cache.js
=== release test-dns ===
Path: internet/test-dns
looking up =  null
  throw new assert.AssertionError({
AssertionError: false == true
    at Object.req.oncomplete (D:\node4\test\internet\test-dns.js:392:10)
    at process._makeCallback (node.js:248:20)
Command: D:\node4\Release\node.exe D:\node4\test\internet\test-dns.js
[08:01|% 100|+ 519|-   5]: Done

We now have green builds for v0.12 branch on windows

@tjfontaine tjfontaine closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.