[Pkg-zfsonlinux-devel] Bug#1068559: Bug#1068559: Bug#1068559: Bug#1068559: zfs-linux: isolation-machine autopkgtest fails: zfs-test-suite times out (hangs?)

[陈 晟祺]

Hi,

> 2024年4月9日 02:51，Paul Gevers <elbrus at debian.org> 写道：
> 
> Our timeout is 10000 seconds, so 2.47 hours, per autopkgtest stanza (overall it's 8 hours). If the test is going to take longer, it will fail anyways. So maybe it was just still running? I'm a bit hesitant, particularly about the memory to make much bigger VM's, because most tests don't need it and it limits the amount of VM's we can make. We need to strike a nice balance (or fix https://salsa.debian.org/ci-team/debci/-/issues/166#note_451831 and add zfs-linux to a "huge" list)
> 

I totally understand your consideration. I think it would be great if we could specify more detailed resource requirements on test metadata (thus not wasting resources on small tests).

> 
> Well, if we can't run the test on our infra, we could disable it, but what's the point of having the autopkgtest then? (If you split the tests over multiple stanza, you get the 2.47 hour per set. Does that help?)
> 

It might help. For upstream test on GitHub Actions, it is actually split into four parts [1], each taking ~1hr. I can (and plan to) integrate that into debt tests.

> Let me try to see if I can have debci create larger VM's for us and let me try your package again. What are the resources you use yourself for the test and how long does it take in that case?
> 

My testing resources are maybe not that representative (20 cores + 32GB memory), it takes about the same time (3hr40min) as upstream configuration (4 cores + 7GB).
I will try with fewer resources recently and give you more information.

[1]: https://github.com/openzfs/zfs/blob/master/.github/workflows/scripts/setup-functional.sh

--
Thanks,
Shengqi Chen