[Bug 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest

[ Christian Ehrhardt ]

...ubuntu7 completed tonight thanks!
I tested 2 times from proposed in the local tester and working as expected now.

Unfortunately the systemd upload itself failed at some of the flaky
(boot and smoke) tests. But it seemed more like the VM it ran in would
be dead.

I retriggered the 4 tests (systemd, iproute2, cryptsetup, dbus)
currently blocked on i386-systemd with appropriate triggers (currently
triggers need: glibc, dbus, systemd).

So in a few hours we know if those now resolve ...

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

Title:
  gdm3 in cosmic fails to start fully in autopkgtest

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In systemd package for a while, there is a boot-and-services test
  case, which tries to install common/typical things and ensure they
  continue to operate with new systemd.

  One of the test cases is gdm3. The test case dependencies are:

  Tests: boot-and-services
  Depends: systemd-sysv,
    systemd,
    udev,
    systemd-container,
    systemd-coredump,
    libpam-systemd,
    xserver-xorg-video-dummy,
    xserver-xorg,
    gdm3 [!s390x],
    cron,
    network-manager,
    busybox-static,
    apparmor,
    pkg-config,
    python3

  The test does following:
  out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])                                                                                  
  self.assertIn(b'gdm-x-session gnome-session', out)                                                                                                 
  out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])                                                                                           
  self.assertIn(b'Xorg vt1', out)                                                                                                                    
  self.active_unit('gdm')

  However, this now errors out upon the first command, meaning gdm-x-session is not running anymore.
  On bionic, this test case continues to operate correctly in the autopkgtest cloud.

  test_gdm3 (__main__.ServicesTest) ... ERROR

  ======================================================================
  ERROR: test_gdm3 (__main__.ServicesTest)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 66, in test_gdm3
      out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
    File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
      **kwargs).stdout
    File "/usr/lib/python3.6/subprocess.py", line 418, in run
      output=stdout, stderr=stderr)
  subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' returned non-zero exit status 1.

  ----------------------------------------------------------------------
  Ran 24 tests in 18.974s

  FAILED (errors=1)

  From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386

  Thus it looks like there is a regression or a change of behavior of
  gdm3 in the cloud in cosmic; since bionic continues to work correctly.

  I will mark this test as an expected failure for now, and monitor it
  separately, as currently, this is blocking many migrations.

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