Timeout doesn't work for manual tests

Bug #377986 reported by Javier Collado
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Medium
Marc Tardif

Bug Description

When running a manual test that contains a command and a description with the $output placeholder, the test is skipped and shown in the results page as not being handled by any plugin. Looking into the logs, it seems that the problem is because the command takes too long to complete according to this error message:
DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

If the test is run with a timeout value added in the test suite, then a different error arises and the command is also aborted:
AttributeError: 'Frontend' object has no attribute 'test'

Please find attached the backtrace for both errors.

Revision history for this message
Javier Collado (javier.collado) wrote :
Revision history for this message
Javier Collado (javier.collado) wrote :

I forgot to ask, what is the default timeout value? I would have expected it to be infinite by default, but it seems it's not or maybe I'm mixing two different timeouts (the on for the test and the on for dbus).

Changed in checkbox:
assignee: nobody → Marc Tardif (cr3)
Revision history for this message
Javier Collado (javier.collado) wrote :

One side effect of this problem seems to be that test case execution finishes unexpectedly and test report is displayed without running shell test cases

David Murphy (schwuk)
Changed in checkbox:
importance: Undecided → Medium
milestone: none → 0.8-alpha3
status: New → Triaged
Marc Tardif (cr3)
Changed in checkbox:
status: Triaged → In Progress
Marc Tardif (cr3)
Changed in checkbox:
status: In Progress → Fix Committed
Marc Tardif (cr3)
Changed in checkbox:
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

Bug attachments

Remote bug watches

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