[Bug 1780767] [NEW] Some tests are flaky due to timeout

[Didier Roche]

Public bug reported:

The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
It's blocking randomly on different tests.

All tests that are stucked, implements closing a request via a timeout
(and then, executing "run"). The bet is that the timeout is short enough
(1s) so that, when autopkgtests infra is busy, time to execute the bash
subcommand is taking more than a second, and so "dismissing" is ran
before execution happens and the whole testsuite hangs.

There are few instances of setting this timeout function:
$ grep eout_add_sec test/*
test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, cont)
test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, cont)
test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, cont)
test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, c)
test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, c)

Short term solution could be to increase the timeout. Long term would be
to eliminate this potential race implementing cancelling differently.

** Affects: apport (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1780767

Title:
  Some tests are flaky due to timeout

Status in apport package in Ubuntu:
  New

Bug description:
  The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
  http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
  It's blocking randomly on different tests.

  All tests that are stucked, implements closing a request via a timeout
  (and then, executing "run"). The bet is that the timeout is short
  enough (1s) so that, when autopkgtests infra is busy, time to execute
  the bash subcommand is taking more than a second, and so "dismissing"
  is ran before execution happens and the whole testsuite hangs.

  There are few instances of setting this timeout function:
  $ grep eout_add_sec test/*
  test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, c)
  test/test_ui_gtk.py:        GLib.timeout_add_seconds(1, c)

  Short term solution could be to increase the timeout. Long term would
  be to eliminate this potential race implementing cancelling
  differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+subscriptions