lp:~smoser/curtin/trunk.trusty-raid5bcache

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~curtin-dev/curtin/trunk at revision 317

Server Team CI bot: Approve (continuous-integration) on 2015-12-05

curtin developers: Pending requested 2015-12-05

Diff: 11 lines (+4/-0)

1 file modified

tests/vmtests/test_raid5_bcache.py (+4/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1523037: dname does not work for partitions on trusty

Medium

Confirmed

Link a bug report

Related blueprints

316. By Scott Moser on 2015-12-05

do not expect sda-part2 to exist in /dev/disk/by-dname on trusty

This never worked, but we did not see failure before because of a
test case never properly executing.

315. By Scott Moser on 2015-12-04

vmtests: improve output of vmtests

This changes vmtest to put its output in a single top level directory.
By default:
  /tmp/vmtest-2015-11-16T204216.241018.log
  /tmp/vmtest-2015-11-16T204216.241018/

Inside that dir are files named per each test, like:
   WilyTestBasic

Add tools/jenkins-runner that simplifies jenkins running so that
artifacts can easily be collected. If you run tools/jenkins-runner
it will create output/ and put all files in there.

Also now allow configuration of what things to keep from the vmtest run
and when to keep them. Default value is to keep all files from failed
tests. This is configurable via CURTIN_VMTEST_KEEP_DATA_PASS and
CURTIN_VMTEST_DATA_FAIL.

Add test_vmtest.py that contains Psuedo tests that act like the vmtests,
but run quickly. They are useful for testing the setUpClass and the test
harness itself. They will pass and not do really anything. To enable them
to fail and exercise that portion of the test harness, set the environment
variable CURTIN_VMTEST_DEBUG_ALLOW_FAIL=1.

Finally add documentation for all environment variables used by vmtest
to doc/devel/README-vmtest.txt.

314. By Scott Moser on 2015-11-20

debian/control: do not list e2fsprogs

e2fsprogs is essential and thus we do not need an explicit
depends per lintian-info depends-on-essential-package-without-using-version.

313. By Scott Moser on 2015-11-19

Rename vmtest test class names to match module.

312. By Scott Moser on 2015-11-19

Modify how vmtests checks if a curtin install was successful.

1. we missed finding failed installs on precise/trusty due to non-systemd
   output. systemd prepends non-pid-1 process output to console with the
   calling process, so we had 'cloud-init[.*]', however on pre-systemd
   systems, that's not present. Fix this by dropping the cloud-init
   portion of the regular expression

2. Add in additional error messages we've seen during debugging of test
   cases

3. Modify the check to first see if we can find curtin's successful
   install message; if that's not found, then look for common errors.

311. By Scott Moser on 2015-11-19

use 'smtar' for extracting tarballs.

smtar allows us to not specify a compression type, but rather
have it be magically determined. This means that in the future
an .tar.xz or .tar.bz2 or .tar can be used as input.

310. By Scott Moser on 2015-11-19

fix curtin.deps.install main

running 'python -m curtin.deps.install'
shows the mismatch between what was in main in curtin/deps/install.py
and in curtin.deps.install_deps.

There isnt any code that currently uses this function, but its likely
we will use in the future, and is a nice way to get dependencies installed.

309. By Scott Moser on 2015-11-18

fix pack_install

pack_install's command was ending up with a list in it.
That would get passed through to subp and fail.

308. By Scott Moser on 2015-11-18

fix errors reported by tox, rename a test

white space issues and a test named
  TrustTestRaid5Bcache
rather than
  TrustyTestRaid5Bcache

307. By Scott Moser on 2015-11-18

tools/launch, tools/xkvm: specify format on disk images

newer versions of qemu complain about disks that do not have
a format= parameter on them. Worse, that can cause serious
issues for an installer as qemu prints messages like:

WARNING: Image format was not specified for <disk> and probing guessed raw.
    Automatically detecting the format is dangerous for raw images, write
    operations on block 0 will be restricted.
    Specify the 'raw' format explicitly to remove the restrictions.

clearly if we can't write to block 0, then we may have issues formatting
disks and such. Wily and later give these errors.