diff options
author | David Kalnischkies <david@kalnischkies.de> | 2021-03-11 13:38:53 +0100 |
---|---|---|
committer | David Kalnischkies <david@kalnischkies.de> | 2021-03-11 14:05:41 +0100 |
commit | 0d25ce3d466ecddea02d171981f011f7dbf95e08 (patch) | |
tree | be5a631b2e2d2c9a34857dd1880617bfd424e7e6 /methods/connect.cc | |
parent | ade9d3c41da55171f258a3aeed2e3b3350da8920 (diff) |
If a transaction is doomed we want to gracefully shutdown our zoo of
worker processes. As explained in the referenced commit we do this by
stopping the main process from handing out new work and ignoring the
replies it gets from the workers, so that they eventually run out of
work.
We tested this previously by checking if a rred worker was given work
items at all, but depending on how lucky the stars of the machine
working on this are the worker would have already gotten work before the
transaction was aborted – so we tried this 25 times a row (f35601e5d2).
No machine can be this lucky, right?
Turns out the autopkgtest armhf machine is very lucky.
I feel a bit sorry for feeding grep such a long "line" to work with, but
it seems to work out. Porterbox amdahl (who is considerably less lucky;
had to turn down to 1 try to get it to fail sometimes) is now happily
running the test in an endless loop.
Of course, I could have broken the test now, but its still a rather
generic grep (in some ways more generic even) and the main part of the
testcase – the update process finishes and fails – is untouched.
References: 38f8704e419ed93f433129e20df5611df6652620
Closes: #984966
Diffstat (limited to 'methods/connect.cc')
0 files changed, 0 insertions, 0 deletions