Add autostart file for plainbox.
checkbox: add behavior probing tests for ResourceMap

Those teats check how ResouceMap and assoiated ResourceIterator,
ResourceObject classes behave in practice. It is a form of reverse
engineering by throwing values at a function and checking what gets
returned (obviously I was reading the source while working on this).

There are also some examples of how to run unsafe via resource programs

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
exporter: move ByteStringStreamTranslator to exporter module

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
scripts/rendercheck_test, scripts/graphics_stress_test, 
jobs/rendercheck.txt.in, jobs/stress.txt.in - Allow blacklisting of 
specific rendercheck tests and use this to exclude the 'repeat' test
from the set of rendercheck tests that run (LP: #1164566)
sru: fix crash on exporting XML file

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
MANIFEST.in: put .xml and .txt files into source tarball

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
run: PEP8 fixes

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
run: spell UTF-8 this way

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
integration_tests: fix PEP8 issues

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
scripts: network_device_info: fix PEP8 issues

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
scripts: network_device_info: remove unused imports

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
scripts: network_device_info: rework style

Using filter() with lambda is deprecated in favor of list comprehensions

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
depmgr: iterate over dependencies in deterministic order

The DependencySolver._visit() job iterates over each dependency as
computed by the DependencySolver._get_dependency_set() method. This
returns a set so the ordering is unspecified.

It makes sense to make this part deterministic so that we always run
jobs in the same order. It also fixes random "problems" for integration
tests that check the verbatim copy of the output.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
session: iterate over dependencies in deterministic order

There is one aspect of _recompute_job_readiness() that is
not deterministic. The loop that checks if each direct dependency
ran correctly iterates over a set returned by job.get_direct_dependencies()

Being deterministic is a desirable property so let's fix this by
sorting the dependencies.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
exporter: text: add missing newline to each output line

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
exporter: text: provide deterministic output

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
exporter: prettify some of the canned output

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
exporter: rfc822: provide deterministic output

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
exporter: text: spell UTF-8 this way

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
"[r=roadmr][bug=][author=zkrynicki] automatic merge by tarmac"