software/mosquitto/test: fix flaky test
This test is using two connection one with a client to subscribe to a topic and wait for message and another one with publish.single to publish to the topic. The test was failing from time to time because the publish might have happened after the client was subscribed. Refactor the test to use `loop` on the client to have more control and be able to wait for the client to be subscribed using the `on_subscribe` callback. The test is also factorized, instead of having the same test twice for IPv4 and IPv6, we pass the host as parameter.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#721852
external
|
Cloudooo.UnitTest-Master |
00:14:43
|
||||||
passed |
#721863
external
|
ERP5.StandaloneDeploymentScriptTest-Debian.Buster |
00:49:01
|
||||||
passed |
#721824
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:27:40
|
||||||
failed |
#721840
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:24:35
|
||||||
passed |
#721836
external
|
SlapOS.Eggs.UnitTest-Master.Python3Next |
00:24:53
|
||||||
passed |
#721887
external
|
Wendelin.StandaloneDeploymentScriptTest-Debian.Buster |
00:37:48
|
||||||
passed |
#721857
external
retried
|
Wendelin.StandaloneDeploymentScriptTest-Debian.Buster |
00:50:42
|
||||||