0s autopkgtest [09:13:06]: starting date and time: 2025-01-18 09:13:06+0000 0s autopkgtest [09:13:06]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [09:13:06]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.2ji7i6q_/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:tomb --apt-upgrade tomb --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=tomb/2.11+dfsg-2 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-arm64-40.secgroup --name adt-plucky-arm64-tomb-20250118-091306-juju-7f2275-prod-proposed-migration-environment-20-9c26dd8d-3df4-4fb9-879a-f40f63034bc8 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-proposed-migration -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 151s autopkgtest [09:15:37]: testbed dpkg architecture: arm64 152s autopkgtest [09:15:38]: testbed apt version: 2.9.18 152s autopkgtest [09:15:38]: @@@@@@@@@@@@@@@@@@@@ test bed setup 152s autopkgtest [09:15:38]: testbed release detected to be: None 153s autopkgtest [09:15:39]: updating testbed package index (apt update) 153s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 153s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 153s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 153s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 154s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [156 kB] 154s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 154s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [823 kB] 154s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.6 kB] 154s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [285 kB] 154s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [57.8 kB] 154s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [963 kB] 154s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [10.5 kB] 154s Fetched 2393 kB in 1s (2470 kB/s) 155s Reading package lists... 156s Reading package lists... 156s Building dependency tree... 156s Reading state information... 156s Calculating upgrade... 157s The following packages will be upgraded: 157s apport apport-core-dump-handler python3-apport python3-problem-report 157s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 157s Need to get 220 kB of archives. 157s After this operation, 0 B of additional disk space will be used. 157s Get:1 http://ftpmaster.internal/ubuntu plucky/main arm64 python3-problem-report all 2.31.0-0ubuntu3 [25.3 kB] 157s Get:2 http://ftpmaster.internal/ubuntu plucky/main arm64 python3-apport all 2.31.0-0ubuntu3 [93.1 kB] 157s Get:3 http://ftpmaster.internal/ubuntu plucky/main arm64 apport-core-dump-handler all 2.31.0-0ubuntu3 [18.3 kB] 157s Get:4 http://ftpmaster.internal/ubuntu plucky/main arm64 apport all 2.31.0-0ubuntu3 [83.0 kB] 158s Fetched 220 kB in 0s (464 kB/s) 158s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 80201 files and directories currently installed.) 158s Preparing to unpack .../python3-problem-report_2.31.0-0ubuntu3_all.deb ... 158s Unpacking python3-problem-report (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 158s Preparing to unpack .../python3-apport_2.31.0-0ubuntu3_all.deb ... 158s Unpacking python3-apport (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 158s Preparing to unpack .../apport-core-dump-handler_2.31.0-0ubuntu3_all.deb ... 158s Unpacking apport-core-dump-handler (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 159s Preparing to unpack .../apport_2.31.0-0ubuntu3_all.deb ... 159s Unpacking apport (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 159s Setting up python3-problem-report (2.31.0-0ubuntu3) ... 159s Setting up python3-apport (2.31.0-0ubuntu3) ... 159s Setting up apport-core-dump-handler (2.31.0-0ubuntu3) ... 160s Setting up apport (2.31.0-0ubuntu3) ... 161s apport-autoreport.service is a disabled or a static unit not running, not starting it. 161s Processing triggers for man-db (2.13.0-1) ... 162s Reading package lists... 162s Building dependency tree... 162s Reading state information... 164s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 164s autopkgtest [09:15:50]: upgrading testbed (apt dist-upgrade and autopurge) 164s Reading package lists... 165s Building dependency tree... 165s Reading state information... 166s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 167s Starting 2 pkgProblemResolver with broken count: 0 167s Done 168s Entering ResolveByKeep 169s 169s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 169s Reading package lists... 170s Building dependency tree... 170s Reading state information... 170s Starting pkgProblemResolver with broken count: 0 170s Starting 2 pkgProblemResolver with broken count: 0 170s Done 172s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 172s autopkgtest [09:15:58]: rebooting testbed after setup commands that affected boot 195s autopkgtest [09:16:21]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 14:19:41 UTC 2024 197s autopkgtest [09:16:23]: @@@@@@@@@@@@@@@@@@@@ apt-source tomb 200s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/universe tomb 2.11+dfsg-2 (dsc) [2050 B] 200s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/universe tomb 2.11+dfsg-2 (tar) [1262 kB] 200s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/universe tomb 2.11+dfsg-2 (diff) [16.2 kB] 200s gpgv: Signature made Fri Jan 17 21:06:39 2025 UTC 200s gpgv: using RSA key 3DF5E8AA43FC9FDFD086F195ADF50EDAF8ADD585 200s gpgv: issuer "sge@debian.org" 200s gpgv: Can't check signature: No public key 200s dpkg-source: warning: cannot verify inline signature for ./tomb_2.11+dfsg-2.dsc: no acceptable signature found 200s autopkgtest [09:16:26]: testing package tomb version 2.11+dfsg-2 200s autopkgtest [09:16:26]: build not needed 201s autopkgtest [09:16:27]: test create-and-use-a-tomb-with-sudo: preparing testbed 201s Reading package lists... 202s Building dependency tree... 202s Reading state information... 202s Starting pkgProblemResolver with broken count: 0 202s Starting 2 pkgProblemResolver with broken count: 0 202s Done 203s The following NEW packages will be installed: 203s argon2 tomb zsh zsh-common 203s 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. 203s Need to get 5079 kB of archives. 203s After this operation, 21.3 MB of additional disk space will be used. 203s Get:1 http://ftpmaster.internal/ubuntu plucky/universe arm64 argon2 arm64 0~20190702+dfsg-4build1 [22.8 kB] 203s Get:2 http://ftpmaster.internal/ubuntu plucky/main arm64 zsh-common all 5.9-6ubuntu3 [4170 kB] 203s Get:3 http://ftpmaster.internal/ubuntu plucky/main arm64 zsh arm64 5.9-6ubuntu3 [807 kB] 203s Get:4 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 tomb arm64 2.11+dfsg-2 [79.7 kB] 204s Fetched 5079 kB in 1s (6744 kB/s) 204s Selecting previously unselected package argon2. 204s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 80201 files and directories currently installed.) 204s Preparing to unpack .../argon2_0~20190702+dfsg-4build1_arm64.deb ... 204s Unpacking argon2 (0~20190702+dfsg-4build1) ... 204s Selecting previously unselected package zsh-common. 204s Preparing to unpack .../zsh-common_5.9-6ubuntu3_all.deb ... 204s Unpacking zsh-common (5.9-6ubuntu3) ... 204s Selecting previously unselected package zsh. 205s Preparing to unpack .../zsh_5.9-6ubuntu3_arm64.deb ... 205s Unpacking zsh (5.9-6ubuntu3) ... 205s Selecting previously unselected package tomb. 205s Preparing to unpack .../tomb_2.11+dfsg-2_arm64.deb ... 205s Unpacking tomb (2.11+dfsg-2) ... 205s Setting up argon2 (0~20190702+dfsg-4build1) ... 205s Setting up zsh-common (5.9-6ubuntu3) ... 205s Setting up zsh (5.9-6ubuntu3) ... 205s Setting up tomb (2.11+dfsg-2) ... 205s Processing triggers for debianutils (5.21) ... 205s Processing triggers for man-db (2.13.0-1) ... 206s autopkgtest [09:16:32]: test create-and-use-a-tomb-with-sudo: [----------------------- 207s ~~ Create a file to hold an encrypted file system ... 207s tomb . Commanded to dig tomb 207s tomb (*) Creating a new tomb in test.tomb 207s tomb . Generating test.tomb of 20MiB 207s 20+0 records in 207s 20+0 records out 207s 20971520 bytes (21 MB, 20 MiB) copied, 0.0698534 s, 300 MB/s 207s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:16 test.tomb 207s tomb (*) Done digging test.tomb 207s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 207s tomb . tomb forge test.tomb.key 207s tomb . tomb lock test.tomb -k test.tomb.key 207s ~~ Create a pbkdf2 key file ... 207s tomb . Commanded to forge key pbkdf2-test.key with cipher algorithm AES256 207s tomb . Using KDF to protect the key password (1 rounds) 207s tomb [W] This operation takes time. Keep using this computer on other tasks. 207s tomb [W] Once done you will be asked to choose a password for your tomb. 207s tomb [W] To make it faster you can move the mouse around. 207s tomb [W] If you are on a server, you can use an Entropy Generation Daemon. 207s 512+0 records in 207s 512+0 records out 207s 512 bytes copied, 0.00044476 s, 1.2 MB/s 207s tomb (*) Choose the password of your key: pbkdf2-test.key 207s tomb . (You can also change it later using 'tomb passwd'.) 207s tomb (*) Using KDF, iteration time: 1000000 207s tomb . generating salt 207s tomb . calculating iterations 208s tomb . encoding the password 210s tomb . Key is valid. 210s tomb . Done forging pbkdf2-test.key 210s tomb (*) Your key is ready: 210s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:16 pbkdf2-test.key 210s ~~ Create an argon2 key file ... 210s tomb . Commanded to forge key argon2-test.key with cipher algorithm AES256 210s tomb . Using KDF to protect the key password (1 rounds) 210s tomb [W] This operation takes time. Keep using this computer on other tasks. 210s tomb [W] Once done you will be asked to choose a password for your tomb. 210s tomb [W] To make it faster you can move the mouse around. 210s tomb [W] If you are on a server, you can use an Entropy Generation Daemon. 210s 512+0 records in 210s 512+0 records out 210s 512 bytes copied, 0.00059732 s, 857 kB/s 210s tomb (*) Choose the password of your key: argon2-test.key 210s tomb . (You can also change it later using 'tomb passwd'.) 210s tomb (*) Using KDF Argon2 210s tomb . memory used: 2^18 210s tomb . kdf salt: 9181bc34926a06c9790e9092bce7ee28ddc50818c1ac7f40fa78c3e25ffc9769 210s tomb . kdf iterations: 1 210s tomb . Key is valid. 210s tomb . Done forging argon2-test.key 210s tomb (*) Your key is ready: 210s -rw------- 1 ubuntu ubuntu 944 Jan 18 09:16 argon2-test.key 211s ~~ Cloak a key file ... 211s tomb . Key is valid. 211s tomb (*) Encoding key argon2-test.key using cipher /usr/share/doc/tomb/examples/cloak-ciphers/emoji 211s tomb (*) Tomb key encoded succesfully 211s ~~ Uncloak and verify a key file ... 211s tomb (*) Key succesfully uncloaked to uncloaked.key. 211s ~~ Testing ext4 file system using a pbkdf2 key ... 211s tomb . Commanded to dig tomb 211s tomb (*) Creating a new tomb in test.tomb 211s tomb . Generating test.tomb of 20MiB 211s 20+0 records in 211s 20+0 records out 211s 20971520 bytes (21 MB, 20 MiB) copied, 0.0680464 s, 308 MB/s 211s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:16 test.tomb 211s tomb (*) Done digging test.tomb 211s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 211s tomb . tomb forge test.tomb.key 211s tomb . tomb lock test.tomb -k test.tomb.key 211s tomb . File is not yet a tomb: test.tomb 211s tomb . Valid tomb file found: test.tomb 211s tomb . Commanded to lock tomb test.tomb 211s tomb (*) Selected filesystem type ext4. 211s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 211s tomb . Fine, this tomb seems empty. 211s tomb . Key is valid. 211s tomb . Locking using cipher: aes-xts-plain64 211s tomb . A password is required to use key pbkdf2-test.key 211s tomb . Unlocking KDF key protection (pbkdf2sha1) 212s tomb . Password OK. 212s tomb (*) Locking test.tomb with pbkdf2-test.key 212s tomb . Formatting Luks mapped device. 220s tomb . Formatting your Tomb with ext4 filesystem. 220s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 220s tomb (*) Your tomb is ready in test.tomb and secured with key pbkdf2-test.key 220s tomb . Commanded to open tomb test.tomb 220s tomb . Valid tomb file found: test.tomb 220s tomb . Key is valid. 220s tomb . Mountpoint not specified, using default: /media/test 220s tomb (*) Opening test on /media/test 220s tomb . This tomb is a valid LUKS encrypted device. 220s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 220s tomb . A password is required to use key pbkdf2-test.key 220s tomb . Unlocking KDF key protection (pbkdf2sha1) 221s tomb . Password OK. 223s tomb (*) Success unlocking tomb test 223s tomb . Filesystem detected: ext4 223s tomb . Checking filesystem via /dev/loop0 223s fsck from util-linux 2.40.2 223s test: clean, 12/4608 files, 1356/4608 blocks 223s tomb (*) Success opening test.tomb on /media/test 223s ~~ Copying some data into the opened tomb ... 223s ~~ Opened tomb's content is ... 223s total 44 223s drwxr-xr-x 3 ubuntu ubuntu 4096 Jan 18 09:16 . 223s drwxr-xr-x 3 root root 4096 Jan 18 09:16 .. 223s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:16 .host 223s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:16 .last 223s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:16 .uid 223s -rw------- 1 ubuntu ubuntu 944 Jan 18 09:16 argon2-test.key 223s drwx------ 2 ubuntu ubuntu 16384 Jan 18 09:16 lost+found 223s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:16 pbkdf2-test.key 223s tomb . Closing tomb [test] mounted on /media/test 223s tomb (*) Tomb [test] closed: your bones will rest in peace. 223s ~~ Testing ext4 file system using a argon2 key ... 223s tomb . Commanded to dig tomb 223s tomb (*) Creating a new tomb in test.tomb 223s tomb . Generating test.tomb of 20MiB 223s 20+0 records in 223s 20+0 records out 223s 20971520 bytes (21 MB, 20 MiB) copied, 0.0697726 s, 301 MB/s 223s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:16 test.tomb 223s tomb (*) Done digging test.tomb 223s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 223s tomb . tomb forge test.tomb.key 223s tomb . tomb lock test.tomb -k test.tomb.key 223s tomb . File is not yet a tomb: test.tomb 223s tomb . Valid tomb file found: test.tomb 223s tomb . Commanded to lock tomb test.tomb 223s tomb (*) Selected filesystem type ext4. 224s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 224s tomb . Fine, this tomb seems empty. 224s tomb . Key is valid. 224s tomb . Locking using cipher: aes-xts-plain64 224s tomb . A password is required to use key argon2-test.key 224s tomb . Unlocking KDF key protection (argon2) 224s tomb . Password OK. 224s tomb (*) Locking test.tomb with argon2-test.key 224s tomb . Formatting Luks mapped device. 231s tomb . Formatting your Tomb with ext4 filesystem. 232s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 232s tomb (*) Your tomb is ready in test.tomb and secured with key argon2-test.key 232s tomb . Commanded to open tomb test.tomb 232s tomb . Valid tomb file found: test.tomb 232s tomb . Key is valid. 232s tomb . Mountpoint not specified, using default: /media/test 232s tomb (*) Opening test on /media/test 232s tomb . This tomb is a valid LUKS encrypted device. 232s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 232s tomb . A password is required to use key argon2-test.key 232s tomb . Unlocking KDF key protection (argon2) 232s tomb . Password OK. 234s tomb (*) Success unlocking tomb test 234s tomb . Filesystem detected: ext4 234s tomb . Checking filesystem via /dev/loop0 234s fsck from util-linux 2.40.2 234s test: clean, 12/4608 files, 1356/4608 blocks 234s tomb (*) Success opening test.tomb on /media/test 235s ~~ Copying some data into the opened tomb ... 235s ~~ Opened tomb's content is ... 235s total 44 235s drwxr-xr-x 3 ubuntu ubuntu 4096 Jan 18 09:17 . 235s drwxr-xr-x 3 root root 4096 Jan 18 09:17 .. 235s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:17 .host 235s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:17 .last 235s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:17 .uid 235s -rw------- 1 ubuntu ubuntu 944 Jan 18 09:16 argon2-test.key 235s drwx------ 2 ubuntu ubuntu 16384 Jan 18 09:16 lost+found 235s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:16 pbkdf2-test.key 235s tomb . Closing tomb [test] mounted on /media/test 235s tomb (*) Tomb [test] closed: your bones will rest in peace. 235s ~~ Testing btrfs file system using a pbkdf2 key ... 235s tomb . Commanded to dig tomb 235s tomb (*) Creating a new tomb in test.tomb 235s tomb . Generating test.tomb of 115MiB 235s 115+0 records in 235s 115+0 records out 235s 120586240 bytes (121 MB, 115 MiB) copied, 0.454429 s, 265 MB/s 235s -rw------- 1 ubuntu ubuntu 115M Jan 18 09:17 test.tomb 235s tomb (*) Done digging test.tomb 235s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 235s tomb . tomb forge test.tomb.key 235s tomb . tomb lock test.tomb -k test.tomb.key 235s tomb . File is not yet a tomb: test.tomb 235s tomb . Valid tomb file found: test.tomb 235s tomb . Commanded to lock tomb test.tomb 235s tomb (*) Selected filesystem type btrfs. 235s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 235s tomb . Fine, this tomb seems empty. 235s tomb . Key is valid. 235s tomb . Locking using cipher: aes-xts-plain64 235s tomb . A password is required to use key pbkdf2-test.key 235s tomb . Unlocking KDF key protection (pbkdf2sha1) 236s tomb . Password OK. 236s tomb (*) Locking test.tomb with pbkdf2-test.key 236s tomb . Formatting Luks mapped device. 244s tomb . Formatting your Tomb with btrfs filesystem. 244s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 244s tomb (*) Your tomb is ready in test.tomb and secured with key pbkdf2-test.key 244s tomb . Commanded to open tomb test.tomb 244s tomb . Valid tomb file found: test.tomb 244s tomb . Key is valid. 244s tomb . Mountpoint not specified, using default: /media/test 244s tomb (*) Opening test on /media/test 244s tomb . This tomb is a valid LUKS encrypted device. 244s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 244s tomb . A password is required to use key pbkdf2-test.key 244s tomb . Unlocking KDF key protection (pbkdf2sha1) 245s tomb . Password OK. 247s tomb (*) Success unlocking tomb test 247s tomb . Filesystem detected: btrfs 247s tomb . Checking filesystem via /dev/loop0 247s [1/7] checking root items 247s [2/7] checking extents 247s [3/7] checking free space tree 247s [4/7] checking fs roots 247s [5/7] checking only csums items (without verifying data) 247s [6/7] checking root refs 247s [7/7] checking quota groups skipped (not enabled on this FS) 247s Opening filesystem to check... 247s Checking filesystem on /dev/mapper/tomb.test.66437b4bb4d34fd221a7d95ca41b5e8d27eb8741bd41ae443897c5d0f7d51aa7.loop0 247s UUID: 36df676d-c70d-41a9-8ed8-20738c01f22b 247s found 147456 bytes used, no error found 247s total csum bytes: 0 247s total tree bytes: 147456 247s total fs tree bytes: 32768 247s total extent tree bytes: 16384 247s btree space waste bytes: 140595 247s file data blocks allocated: 0 247s referenced 0 247s tomb (*) Success opening test.tomb on /media/test 248s ~~ Copying some data into the opened tomb ... 248s ~~ Opened tomb's content is ... 248s total 40 248s drwxr-xr-x 1 ubuntu ubuntu 88 Jan 18 09:17 . 248s drwxr-xr-x 3 root root 4096 Jan 18 09:17 .. 248s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:17 .host 248s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:17 .last 248s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:17 .uid 248s -rw------- 1 ubuntu ubuntu 944 Jan 18 09:16 argon2-test.key 248s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:16 pbkdf2-test.key 248s tomb . Closing tomb [test] mounted on /media/test 248s tomb (*) Tomb [test] closed: your bones will rest in peace. 248s ~~ Testing btrfsmixedmode file system using a argon2 key ... 248s tomb . Commanded to dig tomb 248s tomb (*) Creating a new tomb in test.tomb 248s tomb . Generating test.tomb of 20MiB 248s 20+0 records in 248s 20+0 records out 248s 20971520 bytes (21 MB, 20 MiB) copied, 0.0687642 s, 305 MB/s 248s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:17 test.tomb 248s tomb (*) Done digging test.tomb 248s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 248s tomb . tomb forge test.tomb.key 248s tomb . tomb lock test.tomb -k test.tomb.key 248s tomb . File is not yet a tomb: test.tomb 248s tomb . Valid tomb file found: test.tomb 248s tomb . Commanded to lock tomb test.tomb 248s tomb (*) Selected filesystem type btrfsmixedmode. 248s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 248s tomb . Fine, this tomb seems empty. 248s tomb . Key is valid. 248s tomb . Locking using cipher: aes-xts-plain64 248s tomb . A password is required to use key argon2-test.key 248s tomb . Unlocking KDF key protection (argon2) 248s tomb . Password OK. 248s tomb (*) Locking test.tomb with argon2-test.key 248s tomb . Formatting Luks mapped device. 256s tomb . Formatting your Tomb with btrfsmixedmode filesystem. 256s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 256s tomb (*) Your tomb is ready in test.tomb and secured with key argon2-test.key 256s tomb . Commanded to open tomb test.tomb 256s tomb . Valid tomb file found: test.tomb 256s tomb . Key is valid. 256s tomb . Mountpoint not specified, using default: /media/test 256s tomb (*) Opening test on /media/test 256s tomb . This tomb is a valid LUKS encrypted device. 256s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 256s tomb . A password is required to use key argon2-test.key 256s tomb . Unlocking KDF key protection (argon2) 257s tomb . Password OK. 259s tomb (*) Success unlocking tomb test 259s tomb . Filesystem detected: btrfs 259s tomb . Checking filesystem via /dev/loop0 259s [1/7] checking root items 259s [2/7] checking extents 259s [3/7] checking free space tree 259s [4/7] checking fs roots 259s [5/7] checking only csums items (without verifying data) 259s [6/7] checking root refs 259s [7/7] checking quota groups skipped (not enabled on this FS) 259s Opening filesystem to check... 259s Checking filesystem on /dev/mapper/tomb.test.66437b4bb4d34fd221a7d95ca41b5e8d27eb8741bd41ae443897c5d0f7d51aa7.loop0 259s UUID: 01f33496-220d-4dcb-a353-0db726348cc4 259s found 36864 bytes used, no error found 259s total csum bytes: 0 259s total tree bytes: 36864 259s total fs tree bytes: 8192 259s total extent tree bytes: 4096 259s btree space waste bytes: 30304 259s file data blocks allocated: 0 259s referenced 0 259s tomb (*) Success opening test.tomb on /media/test 259s ~~ Copying some data into the opened tomb ... 259s ~~ Opened tomb's content is ... 259s total 28 259s drwxr-xr-x 1 ubuntu ubuntu 88 Jan 18 09:17 . 259s drwxr-xr-x 3 root root 4096 Jan 18 09:17 .. 259s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:17 .host 259s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:17 .last 259s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:17 .uid 259s -rw------- 1 ubuntu ubuntu 944 Jan 18 09:16 argon2-test.key 259s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:16 pbkdf2-test.key 259s tomb . Closing tomb [test] mounted on /media/test 259s tomb (*) Tomb [test] closed: your bones will rest in peace. 259s autopkgtest [09:17:25]: test create-and-use-a-tomb-with-sudo: -----------------------] 260s create-and-use-a-tomb-with-sudo PASS 260s autopkgtest [09:17:26]: test create-and-use-a-tomb-with-sudo: - - - - - - - - - - results - - - - - - - - - - 260s autopkgtest [09:17:26]: test create-and-use-a-tomb-with-doas: preparing testbed 385s autopkgtest [09:19:31]: testbed dpkg architecture: arm64 385s autopkgtest [09:19:31]: testbed apt version: 2.9.18 385s autopkgtest [09:19:31]: @@@@@@@@@@@@@@@@@@@@ test bed setup 385s autopkgtest [09:19:31]: testbed release detected to be: plucky 386s autopkgtest [09:19:32]: updating testbed package index (apt update) 386s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 387s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 387s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 387s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 387s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 387s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [156 kB] 387s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.6 kB] 387s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [823 kB] 387s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [285 kB] 387s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [57.8 kB] 387s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [963 kB] 387s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [10.5 kB] 387s Fetched 2393 kB in 1s (2506 kB/s) 388s Reading package lists... 389s Reading package lists... 389s Building dependency tree... 389s Reading state information... 389s Calculating upgrade... 390s The following packages will be upgraded: 390s apport apport-core-dump-handler python3-apport python3-problem-report 390s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 390s Need to get 220 kB of archives. 390s After this operation, 0 B of additional disk space will be used. 390s Get:1 http://ftpmaster.internal/ubuntu plucky/main arm64 python3-problem-report all 2.31.0-0ubuntu3 [25.3 kB] 390s Get:2 http://ftpmaster.internal/ubuntu plucky/main arm64 python3-apport all 2.31.0-0ubuntu3 [93.1 kB] 390s Get:3 http://ftpmaster.internal/ubuntu plucky/main arm64 apport-core-dump-handler all 2.31.0-0ubuntu3 [18.3 kB] 390s Get:4 http://ftpmaster.internal/ubuntu plucky/main arm64 apport all 2.31.0-0ubuntu3 [83.0 kB] 391s Fetched 220 kB in 0s (529 kB/s) 391s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 80201 files and directories currently installed.) 391s Preparing to unpack .../python3-problem-report_2.31.0-0ubuntu3_all.deb ... 391s Unpacking python3-problem-report (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 391s Preparing to unpack .../python3-apport_2.31.0-0ubuntu3_all.deb ... 391s Unpacking python3-apport (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 391s Preparing to unpack .../apport-core-dump-handler_2.31.0-0ubuntu3_all.deb ... 391s Unpacking apport-core-dump-handler (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 391s Preparing to unpack .../apport_2.31.0-0ubuntu3_all.deb ... 391s Unpacking apport (2.31.0-0ubuntu3) over (2.31.0-0ubuntu2) ... 391s Setting up python3-problem-report (2.31.0-0ubuntu3) ... 391s Setting up python3-apport (2.31.0-0ubuntu3) ... 392s Setting up apport-core-dump-handler (2.31.0-0ubuntu3) ... 393s Setting up apport (2.31.0-0ubuntu3) ... 393s apport-autoreport.service is a disabled or a static unit not running, not starting it. 393s Processing triggers for man-db (2.13.0-1) ... 394s Reading package lists... 394s Building dependency tree... 394s Reading state information... 395s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 395s autopkgtest [09:19:41]: upgrading testbed (apt dist-upgrade and autopurge) 395s Reading package lists... 395s Building dependency tree... 395s Reading state information... 396s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 396s Starting 2 pkgProblemResolver with broken count: 0 396s Done 397s Entering ResolveByKeep 397s 397s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 397s Reading package lists... 398s Building dependency tree... 398s Reading state information... 398s Starting pkgProblemResolver with broken count: 0 398s Starting 2 pkgProblemResolver with broken count: 0 398s Done 399s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 399s autopkgtest [09:19:45]: rebooting testbed after setup commands that affected boot 425s Reading package lists... 425s Building dependency tree... 425s Reading state information... 426s Starting pkgProblemResolver with broken count: 0 426s Starting 2 pkgProblemResolver with broken count: 0 426s Done 428s The following NEW packages will be installed: 428s argon2 doas opendoas tomb zsh zsh-common 428s 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. 428s Need to get 5105 kB of archives. 428s After this operation, 21.4 MB of additional disk space will be used. 428s Get:1 http://ftpmaster.internal/ubuntu plucky/universe arm64 argon2 arm64 0~20190702+dfsg-4build1 [22.8 kB] 429s Get:2 http://ftpmaster.internal/ubuntu plucky/universe arm64 opendoas arm64 6.8.2-1 [22.7 kB] 429s Get:3 http://ftpmaster.internal/ubuntu plucky/universe arm64 doas arm64 6.8.2-1 [2772 B] 429s Get:4 http://ftpmaster.internal/ubuntu plucky/main arm64 zsh-common all 5.9-6ubuntu3 [4170 kB] 429s Get:5 http://ftpmaster.internal/ubuntu plucky/main arm64 zsh arm64 5.9-6ubuntu3 [807 kB] 429s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 tomb arm64 2.11+dfsg-2 [79.7 kB] 430s Fetched 5105 kB in 1s (6407 kB/s) 430s Selecting previously unselected package argon2. 430s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 80201 files and directories currently installed.) 430s Preparing to unpack .../0-argon2_0~20190702+dfsg-4build1_arm64.deb ... 430s Unpacking argon2 (0~20190702+dfsg-4build1) ... 430s Selecting previously unselected package opendoas. 430s Preparing to unpack .../1-opendoas_6.8.2-1_arm64.deb ... 430s Unpacking opendoas (6.8.2-1) ... 430s Selecting previously unselected package doas. 430s Preparing to unpack .../2-doas_6.8.2-1_arm64.deb ... 430s Unpacking doas (6.8.2-1) ... 430s Selecting previously unselected package zsh-common. 430s Preparing to unpack .../3-zsh-common_5.9-6ubuntu3_all.deb ... 430s Unpacking zsh-common (5.9-6ubuntu3) ... 431s Selecting previously unselected package zsh. 431s Preparing to unpack .../4-zsh_5.9-6ubuntu3_arm64.deb ... 431s Unpacking zsh (5.9-6ubuntu3) ... 431s Selecting previously unselected package tomb. 431s Preparing to unpack .../5-tomb_2.11+dfsg-2_arm64.deb ... 431s Unpacking tomb (2.11+dfsg-2) ... 431s Setting up argon2 (0~20190702+dfsg-4build1) ... 431s Setting up zsh-common (5.9-6ubuntu3) ... 431s Setting up zsh (5.9-6ubuntu3) ... 431s Setting up opendoas (6.8.2-1) ... 431s Setting up tomb (2.11+dfsg-2) ... 431s Setting up doas (6.8.2-1) ... 431s Processing triggers for debianutils (5.21) ... 431s Processing triggers for man-db (2.13.0-1) ... 435s autopkgtest [09:20:21]: test create-and-use-a-tomb-with-doas: [----------------------- 435s ~~ Create a file to hold an encrypted file system ... 435s tomb . Commanded to dig tomb 435s tomb (*) Creating a new tomb in test.tomb 435s tomb . Generating test.tomb of 20MiB 435s 20+0 records in 435s 20+0 records out 435s 20971520 bytes (21 MB, 20 MiB) copied, 0.0897289 s, 234 MB/s 435s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:20 test.tomb 435s tomb (*) Done digging test.tomb 435s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 435s tomb . tomb forge test.tomb.key 435s tomb . tomb lock test.tomb -k test.tomb.key 435s ~~ Create a pbkdf2 key file ... 435s tomb . Commanded to forge key pbkdf2-test.key with cipher algorithm AES256 435s tomb . Using KDF to protect the key password (1 rounds) 435s tomb [W] This operation takes time. Keep using this computer on other tasks. 435s tomb [W] Once done you will be asked to choose a password for your tomb. 435s tomb [W] To make it faster you can move the mouse around. 435s tomb [W] If you are on a server, you can use an Entropy Generation Daemon. 435s 512+0 records in 435s 512+0 records out 435s 512 bytes copied, 0.00050676 s, 1.0 MB/s 435s tomb (*) Choose the password of your key: pbkdf2-test.key 435s tomb . (You can also change it later using 'tomb passwd'.) 435s tomb (*) Using KDF, iteration time: 1000000 435s tomb . generating salt 435s tomb . calculating iterations 436s tomb . encoding the password 438s tomb . Key is valid. 438s tomb . Done forging pbkdf2-test.key 438s tomb (*) Your key is ready: 438s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:20 pbkdf2-test.key 439s ~~ Create an argon2 key file ... 439s tomb . Commanded to forge key argon2-test.key with cipher algorithm AES256 439s tomb . Using KDF to protect the key password (1 rounds) 439s tomb [W] This operation takes time. Keep using this computer on other tasks. 439s tomb [W] Once done you will be asked to choose a password for your tomb. 439s tomb [W] To make it faster you can move the mouse around. 439s tomb [W] If you are on a server, you can use an Entropy Generation Daemon. 439s 512+0 records in 439s 512+0 records out 439s 512 bytes copied, 0.00109476 s, 468 kB/s 439s tomb (*) Choose the password of your key: argon2-test.key 439s tomb . (You can also change it later using 'tomb passwd'.) 439s tomb (*) Using KDF Argon2 439s tomb . memory used: 2^18 439s tomb . kdf salt: dbc4e430739b16f60f6e1aa15fdf046d187c16306e7a519bb7cd325550a9b079 439s tomb . kdf iterations: 1 439s tomb . Key is valid. 439s tomb . Done forging argon2-test.key 439s tomb (*) Your key is ready: 439s -rw------- 1 ubuntu ubuntu 940 Jan 18 09:20 argon2-test.key 440s ~~ Cloak a key file ... 440s tomb . Key is valid. 440s tomb (*) Encoding key argon2-test.key using cipher /usr/share/doc/tomb/examples/cloak-ciphers/emoji 440s tomb (*) Tomb key encoded succesfully 440s ~~ Uncloak and verify a key file ... 440s tomb (*) Key succesfully uncloaked to uncloaked.key. 440s ~~ Testing ext4 file system using a pbkdf2 key ... 440s tomb . Commanded to dig tomb 440s tomb (*) Creating a new tomb in test.tomb 440s tomb . Generating test.tomb of 20MiB 440s 20+0 records in 440s 20+0 records out 440s 20971520 bytes (21 MB, 20 MiB) copied, 0.082778 s, 253 MB/s 440s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:20 test.tomb 440s tomb (*) Done digging test.tomb 440s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 440s tomb . tomb forge test.tomb.key 440s tomb . tomb lock test.tomb -k test.tomb.key 440s tomb . File is not yet a tomb: test.tomb 440s tomb . Valid tomb file found: test.tomb 440s tomb . Commanded to lock tomb test.tomb 440s tomb (*) Selected filesystem type ext4. 440s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 440s tomb . Fine, this tomb seems empty. 440s tomb . Key is valid. 440s tomb . Locking using cipher: aes-xts-plain64 440s tomb . A password is required to use key pbkdf2-test.key 440s tomb . Unlocking KDF key protection (pbkdf2sha1) 442s tomb . Password OK. 442s tomb (*) Locking test.tomb with pbkdf2-test.key 442s tomb . Formatting Luks mapped device. 449s tomb . Formatting your Tomb with ext4 filesystem. 449s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 449s tomb (*) Your tomb is ready in test.tomb and secured with key pbkdf2-test.key 449s tomb . Commanded to open tomb test.tomb 449s tomb . Valid tomb file found: test.tomb 450s tomb . Key is valid. 450s tomb . Mountpoint not specified, using default: /media/test 450s tomb (*) Opening test on /media/test 450s tomb . This tomb is a valid LUKS encrypted device. 450s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 450s tomb . A password is required to use key pbkdf2-test.key 450s tomb . Unlocking KDF key protection (pbkdf2sha1) 451s tomb . Password OK. 453s tomb (*) Success unlocking tomb test 453s tomb . Filesystem detected: ext4 453s tomb . Checking filesystem via /dev/loop0 453s fsck from util-linux 2.40.2 453s test: clean, 12/4608 files, 1356/4608 blocks 453s tomb (*) Success opening test.tomb on /media/test 453s ~~ Copying some data into the opened tomb ... 453s ~~ Opened tomb's content is ... 453s total 44 453s drwxr-xr-x 3 ubuntu ubuntu 4096 Jan 18 09:20 . 453s drwxr-xr-x 3 root root 4096 Jan 18 09:20 .. 453s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:20 .host 453s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:20 .last 453s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:20 .uid 453s -rw------- 1 ubuntu ubuntu 940 Jan 18 09:20 argon2-test.key 453s drwx------ 2 ubuntu ubuntu 16384 Jan 18 09:20 lost+found 453s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:20 pbkdf2-test.key 453s tomb . Closing tomb [test] mounted on /media/test 454s tomb (*) Tomb [test] closed: your bones will rest in peace. 454s ~~ Testing ext4 file system using a argon2 key ... 454s tomb . Commanded to dig tomb 454s tomb (*) Creating a new tomb in test.tomb 454s tomb . Generating test.tomb of 20MiB 454s 20+0 records in 454s 20+0 records out 454s 20971520 bytes (21 MB, 20 MiB) copied, 0.0834439 s, 251 MB/s 454s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:20 test.tomb 454s tomb (*) Done digging test.tomb 454s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 454s tomb . tomb forge test.tomb.key 454s tomb . tomb lock test.tomb -k test.tomb.key 454s tomb . File is not yet a tomb: test.tomb 454s tomb . Valid tomb file found: test.tomb 454s tomb . Commanded to lock tomb test.tomb 454s tomb (*) Selected filesystem type ext4. 454s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 454s tomb . Fine, this tomb seems empty. 454s tomb . Key is valid. 454s tomb . Locking using cipher: aes-xts-plain64 454s tomb . A password is required to use key argon2-test.key 454s tomb . Unlocking KDF key protection (argon2) 455s tomb . Password OK. 455s tomb (*) Locking test.tomb with argon2-test.key 455s tomb . Formatting Luks mapped device. 462s tomb . Formatting your Tomb with ext4 filesystem. 462s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 462s tomb (*) Your tomb is ready in test.tomb and secured with key argon2-test.key 462s tomb . Commanded to open tomb test.tomb 462s tomb . Valid tomb file found: test.tomb 462s tomb . Key is valid. 462s tomb . Mountpoint not specified, using default: /media/test 462s tomb (*) Opening test on /media/test 462s tomb . This tomb is a valid LUKS encrypted device. 462s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 462s tomb . A password is required to use key argon2-test.key 462s tomb . Unlocking KDF key protection (argon2) 463s tomb . Password OK. 465s tomb (*) Success unlocking tomb test 465s tomb . Filesystem detected: ext4 465s tomb . Checking filesystem via /dev/loop0 465s fsck from util-linux 2.40.2 465s test: clean, 12/4608 files, 1356/4608 blocks 465s tomb (*) Success opening test.tomb on /media/test 465s ~~ Copying some data into the opened tomb ... 465s ~~ Opened tomb's content is ... 465s total 44 465s drwxr-xr-x 3 ubuntu ubuntu 4096 Jan 18 09:20 . 465s drwxr-xr-x 3 root root 4096 Jan 18 09:20 .. 465s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:20 .host 465s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:20 .last 465s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:20 .uid 465s -rw------- 1 ubuntu ubuntu 940 Jan 18 09:20 argon2-test.key 465s drwx------ 2 ubuntu ubuntu 16384 Jan 18 09:20 lost+found 465s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:20 pbkdf2-test.key 465s tomb . Closing tomb [test] mounted on /media/test 465s tomb (*) Tomb [test] closed: your bones will rest in peace. 465s ~~ Testing btrfs file system using a pbkdf2 key ... 465s tomb . Commanded to dig tomb 465s tomb (*) Creating a new tomb in test.tomb 465s tomb . Generating test.tomb of 115MiB 466s -rw------- 1 ubuntu ubuntu 115M Jan 18 09:20 test.tomb 466s 115+0 records in 466s 115+0 records out 466s 120586240 bytes (121 MB, 115 MiB) copied, 0.400173 s, 301 MB/s 466s tomb (*) Done digging test.tomb 466s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 466s tomb . tomb forge test.tomb.key 466s tomb . tomb lock test.tomb -k test.tomb.key 466s tomb . File is not yet a tomb: test.tomb 466s tomb . Valid tomb file found: test.tomb 466s tomb . Commanded to lock tomb test.tomb 466s tomb (*) Selected filesystem type btrfs. 466s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 466s tomb . Fine, this tomb seems empty. 466s tomb . Key is valid. 466s tomb . Locking using cipher: aes-xts-plain64 466s tomb . A password is required to use key pbkdf2-test.key 466s tomb . Unlocking KDF key protection (pbkdf2sha1) 467s tomb . Password OK. 467s tomb (*) Locking test.tomb with pbkdf2-test.key 467s tomb . Formatting Luks mapped device. 474s tomb . Formatting your Tomb with btrfs filesystem. 475s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 475s tomb (*) Your tomb is ready in test.tomb and secured with key pbkdf2-test.key 475s tomb . Commanded to open tomb test.tomb 475s tomb . Valid tomb file found: test.tomb 475s tomb . Key is valid. 475s tomb . Mountpoint not specified, using default: /media/test 475s tomb (*) Opening test on /media/test 475s tomb . This tomb is a valid LUKS encrypted device. 475s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 475s tomb . A password is required to use key pbkdf2-test.key 475s tomb . Unlocking KDF key protection (pbkdf2sha1) 476s tomb . Password OK. 478s tomb (*) Success unlocking tomb test 478s tomb . Filesystem detected: btrfs 478s tomb . Checking filesystem via /dev/loop0 478s [1/7] checking root items 478s [2/7] checking extents 478s [3/7] checking free space tree 478s [4/7] checking fs roots 478s [5/7] checking only csums items (without verifying data) 478s [6/7] checking root refs 478s Opening filesystem to check... 478s Checking filesystem on /dev/mapper/tomb.test.66437b4bb4d34fd221a7d95ca41b5e8d27eb8741bd41ae443897c5d0f7d51aa7.loop0 478s UUID: 2d60bc4c-5605-4f18-ab41-abc9f65d05d0 478s found 147456 bytes used, no error found 478s total csum bytes: 0 478s total tree bytes: 147456 478s total fs tree bytes: 32768 478s total extent tree bytes: 16384 478s btree space waste bytes: 140595 478s file data blocks allocated: 0 478s referenced 0 478s [7/7] checking quota groups skipped (not enabled on this FS) 478s tomb (*) Success opening test.tomb on /media/test 478s ~~ Copying some data into the opened tomb ... 478s ~~ Opened tomb's content is ... 478s total 40 478s drwxr-xr-x 1 ubuntu ubuntu 88 Jan 18 09:21 . 478s drwxr-xr-x 3 root root 4096 Jan 18 09:21 .. 478s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:21 .host 478s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:21 .last 478s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:21 .uid 478s -rw------- 1 ubuntu ubuntu 940 Jan 18 09:20 argon2-test.key 478s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:20 pbkdf2-test.key 478s tomb . Closing tomb [test] mounted on /media/test 479s tomb (*) Tomb [test] closed: your bones will rest in peace. 479s ~~ Testing btrfsmixedmode file system using a argon2 key ... 479s tomb . Commanded to dig tomb 479s tomb (*) Creating a new tomb in test.tomb 479s tomb . Generating test.tomb of 20MiB 479s 20+0 records in 479s 20+0 records out 479s 20971520 bytes (21 MB, 20 MiB) copied, 0.0845105 s, 248 MB/s 479s -rw------- 1 ubuntu ubuntu 20M Jan 18 09:21 test.tomb 479s tomb (*) Done digging test.tomb 479s tomb . Your tomb is not yet ready, you need to forge a key and lock it: 479s tomb . tomb forge test.tomb.key 479s tomb . tomb lock test.tomb -k test.tomb.key 479s tomb . File is not yet a tomb: test.tomb 479s tomb . Valid tomb file found: test.tomb 479s tomb . Commanded to lock tomb test.tomb 479s tomb (*) Selected filesystem type btrfsmixedmode. 479s tomb . Checking if the tomb is empty (we never step on somebody else's bones). 479s tomb . Fine, this tomb seems empty. 479s tomb . Key is valid. 479s tomb . Locking using cipher: aes-xts-plain64 479s tomb . A password is required to use key argon2-test.key 479s tomb . Unlocking KDF key protection (argon2) 480s tomb . Password OK. 480s tomb (*) Locking test.tomb with argon2-test.key 480s tomb . Formatting Luks mapped device. 487s tomb . Formatting your Tomb with btrfsmixedmode filesystem. 487s tomb . Done locking test using Luks dm-crypt aes-xts-plain64 487s tomb (*) Your tomb is ready in test.tomb and secured with key argon2-test.key 487s tomb . Commanded to open tomb test.tomb 488s tomb . Valid tomb file found: test.tomb 488s tomb . Key is valid. 488s tomb . Mountpoint not specified, using default: /media/test 488s tomb (*) Opening test on /media/test 488s tomb . This tomb is a valid LUKS encrypted device. 488s tomb . Cipher is "aes" mode "xts-plain64" hash "sha512" 488s tomb . A password is required to use key argon2-test.key 488s tomb . Unlocking KDF key protection (argon2) 488s tomb . Password OK. 490s tomb (*) Success unlocking tomb test 490s tomb . Filesystem detected: btrfs 490s tomb . Checking filesystem via /dev/loop0 490s [1/7] checking root items 490s [2/7] checking extents 490s [3/7] checking free space tree 490s [4/7] checking fs roots 490s [5/7] checking only csums items (without verifying data) 490s Opening filesystem to check... 490s Checking filesystem on /dev/mapper/tomb.test.66437b4bb4d34fd221a7d95ca41b5e8d27eb8741bd41ae443897c5d0f7d51aa7.loop0 490s UUID: 41001585-1b7b-4839-abbf-3553f19f6e3d 490s found 36864 bytes used, no error found 490s total csum bytes: 0 490s total tree bytes: 36864 490s total fs tree bytes: 8192 490s total extent tree bytes: 4096 490s btree space waste bytes: 30304 490s file data blocks allocated: 0 490s referenced 0 490s [6/7] checking root refs 490s [7/7] checking quota groups skipped (not enabled on this FS) 491s tomb (*) Success opening test.tomb on /media/test 491s ~~ Copying some data into the opened tomb ... 491s ~~ Opened tomb's content is ... 491s total 28 491s drwxr-xr-x 1 ubuntu ubuntu 88 Jan 18 09:21 . 491s drwxr-xr-x 3 root root 4096 Jan 18 09:21 .. 491s -rw------- 1 ubuntu ubuntu 12 Jan 18 09:21 .host 491s -rw------- 1 ubuntu ubuntu 11 Jan 18 09:21 .last 491s -rw------- 1 ubuntu ubuntu 5 Jan 18 09:21 .uid 491s -rw------- 1 ubuntu ubuntu 940 Jan 18 09:20 argon2-test.key 491s -rw------- 1 ubuntu ubuntu 947 Jan 18 09:20 pbkdf2-test.key 491s tomb . Closing tomb [test] mounted on /media/test 491s tomb (*) Tomb [test] closed: your bones will rest in peace. 491s autopkgtest [09:21:17]: test create-and-use-a-tomb-with-doas: -----------------------] 492s create-and-use-a-tomb-with-doas PASS 492s autopkgtest [09:21:18]: test create-and-use-a-tomb-with-doas: - - - - - - - - - - results - - - - - - - - - - 492s autopkgtest [09:21:18]: @@@@@@@@@@@@@@@@@@@@ summary 492s create-and-use-a-tomb-with-sudo PASS 492s create-and-use-a-tomb-with-doas PASS 509s nova [W] Using flock in prodstack6-arm64 509s Creating nova instance adt-plucky-arm64-tomb-20250118-091306-juju-7f2275-prod-proposed-migration-environment-20-9c26dd8d-3df4-4fb9-879a-f40f63034bc8 from image adt/ubuntu-plucky-arm64-server-20250118.img (UUID 120b6518-c337-4010-a36c-6a4426a27dbc)... 509s nova [W] Timed out waiting for 0669d963-52e5-4e0e-aa6f-48520a75451d to get deleted. 509s nova [W] Using flock in prodstack6-arm64 509s Creating nova instance adt-plucky-arm64-tomb-20250118-091306-juju-7f2275-prod-proposed-migration-environment-20-9c26dd8d-3df4-4fb9-879a-f40f63034bc8 from image adt/ubuntu-plucky-arm64-server-20250118.img (UUID 120b6518-c337-4010-a36c-6a4426a27dbc)... 509s nova [W] Timed out waiting for 155e2688-0199-4770-a51a-67afe27867de to get deleted.