open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 ADT test failure with linux-hwe 4.13.0-42.47~16.04.1

[Khaled El Mously]

Testing failed on:
    amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/open-vm-tools/20180518_024018_c3663@/log.gz
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/open-vm-tools/20180518_023222_c3663@/log.gz

[Christian Ehrhardt  (paelzer)]

Hi Khaled,
I must admit http://autopkgtest.ubuntu.com/packages/open-vm-tools puzzles me.
From a source perspective open-vm-tools doesn't have (and never had) a autopkgtest.
So I wonder why there are good/bad tests at all.

In addition the two links you sent are not failing:
  SKIP no tests in this package

So what exactly is the request on the skipped tests.
It is correct to skip them as there are no tests in this package.

[Khaled El Mously (kmously)]

Thanks for the quick response Christian.

This log shows an example of the old behaviour of the open-vm-tools packagetest:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/o/open-vm-tools/20180510_164956_6d88c@/log.gz

which used to report a "command1 PASS" instead of the current "SKIP no tests in this package". This is why it appears as a regression in the kernel automated tests.

Is this change in behaviour expected?

[Christian Ehrhardt  (paelzer)]

Hi Khaled,
I've seen the old logs as well (which was triggering the puzzlement I stated above).

I have wondered about that command1 test and might feel ashamed once we find out where it came from, but for now the point is that there is no debian/test in ANY revision.

In a repo containing all revisions of open-vm-tools (Debian and Ubuntu):
$ git log --follow -- debian/tests/control
$ git log --all --full-history -- debian/tests/control
Both are empty, so there never was a test from my POV.

And for example your link tests:
 open-vm-tools is already the newest version (2:10.1.10-3ubuntu0.1).
But if I check out the tarball (or form my git) content of pkg/import/2%10.1.10-3ubuntu0.1 then there is no debian/tests dir at all.

$ pull-lp-source open-vm-tools 2:10.1.10-3ubuntu0.1
pull-lp-source: Downloading open-vm-tools version 2:10.1.10-3ubuntu0.1
pull-lp-source: Downloading open-vm-tools_10.1.10.orig.tar.gz from archive.ubuntu.com (3.379 MiB)
pull-lp-source: Downloading open-vm-tools_10.1.10-3ubuntu0.1.debian.tar.xz from archive.ubuntu.com (0.045 MiB)
pull-lp-source: Downloading open-vm-tools_10.1.10-3ubuntu0.1.debian.tar.xz from launchpad.net (0.045 MiB)
gpgv: Signature made Do 15 Feb 2018 13:41:37 CET
gpgv: using RSA key BA3E29338280B242
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./open-vm-tools_10.1.10-3ubuntu0.1.dsc
dpkg-source: info: extracting open-vm-tools in open-vm-tools-10.1.10
dpkg-source: info: unpacking open-vm-tools_10.1.10.orig.tar.gz
dpkg-source: info: unpacking open-vm-tools_10.1.10-3ubuntu0.1.debian.tar.xz
dpkg-source: info: applying debian/0001-kvers.patch
dpkg-source: info: applying debian/pam-use-common-auth-account
dpkg-source: info: applying debian/max_nic_count
dpkg-source: info: applying from_arch/0001-Fix-vmxnet-module-on-kernels-3.16.patch
dpkg-source: info: applying debian/enable_vmhgfs-fuse_by_default
dpkg-source: info: applying debian/vmxnet_fix_kernel_4.7.patch
dpkg-source: info: applying debian/scsi-udev-rule
dpkg-source: info: applying resolutionKMS-wayland.patch
[✓]─[paelzer@lap:/tmp]──[17828]──[08:10 Fr Mai 18]──
$ ll open-vm-tools-10.1.10/debian/tests
ls: cannot access 'open-vm-tools-10.1.10/debian/tests': No such file or directory

So what did it test - I don't know atm?

[Launchpad Janitor (janitor)]

[Expired for open-vm-tools (Ubuntu) because there has been no activity for 60 days.]