* Allow run failed tests on google-nested backend
This change is to allow running just the failed tests for google-nested
backend when the "Run failed" tag is set
* Make sure no new lines in results
* fix core22-basic to deal with recovery-keys change
* filter by backend to make sure external subtests are not included
* Fix core22-basic disabling recovery keys checks
* Fix recovery keys for core20-basic test now
* Update the key for nested cache
It's --show-keys, so the test was not really exercising the API operation as a
non-root user.
Signed-off-by: Maciej Borzecki <maciej.zenon.borzecki@canonical.com>
The change includes:
. Many functions added to tests.nested tool
. is-nested
. get
. boot-id
. secboot-sign
. Restructured the tests.nested tool command to simplify the cli
. exec
. vm (before was start-vm, stop-vm, and remove-vm)
The tests were update to use the tests.nested tool instead of the
nested.sh helper.
Next step is to reorganize the helper in 2 parts.
* devicestate: add support to save timings from install mode
Using a quick and not super nice way to store debug timings of
the install to the ubuntu-data partition.
* devicestate: rework timing log writing (thanks to Samuele)
* devicestate: rework because we can not call into snapd when snapd tries to reboot
* devicestate: improve unit test
* devicestate: snap debug timings --ensure=seed needs to run on its own
* devicestate: write the logs *after* the timings so that any failure from the timing writing is captured
* devicestate: fix comment
* tests: remove silly debug output
* tests: test install-timings.txt.gz more
* devicestate: add extra \n after each debug change output
* devicestate: move state unlock into writeTimings() and skip the "seed" change, we get the info via "snap debug timings --ensure=seed"
* devicestate: add clear information what is happening in writeTimings (thanks to Maciej)
* devicestate: update test to latest code changes
* tests: remove stray newline
This change includes:
. a new nested_retry command for nested tests
. tests updates to start using the new command intead of a loop
. replaced the existent retry functions using the new retry command
The change updates the layout of the tests following a proposed order
which should make the test easier to read and understand
The proposed order is:
summary
details
backends
systems
manual
priority
warn-timeout
kill-timeout
environment
prepare
restore
debug
execute
This change includes:
. core20 and core nested suites are unified into core suite. This
avoids tests duplication
. Now the tpm, secboot and kvm variables have defaults which are used
through functions defined in nested.sh
. By default the uc20 is build with secboot and tpm enabled.
. By detauld uc16 and uc18 are not using neither secboot nor tpm
. By default kvm is always used
. To define a different behaviour, the test needs to define the
variable in its environment.
