nanomsg-0.6-beta vs2010 win32 build failed:
1> 91% tests passed, 3 tests failed out of 33
1>
1> Total Test time (real) = 41.32 sec
1>
1> The following tests FAILED:
1> 7 - tcp_shutdown (Failed)
1> 8 - ws (Not Run)
1> 9 - tcpmux (Not Run)
1> Errors while running CTest
CallStack:
msvcr100d.dll!_NMSG_WRITE(int rterrnum) 行 217 C
msvcr100d.dll!abort() 行 61 C
nanomsg.dll!nn_err_abort() 行 33 C
nanomsg.dll!nn_usock_handler(nn_fsm * self, int src, int type, void * srcptr)
行 989 C
nanomsg.dll!nn_fsm_feed(nn_fsm * self, int src, int type, void * srcptr) 行 72nanomsg.dll!nn_worker_routine(void * arg) 行 203 C
C
All,
I’ve released (for real this time!) nanomsg-0.6-beta. This release
has quite a few improvements since 0.5, and various fixes, so I highly
recommend updating to it. Notably, the web sockets support was
integrated post-0.5, and there is a wire protocol change for surveyor
that makes it possible for a respondent to peer with multiple
surveyors. (And, btw, also makes it possible to create devices that
behave properly with surveyor.)
As of 0.6, the download page has gotten some changes. Notably, I’m
using github releases for actually releasing content, which gives an
HTTPS secure download, which should increase confidence in the
content. I’m still providing MD5 and SHA1 on the download page. The
legacy versions are still served from the download.nanomsg.org
<http://download.nanomsg.org/> site, but new versions starting with
0.6 are no longer posted there. Feel free to go ahead and download
from the github releases page going forward though.
Also, the build includes continuous integration and deployment
provided by Travis CI and AppVeyor. Again, this should increase
overall confidence in the project and hopefully minimize the
likelihood of regressions.
The legacy waterfall testing is still present, but as it is provided
entirely by volunteer resources, I felt it better to rely on services
offered by a commercial concern that focuses on CI as a core delivery
product. This also lets me get the automated deployment integrated,
which is a huge benefit.
Hopefully releases of future versions will have fewer hiccups and we
can resume a more timely release train.
- Garrett
