Merge lp:~sylvain-pineau/checkbox/hwcollect_cleanup into lp:checkbox

[Sylvain Pineau]

cleanup of unused provider, hwcollect. hwsubmit testplan in the checkbox provider contains the same thing.

[Paul Larson (pwlars)]

+1

review: Approve

=== removed file 'providers/README.rst'
--- providers/README.rst	2015-08-17 10:03:17 +0000
+++ providers/README.rst	1970-01-01 00:00:00 +0000
@@ -1,95 +0,0 @@
-Plainbox Providers
-==================
-
-This directory contains a number of Plainbox Providers. Those providers are
-kept here for both historic reasons and some extra simplicity in making changes
-that also require synchronized updates to other parts of the greater Checkbox
-project (e.g. changes to checkbox-support or to plainbox).
-
-In-Tree Providers
-=================
-
-The following providers are kept here, in tree:
-
-``2015.com.canonical.certification:qml-tests/``:
-
-    Tests natively implemented in QML and the Ubuntu SDK libraries. Tests in
-    this provider are used by Checkbox on the Ubuntu Phone.
-    
-``plainbox-provider-checkbox/``:
-
-    Oldest and most varied collection of tests. The tests themselves are used
-    by various other providers (they are referenced from their test plans).
-    
-``plainbox-provider-hwcollect/``:
-
-    The provider that is meant to fuel the needs of ``canonical-hw-collection``
-    tool. Currently unused.
-
-``plainbox-provider-piglit/``:
-
-    A small provider, split off from the Checkbox provider, focused on wrapping
-    and exposing the ``piglit`` OpenGL testing tool. Jobs from this provider
-    are used in some test plans, most notably in CDTS.
-
-``plainbox-provider-resource-generic/``:
-
-    A provider much smaller than checkbox that is aways used alongside with it.
-    This provider contains various resource jobs and utility scripts. It is
-    used in both on Ubuntu desktop and server environments. 
-
-``plainbox-provider-snappy-ubuntu-core/``:
-
-    A provider that contains new jobs focused on Ubuntu Snappy Core
-    environment. As of August 2015 this is an area of active research.
-
-``plainbox-provider-ubuntu-touch/``:
-
-    A provider that contains now jobs focused on Ubuntu Phone environments.
-    This provider is shipped, bundled, with Checkbox Touch and is available in
-    the Ubuntu Store. 
-
-Out-Of-Tree Providers
-=====================
-
-The following providers are kept out of tree, they are referenced here so
-that developers can find pointers to some of the code that was here before.
-
-
-``plainbox-provider-canonical-driver-test-suite``:
-
-    The provider is present on the ``cdts`` project, on Lauchpad, in bzr, in
-    the main branch of the project. This provider refers to various jobs in the
-    checkbox and piglit providers.
-
-    A handy link to the code is:
-
-    https://code.launchpad.net/~checkbox-ihv-ng/cdts/trunk
-
-``plainbox-provider-certification-client``:
-
-    The provider is present on the
-    ``plainbox-provider-canonical-certification`` project, on Launchpad, in
-    Git, in the ``master-client`` branch.
-
-    This provider is used by the Canonical Certification team for certification
-    of "client" hardware (desktops, laptops, etc.). This provider is mainly a
-    list of test plans that refer to the jobs in the checkbox provider.
-
-    A handy link to the code is:
-
-    https://code.launchpad.net/~checkbox-dev/plainbox-provider-canonical-certification/+git/plainbox-provider-canonical-certification/+ref/master-client
-
-``plainbox-provider-certification-server``:
-
-    The provider is present on the
-    ``plainbox-provider-canonical-certification`` project, on Launchpad, in
-    Git, in the ``master-server`` branch.
-
-    This provider is used by the Canonical Certification team for certification
-    of server hardware. This provider is mainly a list of test plans that refer
-    to the jobs in the checkbox provider.
-
-    A handy link to the code is:
-
-    https://code.launchpad.net/~checkbox-dev/plainbox-provider-canonical-certification/+git/plainbox-provider-canonical-certification/+ref/master-server
 
=== removed directory 'providers/plainbox-provider-hwcollect'
=== removed file 'providers/plainbox-provider-hwcollect/.bzrignore'
--- providers/plainbox-provider-hwcollect/.bzrignore	2015-08-03 14:10:45 +0000
+++ providers/plainbox-provider-hwcollect/.bzrignore	1970-01-01 00:00:00 +0000
@@ -1,2 +0,0 @@
-dist/*.tar.gz
-build/mo/*
 \ No newline at end of file
 
=== removed file 'providers/plainbox-provider-hwcollect/.gitignore'
--- providers/plainbox-provider-hwcollect/.gitignore	2015-08-03 14:10:45 +0000
+++ providers/plainbox-provider-hwcollect/.gitignore	1970-01-01 00:00:00 +0000
@@ -1,2 +0,0 @@
-dist/*.tar.gz
-build/mo/*
 \ No newline at end of file
 
=== removed file 'providers/plainbox-provider-hwcollect/README.md'
--- providers/plainbox-provider-hwcollect/README.md	2015-08-03 14:10:45 +0000
+++ providers/plainbox-provider-hwcollect/README.md	1970-01-01 00:00:00 +0000
@@ -1,47 +0,0 @@
-Skeleton for a new PlainBox provider
-====================================
-
-This is a skeleton PlainBox provider that was generated using
-``plainbox startprovider ...``.
-
-It is just the starting point, there is nothing here of value to you
-yet. If you know how this works then just remove this file along with
-other example content and start working on your new tests,
-otherwise, read on.
-
-Inside the ``jobs/`` directory you will find several files that define
-a number of "jobs" (more than one job per file actually). A job, in
-PlainBox parlance, is the smallest piece of executable test code. Each
-job has a name and a number of other attributes.
-
-Jobs can be arranged in lists, test plans if you will that are known
-as "whitelists". Those are defined in the ``whitelists/`` directory,
-this time one per file. You can create as many whitelists as you need,
-referring to arbitrary subsets of your jobs.
-
-Then there are the ``bin/`` and ``data/`` directories. Those are
-entirely for custom content you may need. You can put arbitrary
-executables in ``bin/``, and those will be available to your job
-definitions. Similarly you can keep any data your jobs might need
-inside the ``data/`` directory. Referring to that directory at runtime
-is a little bit trickier but one of the examples generated in this
-skeleton shows how to do that.
-
-Lastly there is the ``manage.py`` script. It requires python3 to run.
-It depends on the python3-plainbox Debian package (or just the
-PlainBox 0.5 upstream package) installed. This script can automate and
-simplify a number of tasks that you will want to do as a test
-developer.
-
-Run ``./manage.py --help`` to see what sub-commands are available. You
-can additionally pass ``--help`` to each sub command, for example
-``./manage.py install --help`` will print the description of the
-install command and all the arguments it supports.
-
-That is it for now. You should check out the official documentation
-for test authors at
-http://plainbox.readthedocs.org/en/latest/author/index.html
-
-If you find bugs or would like to see additional features developed
-you can file bugs on the parent project page:
-https://bugs.launchpad.net/checkbox/+filebug
 \ No newline at end of file
 
=== removed file 'providers/plainbox-provider-hwcollect/manage.py'
--- providers/plainbox-provider-hwcollect/manage.py	2015-08-03 14:10:45 +0000
+++ providers/plainbox-provider-hwcollect/manage.py	1970-01-01 00:00:00 +0000
@@ -1,21 +0,0 @@
-#!/usr/bin/env python3
-from plainbox.provider_manager import setup, N_
-
-# You can inject other stuff here but please don't go overboard.
-#
-# In particular, if you need comprehensive compilation support to get
-# your bin/ populated then please try to discuss that with us in the
-# upstream project IRC channel #checkbox on irc.freenode.net.
-
-# NOTE: one thing that you could do here, that makes a lot of sense,
-# is to compute version somehow. This may vary depending on the
-# context of your provider. Future version of PlainBox will offer git,
-# bzr and mercurial integration using the versiontools library
-# (optional)
-
-setup(
-    name='2013.com.canonical.certification:hwcollect',
-    version="1.0",
-    description=N_("Plainbox provide for the Canonical hardware collection tool"),
-    gettext_domain="plainbox-provider-hwcollect"
-)
 
=== removed directory 'providers/plainbox-provider-hwcollect/po'
=== removed file 'providers/plainbox-provider-hwcollect/po/POTFILES.in'
--- providers/plainbox-provider-hwcollect/po/POTFILES.in	2016-03-07 07:18:04 +0000
+++ providers/plainbox-provider-hwcollect/po/POTFILES.in	1970-01-01 00:00:00 +0000
@@ -1,3 +0,0 @@
-[encoding: UTF-8]
-[type: gettext/rfc822deb] units/hwcollect.pxu
-manage.py
 
=== removed directory 'providers/plainbox-provider-hwcollect/units'
=== removed file 'providers/plainbox-provider-hwcollect/units/hwcollect.pxu'
--- providers/plainbox-provider-hwcollect/units/hwcollect.pxu	2015-08-08 22:22:28 +0000
+++ providers/plainbox-provider-hwcollect/units/hwcollect.pxu	1970-01-01 00:00:00 +0000
@@ -1,35 +0,0 @@
-unit: test plan
-id: hwcollect
-_name: Hardware collection
-include:
-    cdimage
-    cpuinfo
-    device
-    dmi
-    dpkg
-    gconf
-    lsb
-    meminfo
-    module
-    package
-    uname
-    usb
-    __info__
-    info/buildstamp
-    cpuinfo_attachment
-    dmesg_attachment
-    dmi_attachment
-    dmidecode_attachment
-    kernel_cmdline_attachment
-    recovery_info_attachment
-    dell_bto_xml_attachment
-    lsmod_attachment
-    dkms_info_attachment
-    lspci_attachment
-    lspci_standard_config_attachment
-    modinfo_attachment
-    modprobe_attachment
-    modules_attachment
-    sysfs_attachment
-    sysctl_attachment
-    udev_attachment