Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to use that. However, it fails. Can you please
investigate the situation and fix it? I copied some of the output at the
bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing, but because machine-isolation
support by ci.debian.net is new I have not marked this bug as serious (yet).

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/packages/s/snapd/testing/amd64/44893416/

117s autopkgtest [08:11:30]: test integrationtests: [-----------------------
117s + mkdir -p /etc/systemd/system/snapd.service.d/
117s + [  !=  ]
117s + systemctl daemon-reload
117s + MemTotal:        2024348 kB
117s MemFree:          511492 kB
117s MemAvailable:    1717772 kB
117s Buffers:           49680 kB
117s Cached:          1214308 kB
117s SwapCached:            0 kB
117s Active:           145956 kB
117s Inactive:        1134464 kB
117s Active(anon):      16548 kB
117s Inactive(anon):      416 kB
117s Active(file):     129408 kB
117s Inactive(file):  1134048 kB
117s Unevictable:          12 kB
117s Mlocked:              12 kB
117s SwapTotal:             0 kB
117s SwapFree:              0 kB
117s Zswap:                 0 kB
117s Zswapped:              0 kB
117s Dirty:             39388 kB
117s Writeback:             0 kB
117s AnonPages:         16492 kB
117s Mapped:            27584 kB
117s Shmem:               488 kB
117s KReclaimable:     130964 kB
117s Slab:             162344 kB
117s SReclaimable:     130964 kB
117s SUnreclaim:        31380 kB
117s KernelStack:        1472 kB
117s PageTables:         1104 kB
117s SecPageTables:         0 kB
117s NFS_Unstable:          0 kB
117s Bounce:                0 kB
117s WritebackTmp:          0 kB
117s CommitLimit:     1012172 kB
117s Committed_AS:      57040 kB
117s VmallocTotal:   34359738367 kB
117s VmallocUsed:       20272 kB
117s VmallocChunk:          0 kB
117s Percpu:              420 kB
117s HardwareCorrupted:     0 kB
117s AnonHugePages:         0 kB
117s ShmemHugePages:        0 kB
117s ShmemPmdMapped:        0 kB
117s FileHugePages:         0 kB
117s FilePmdMapped:         0 kB
117s Unaccepted:            0 kB
117s HugePages_Total:       0
117s HugePages_Free:        0
117s HugePages_Rsvd:        0
117s HugePages_Surp:        0
117s Hugepagesize:       2048 kB
117s Hugetlb:               0 kB
117s DirectMap4k:       73588 kB
117s DirectMap2M:     2023424 kB
117s DirectMap1G:           0 kB
117s printf %s\n -950
117s + cat /proc/meminfo
117s + echo ubuntu:ubuntu
117s + chpasswd
117s chpasswd: (user ubuntu) pam_chauthtok() failed, error:
117s Authentication token manipulation error
117s chpasswd: (line 1, user ubuntu) password not changed
118s autopkgtest [08:11:31]: test integrationtests: -----------------------]

Hello

Thank you for reporting this. I think I understand what the problem is and I may already have a patch that I have not yet upstreamed or sent to debian.

Thanks again, I will test the fix and send it as soon as the xz archive woes are over.

Best regards
ZK

Hello

Thank you for reporting this. I think I understand what the problem is and I may already have a patch that I have not yet upstreamed or sent to debian.

Thanks again, I will test the fix and send it as soon as the xz archive woes are over.

Best regards
ZK