Thanks Ganesh! On 25 January 2018 at 14:43, Ganesh Murthy <[email protected]> wrote: > Thanks Robbie. I have entered a JIRA to track this. > > https://issues.apache.org/jira/browse/DISPATCH-919 > > On Thu, Jan 25, 2018 at 7:16 AM, Robbie Gemmell <[email protected]> > wrote: > >> Is it possible to detect that it isnt installed and emit a warning >> when cmake is run? Or perhaps just when the tests are run? I think >> that could help folks running into this new requirement for the first >> time. >> >> The failures you get when running on a box without unittest2 didn't >> immediately scream 'install python-unittest2', and though it is now >> mentioned in the README it seems likely that someone updating from >> dispatch 1.0.0 to 1.1.0 wont necessarily see that or think to install >> that specifically first if they dont happen to already have it. >> >> Robbie >> >> On 21 December 2017 at 20:21, Ganesh Murthy <[email protected]> wrote: >> > As a fix to https://issues.apache.org/jira/browse/DISPATCH-894 , Qpid >> > Dispatch is now using Python's unittest2 (instead of unittest) to run >> unit >> > tests. >> > >> > https://pypi.python.org/pypi/unittest2 >> > >> > "unittest2 is a backport of the new features added to the unittest >> testing >> > framework in Python 2.7 and onwards. It is tested to run on Python 2.6, >> > 2.7, 3.2, 3.3, 3.4 and pypy." >> > >> > In order to run Qpid Dispatch master branch unit tests in your system, >> you >> > will have to install the python-unittest2 package which is available on >> > both Debian (Ubuntu) and RPM based systems (RHEL, Fedora, CentOS etc.) >> > >> > Here is the commit if you want to take a look - >> > >> > https://github.com/apache/qpid-dispatch/commit/ >> 4a173e1ec0f7e0e8f9d7d37b9549d4f9c9d37fb0 >> > >> > Thanks. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
