kernel-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

The upload auto-triggered new test runs of all DKMS packages against the
new DKMS:

 -  http://people.canonical.com/~ubuntu-archive/proposed-migration/vivid/update_excuses.html#dkms
    particularly http://autopkgtest.ubuntu.com/packages/t/tp-smapi/vivid/i386/  (as per SRU test case), first run failed, second run (with -proposed dkms) succeeds

 - http://people.canonical.com/~ubuntu-archive/proposed-migration/trusty/update_excuses.html#dkms
   http://autopkgtest.ubuntu.com/packages/t/tp-smapi/trusty/i386/

 - http://people.canonical.com/~ubuntu-archive/proposed-migration/precise/update_excuses.html#dkms
   http://autopkgtest.ubuntu.com/packages/t/tp-smapi/precise/amd64/

Note that there are some packages that are shown as "regression"; this
is because these DKMS packages don't work against these release's
default linux-meta, but they do work against some other kernel (e. g.
linux-meta-lts-vivid, or linux-ti-omap4). This is not a regression with
DKMS though, as these already failed with the previous DKMS.

Thus I consider this verified. Thanks Andy for fixing!

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1498896

Title:
  autopkgtest: only collect dkms make logs if they exist

Status in dkms package in Ubuntu:
  Fix Committed
Status in dkms source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Vivid:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed

Bug description:
  When testing binary packages from a dkms source we install each
  package and check if it has dkms configuration in it, if not we ignore
  it.  Unfortunatly we attempt to collect make.log for the dkms module
  regardless of whether it was a dkms package triggering it to fail and
  stop processing for this source:

      I: Installing binary package tp-smapi-source
      [...]
      /usr/lib/dkms/dkms-autopkgtest: 15: cd: can't cd to /var/lib/dkms

  SRU TEST CASE:
   - Run adt-run --apt-pocket=proposed -U tp-smapi --- qemu adt-precise-amd64-cloud.img   # (or on any other release)
   - With current version this fails like https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-precise/precise/i386/t/tp-smapi/20150923_105948%40/log.gz
   - With fixed version the "wrong" tp-smapi-source binary should be skipped and it should go on testing the tp-smapi-dkms package. THis should then build a module and succeed.

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