Hi Paul, > 2024年4月7日 21:10，Paul Gevers <elb...@debian.org> 写道： > > Hi, > > The host that runs this is an m3-large instance at equinix [1]. > > We create the qemu image with autopkgtest-build-qemu (default settings as far > as I know). > > From within the testbed: > root@host:~# lscpu > lscpu > Architecture: x86_64 > CPU op-mode(s): 32-bit, 64-bit > Address sizes: 48 bits physical, 48 bits virtual > Byte Order: Little Endian > CPU(s): 1 > On-line CPU(s) list: 0 > Vendor ID: AuthenticAMD > BIOS Vendor ID: QEMU > Model name: AMD EPYC 7502P 32-Core Processor > BIOS Model name: pc-i440fx-7.2 CPU @ 2.0GHz > BIOS CPU family: 1 > CPU family: 23 > Model: 49 > Thread(s) per core: 1 > Core(s) per socket: 1 > Socket(s): 1 > > root@host:~# lsmem > lsmem > RANGE SIZE STATE REMOVABLE BLOCK > 0x0000000000000000-0x000000007fffffff 2G online yes 0-15 > > Memory block size: 128M > Total online memory: 2G > Total offline memory: 0B >
With resources limited to one CPU (AMD EPYC 7551) and 2G memory, my local test could now reproduce the test hang and following time out error. I think it is caused by insufficient resources (e.g. OOM killer, but I am not sure). Even we can work it around, the test process would be still be too slow to finish. Is it possible to allocate more resources for the test? For reference, openzfs uses GitHub-hosted workflow runners [1] for test. Each runner has 2 CPU cores and 7 GB memory, under which configuration the whole test still takes ~4hrs. If not, is there any way to mark the test as optional (thus not causing RC bug)? Otherwise our worst choice would be disable the test completely. [1]: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-private-repositories [2]: https://github.com/openzfs/zfs/blob/master/.github/workflows/scripts/setup-functional.sh Thanks, Shengqi Chen
