| 21 Oct 2021 |
Vladimír Čunát | It's still possible to restart all-failed or all-aborted in an eval. | 12:42:14 |
sterni | :D | 12:42:24 |
Vladimír Čunát | ... but that often restarts much more than one wants. | 12:42:33 |
K900 | Janne Heß is the QEMU process alive when it hangs? | 18:58:50 |
K900 | It should definitely exit when that exits | 18:58:59 |
Janne Heß | nope, it's already dead | 18:59:03 |
Janne Heß | ah sorry it is | 18:59:11 |
K900 | Oh no | 18:59:16 |
Janne Heß |  Download image.png | 18:59:21 |
K900 | Can you poke it and see what it's doing? | 18:59:38 |
K900 | Or at least get a core dump | 18:59:45 |
K900 | Cause it should have been sigtermed | 18:59:51 |
Janne Heß | core dump of what? | 19:00:06 |
K900 | Qemu | 19:00:11 |
K900 | Just to see why it's not dying | 19:00:38 |
Janne Heß | SIGABRT causes python to coredump as well btw | 19:01:17 |
K900 | Huh | 19:01:35 |
baloo | may I suggest find /proc/$(pidof qemu)/ -name stack -print -exec cat {} \; as well? | 19:01:57 |
Janne Heß | I'll rerun the test, might take some minutes | 19:02:13 |
Janne Heß | I also outlined the flakyness that you mentioned, K900 without rewriting the entire function ;) | 19:02:39 |
Janne Heß | * I also fixed the flakyness that you mentioned, K900 without rewriting the entire function ;) | 19:02:44 |
baloo | (qemu is in uninterruptible sleep, and dump the kernel stack might prove useful) | 19:02:47 |
K900 | Which one? | 19:02:50 |
baloo | * (qemu is in uninterruptible sleep, and dumping the kernel stack might prove useful) | 19:02:55 |
Janne Heß | https://github.com/NixOS/nixpkgs/pull/142498 | 19:03:13 |
Janne Heß | this one | 19:03:14 |
K900 | Oh yeah nice | 19:03:30 |
K900 | I was less going to rewrite that particular function | 19:04:15 |
K900 | And more going to rewrite the whole damn thing | 19:04:20 |
K900 | But that is nice | 19:04:23 |