+1 * kit contents ** signature appears ok ** md5sum checks ok ** ?? I can't figure out how to deal with the binary .sha512 file? how does one test that?
* functionality ** compiles and runs binary test against proton-python, proton-cpp, and amqpnetlite clients ** ran some large content tests OK with same clients When things go wrong in this test environment it is not easy figuring out what happened. There are so many places for things to fail: Client protocol error, client out of memory or other process error, broker protocol or memory or process issue, zombie processes causing broker to hold onto hundreds of megabytes of memory and that prevents the next test from starting, actual interoperability errors, etc. That said, this is still a useful framework. ----- Original Message ----- > From: "Kim van der Riet" <kim.vdr...@redhat.com> > To: users@qpid.apache.org > Sent: Friday, October 27, 2017 2:32:49 PM > Subject: [VOTE] Release of qpid-interop-test 0.1.0 > > This is the first official release of the test tool qpid-interop-test. > > I have provided a release candidate at: > https://dist.apache.org/repos/dist/dev/qpid/interop-test/0.1.0-rc4/ > > Instructions for building and installation are in QUICKSTART.md. > > Please test and vote. > > Thanks, > Kim van der Riet > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
