On 31/07/2025 10:41, Samuel Thibault wrote:
It's quite probable, as swapping is a very involved vm thing and we do
know that there are some issues with it, we see sometimes odd build
failures on buildds due to this.
Perhaps you can tune the stress-ng scenarii to isolate the termination
test that you are after from swapping concerns.
I think that is possible and worth a try. The process termination is
currently slowed significantly after the high pageout during the test
run which is why the SIGKILL is required at all. The stress-ng
termination signal sequence is SIGALRMx4, SIGTERM then SIGKILL with a
small time between signals. I could change that to SIGALRM then SIGKILL
and lower the time interval to see if I can get a SIGALRM being
processed whilst SIGKILL is delivered without swapping having taken place.
I'd like to try and find the cause of the swapping bugs so I'll also
continue with the existing test case.
Regards,
Mike.
