[zeromq-dev] C++ assertion failed with Java client

Frittum Johannes Johannes.Frittum at austrocontrol.at
Thu Feb 9 01:55:36 CET 2012

Hello Pieter!

> -----Ursprüngliche Nachricht-----
> Von: zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-
> bounces at lists.zeromq.org] Im Auftrag von Pieter Hintjens
> Gesendet: Mittwoch, 8. Februar 2012 21:31
> An: AJ Lewis
> Cc: ZeroMQ development list
> Betreff: Re: [zeromq-dev] C++ assertion failed with Java client
> On Tue, Feb 7, 2012 at 9:04 AM, AJ Lewis <aj.lewis at quantum.com> wrote:
> > I think this makes sense too.  "Check in early, check in often."
> Precisely. It is about lowering the latency between change and validation.

But don't forget to automatically unit-test on every check in.
Maybe some kind of continuous delivery pipeline could be setup for ZMQ...

Therefore automated tests (unit/component, functional, non-functional, performance) would be needed. Maybe I look at it if I have more time to spare - At least I could try to set up the pipeline to poll the repo for changes, build automatically from that and report about its outcome a few minutes later online. Then we can add tests gradually for every function that is added/changed. That way the test base can grow. We get automatic health feedback from the system.

If there is interest in that I can have a look.

Johannes Frittum

More information about the zeromq-dev mailing list