kubuntu-council team mailing list archive
-
kubuntu-council team
-
Mailing list archive
-
Message #01168
[Merge] ~hyask/ubuntu-manual-tests:skia/cleanup_base_test into ubuntu-manual-tests:main
Skia has proposed merging ~hyask/ubuntu-manual-tests:skia/cleanup_base_test into ubuntu-manual-tests:main.
Commit message:
Add an optional cleaning step for chroot test
As these tests are not performed in a VM, and do some `mount --bind` of
the system's `dev`, `dev/pts`, `proc`, `sys`, an optional cleanup step
reminding the tester that there is some `umount` to do before `rm` is a
**very good idea**. Believe me, I've been there, and restoring `/dev` by
hand is not funny :-)
Requested reviews:
Ubuntu Testcase Admins (ubuntu-testcase)
For more details, see:
https://code.launchpad.net/~hyask/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/460936
--
Your team Ubuntu Testcase Admins is requested to review the proposed merge of ~hyask/ubuntu-manual-tests:skia/cleanup_base_test into ubuntu-manual-tests:main.
diff --git a/testcases/image/1318_Ubuntu Core Image Smoke Test b/testcases/image/1318_Ubuntu Core Image Smoke Test
index e55cc54..287b8ed 100644
--- a/testcases/image/1318_Ubuntu Core Image Smoke Test
+++ b/testcases/image/1318_Ubuntu Core Image Smoke Test
@@ -7,6 +7,7 @@ This testcase is intended to confirm the base chroot tarball is in proper workin
<dt>sudo cp /etc/resolv.conf base/etc/</dt>
<dt>sudo chroot base</dt>
<dt>apt update; apt install (some package)</dt>
+ <dt>optional cleanup after exit from the chroot: for m in dev/pts dev sys proc; do sudo umount base/$m; done; sudo rm base -rf</dt>
</dl>
<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong>
Follow ups