Re: [mosquitto-dev] Errors running tests on (cross-compiled) target

["Colin Helliwell" <colin.helliwell@xxxxxxxxxxxxxx>]

Pretty much sorted now, thanks.
However for the lib tests I'm having to install mosq_test.py into both lib/c and lib/cpp [I install the two sets of .py's/.test's into those two subdirectories to keep them separate], otherwise mosq_test isn't found. The broker tests are ok with it just in the parent directory (the same level as lib, broker and ssl).
Can't spot what path might need editing for the lib tests to find it?

-----Original Message-----
From: rogerlight@xxxxxxxxx [mailto:rogerlight@xxxxxxxxx] On Behalf Of Roger Light
Sent: 01 June 2016 15:43
To: colin.helliwell@xxxxxxxxxxxxxx; General development discussions for the mosquitto project <mosquitto-dev@xxxxxxxxxxx>
Subject: Re: [mosquitto-dev] Errors running tests on (cross-compiled) target

Hi Colin,


> These 12 failing tests are:
>   03-pattern-matching-helper.py
>   03-publish-b2c-disconnect-qos1-helper.py
>   03-publish-b2c-disconnect-qos2-helper.py
...

These aren't separate tests, they are helper scripts for other tests.
If those are the only ones that fail it looks like you're good to go.

> The other fail is in 01-connect-uname-password-success-no-tls.py

This one is only for if you've compiled without openssl support and hence the passwords would not be hashed - a bad idea of course! You don't need to worry about this one either.

I looked up your site, you're about the closest geographically of anybody that has been in touch on this list :)

Cheers,

Roger