5 seconds for the shared ros test is not enough

Bug #1673621 reported by Leo Arias
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
High
Kyle Fazzari

Bug Description

5 seconds to set up, run and receive the message in the shared ros is sometimes not enough:

https://paste.ubuntu.com/24191610/

In that execution, 5 seconds was enough just to send the third message. And no message was received on the other side.

On this other execution, the 7th message was the first received: https://paste.ubuntu.com/24191611/

So, we should increase the timeout.

Tags: tests
Revision history for this message
Leo Arias (elopio) wrote :
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

We changed it to 30s and still see timeouts on some runs. After a 2 hour run it is not nice to see a failure due to racy timeouts so I suggest we go the mosquitto route (maybe assign to Kyle).

Leo Arias (elopio)
Changed in snapcraft:
assignee: Leo Arias (elopio) → Kyle Fazzari (kyrofa)
Revision history for this message
Kyle Fazzari (kyrofa) wrote :

Here, this will make them more similar to the mosquitto demo and exit after a single message has been received: https://github.com/snapcore/snapcraft/pull/1201 .

Changed in snapcraft:
status: In Progress → Fix Committed
milestone: none → 2.28
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.