From 5adee495c1a705a71ce67ffacf8545d0d2dcf779 Mon Sep 17 00:00:00 2001 From: sergio-j-cazzolato Date: Fri, 22 Jun 2018 18:09:50 -0300 Subject: Changes on how journalctl logs are managed Changes introduced New retry method which is intended to replace the retry mechanisms used in the tests waiting for a match in the logs. Examples are: install-cache, catalog-update, snap-confine-from-core, etc New method to check if snapd state is saved Fix shellcheck issue Start cursor after all the snaps from the previous tests were removed Check journal for snapd-reexec test, due to this error: https://paste.ubuntu.com/p/YwRP639VZn/ Restart journalctl to avoid messages comming late Some logs from previous test are being stored after the new marker is set. This is an example: https://api.travis- ci.org/v3/job/395465568/log.txt --- tests/unit/spread-shellcheck/can-fail | 1 - 1 file changed, 1 deletion(-) (limited to 'tests/unit') diff --git a/tests/unit/spread-shellcheck/can-fail b/tests/unit/spread-shellcheck/can-fail index fa8adb4f5c..4e1e4b14d2 100644 --- a/tests/unit/spread-shellcheck/can-fail +++ b/tests/unit/spread-shellcheck/can-fail @@ -80,7 +80,6 @@ tests/main/snap-advise-command/task.yaml tests/main/snap-auto-import-asserts-spools/task.yaml tests/main/snap-auto-import-asserts/task.yaml tests/main/snap-auto-mount/task.yaml -tests/main/snap-confine-from-core/task.yaml tests/main/snap-confine-privs/task.yaml tests/main/snap-confine/task.yaml tests/main/snap-connect/task.yaml -- cgit v1.2.3