debcrafters-packages team mailing list archive

[Andreas Hasenack <2119291@xxxxxxxxxxxxxxxxxx>]

Marking the main task of gtk4 as fix released, because we haven't seen
this problem in questing (or plucky).

** Also affects: mesa (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: gtk4 (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: gtk4 (Ubuntu Noble)
    Milestone: None => ubuntu-24.04.3

** Changed in: gtk4 (Ubuntu Noble)
   Importance: Undecided => Critical

** Changed in: gtk4 (Ubuntu)
       Status: New => Fix Released

** Changed in: gtk4 (Ubuntu Noble)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2119291

Title:
  mesa 25.0.7 SRU breaks gtk4 on s390x

Status in gtk4 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in gtk4 source package in Noble:
  Fix Committed
Status in mesa source package in Noble:
  New

Bug description:
  [ Impact ]

  There are a number of gtk4 tests (build-time, and again at autopkgtest
  time) that are failing on s390x *only* when run in the combination of
  an updated mesa package (25.0.7-0ubuntu0.24.04.1).

  s390x is not a desktop platform, there are no desktop images for it,
  and gtk4 is not seeded in that architecture. While it would be best to
  fully understand what is making these tests fail, it's best to skip
  them for now in that architecture only, so that users in other
  architectures can benefit from the mesa and gtk4 updates.

  
  [ Test Plan ]
  The failure manifests itself in the build-time tests, which are again repeated at autopkgtest time. Therefore, the test plan consists of:
  - no build failure in any platform, and specifically s390x
  - no autopkgtest failure in any platform, and specifically s390x

  [ Where problems could occur ]

  This SRU is skipping certain gtk4 tests in s390x only, not reducing
  the test coverage in other architectures.

  Since the real cause of the test failures was not determined yet (and
  they only fail in combination with the new mesa update, as mentioned
  in the [impact] section), it's possible that by skipping these tests
  we are overlooking something that could be important down the line.

  [ Other Info ]

  There is already a long list of tests that are being skipped on s390x,
  and we are adding more tests to that list.

  [ Original Description ]

  First seen in the autopkgtest:

  https://autopkgtest.ubuntu.com/packages/g/gtk4/noble/s390x

  mesa 25.0.7-0ubuntu0.24.04.1 regresses the autopkgtest of gtk4
  4.14.5+ds-0ubuntu0.1 on s390x.

  42515s build-x11            PASS (superficial)
  42515s build-wayland        FAIL timed out
  42515s python3-gi-x11       PASS (superficial)
  42515s python3-gi-wayland   FAIL timed out
  42515s installed-tests-x11  PASS
  42515s installed-tests-wayland FAIL non-zero exit status 2
  42515s installed-tests-flaky-x11 FLAKY non-zero exit status 2
  42515s installed-tests-flaky-wayland FLAKY non-zero exit status 2

  The build-wayland and python3-gi-wayland autopkgtests do not terminate
  and eventually hit the time out.

  We have tried running the tests on a bigger instance (added to
  'big_packages') and have tried triggering the tests with 'all-
  proposed=1'.

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