[Bug 1705482] [NEW] ADT tests periodically failing on s390x with the glib/testfilemonitor.test test case

[Dimitri John Ledkov]

Public bug reported:

http://autopkgtest.ubuntu.com/packages/glib2.0/artful/s390x

You can see that sometimes the ADT tests fail. With retries working.

Running test: glib/testfilemonitor.test
# random seed: R02S6148f6074ee8711c45886d3ff5c04648
1..5
# Start of monitor tests
**
GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
# GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
FAIL: glib/testfilemonitor.test (Child process killed by signal 6)

Running test: glib/testfilemonitor.test
# random seed: R02S453d93631f05d14fc46a0834c6ae2782
1..5
# Start of monitor tests
**
GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
# GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
FAIL: glib/testfilemonitor.test (Child process killed by signal 6)

And similar. I wonder if this is due to load on the host (these tests
are running in lxd) or due to unlucky random seeds. Is there a way to
rerun this individual glib test case, such that I could troubleshoot
this further and/or file an upstream bug report?

** Affects: glib2.0 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: adt-fail

** Tags added: adt-fail

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

Title:
  ADT tests periodically failing on s390x with the
  glib/testfilemonitor.test test case

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  http://autopkgtest.ubuntu.com/packages/glib2.0/artful/s390x

  You can see that sometimes the ADT tests fail. With retries working.

  Running test: glib/testfilemonitor.test
  # random seed: R02S6148f6074ee8711c45886d3ff5c04648
  1..5
  # Start of monitor tests
  **
  GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
  # GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
  FAIL: glib/testfilemonitor.test (Child process killed by signal 6)

  Running test: glib/testfilemonitor.test
  # random seed: R02S453d93631f05d14fc46a0834c6ae2782
  1..5
  # Start of monitor tests
  **
  GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
  # GLib-GIO:ERROR:../../../../../gio/tests/testfilemonitor.c:72:check_expected_event: assertion failed (e1->step == e2->step): (-1 == 2)
  FAIL: glib/testfilemonitor.test (Child process killed by signal 6)

  And similar. I wonder if this is due to load on the host (these tests
  are running in lxd) or due to unlucky random seeds. Is there a way to
  rerun this individual glib test case, such that I could troubleshoot
  this further and/or file an upstream bug report?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1705482/+subscriptions