Hiya,

On Fri, Jan 26, 2007 at 02:18:52AM +0300, генерал Пурпоз wrote:
> 78. send_bad_offset....... server child failed: socket read failed (-3): 
> Connection closed
> pass

The test for this one is actually not very portable, but it worked OK 
regardless; nothing to worry about either way.

> -> running `socket':
>  0. multi_init............ pass
>  1. resolve............... pass
>  ...snip...
> 24. small_writes.......... pass
> 25. large_writes.......... FAIL (write failed (-3): Broken pipe)

Can you look in the test/child.log log to see what happened to the 
server process here?  The section from:

**** Child forked for test large_writes ****

is the relevant bit.

> 26. echo_lines............ pass
> 27. blocking.............. pass
> 28. write_reset........... WARNING: got EOF, failed to elicit TCP RST
>     ...................... pass (with 1 warning)

This is nothing to worry about, it just means the test suite could not 
produce the particular TCP behaviour needed to test some code paths.

> -> running `ssl':
>  0. init.................. pass
>  ...snip...
>  7. dname_compare......... pass
>  8. dname_readable........ FAIL (certificate subject dname was `H0llo World, 
> Neon Hackers Ltd, Cambridge, Cambridgeshire, GB' not `HГЁllo World, Neon 
> Hackers Ltd, Cambridge, Cambridgeshire, GB')
>  9. import_export......... pass
>  ...snip...
> 47. auth_tunnel_creds..... pass
> <- summary for `ssl': of 48 tests run: 47 passed, 1 failed. 97.9%
> The only failed test here is due to the lack of UNICODE and UTF-8
> support on QNX4, I hope this is a minor issue, since I'll not use any
> certs with any non-ASCII characters. Please comment.

This gets reported on some other platforms too IIRC.  I think the 
problem is more likely that the UTF-8 characters don't make it through 
to the certificate from test/makekeys.sh.  Again, this is probably a 
problem in the test suite not the code.

> All other test suites report 100% passage.

Good news, thanks for sending this in.

Regards,

joe

_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon

Reply via email to