Revert "UI progress: set a 1 second cycle for a complete throbber iteration"

This reverts commit 10e6af662844a4c9df6994bfc7536f0413fbc82d.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
job mainloop: if test state is received, do not go through another loop

There's a bug in the current job mainloop that causes significant delays.
The test state is received from the test via the queue in an async fashion,
but if a proper state is received, we failt to mark the loop as done.

This patch, in conjunction with the previous reverted commit, puts the
queue timeout in sync with the UI timeout and puts the cycle timeout
back to 1s, without the adverse consequences.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Job main loop: just break out of the loop instead of using special flags

As spotted by Ruda. Thanks!

CC: Ruda Moura <rmoura@redhat.com>
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Job main loop: add functional tests to the selftest suite

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Merge pull request #144 from clebergnu/test-execution-times-async

Test execution times async
Job main loop: functional tests timing

Looks like test bots, such as travis, can have very little resources
at times and run things really slowly, example:

======================================================================
FAIL: Sleeptest is supposed to take 1 second, let's make a sandwich of
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/avocado-framework/avocado/selftests/all/
functional/avocado/basic_tests.py", line 238, in test_runner_sleep_fail_sleep_timing
    self.assertLess(actual_time, 4.0)
AssertionError: 4.036144018173218 not less than 4.0

Let's increase the maximum expected times.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Merge pull request #145 from clebergnu/mainloop-functional-test-timeout

Job main loop: functional tests timing