lttng team mailing list archive

[Launchpad Bug Tracker <1777682@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.7

---------------
lttng-modules (2.8.0-1ubuntu1~16.04.7) xenial; urgency=medium

  * ubuntu_lttng_smoke_test failed on Azure 4.15 (LP: #1778642)
    - debian/patches/0041-Fix-do-not-use-CONFIG_HOTPLUG_CPU-for-the-new-hotplu.patch
    - debian/patches/0042-Cleanup-comment-about-CONFIG_HOTPLUG_CPU-ifdef.patch

 -- Kleber Sacilotto de Souza <kleber.souza@xxxxxxxxxxxxx>  Thu, 19 Jul
2018 17:47:16 +0200

** Changed in: lttng-modules (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
LTTng, which is subscribed to lttng-modules in Ubuntu.
Matching subscriptions: lttng-modules-bugs
https://bugs.launchpad.net/bugs/1777682

Title:
  lttng-modules 2.8.0-1ubuntu1~16.04.5 ADT test failure with linux-hwe-
  edge 4.15.0-23.25~16.04.1

Status in lttng-modules package in Ubuntu:
  In Progress
Status in lttng-modules source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  Currently the DKMS package fails to install on supported custom
  kernels that are based on 4.15. That includes the current 4.15
  hwe-edge and some of the custom and cloud kernels as well.

  [Test Case]

  Install the broadcom-sta package with the 4.15 hwe-edge kernel. The
  package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that, the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.13
  - linux-hwe-edge 4.15
  - linux-azure 4.15

  [Original Description]

  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lttng-modules/20180528_193635_39048@/log.gz
      arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lttng-modules/20180528_195032_39048@/log.gz
      armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/lttng-modules/20180528_194139_39048@/log.gz
      i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lttng-modules/20180528_194024_39048@/log.gz
      ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lttng-modules/20180528_194343_39048@/log.gz
      s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lttng-modules/20180528_193734_39048@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1777682/+subscriptions