| 9 Oct 2021 |
 lukegb (he/him) | e.g. https://hydra.nixos.org/build/155606118/nixlog/39 | 00:18:32 |
| lukegb (he/him) | Fatal Python error: _enter_buffered_busy: could not acquire lock for <_io.BufferedWriter name='<stderr>'> at interpreter shutdown, possibly due to daemon threads
Python runtime state: finalizing (tstate=0x441670)
Current thread 0x0000fffff7ff47b0 (most recent call first):
<no Python frame>
/nix/store/cf43j6r16pir93wc97wl10n8ybww6pa8-stdenv-linux/setup: line 1319: 4 Aborted (core dumped) /nix/store/hn2kc3fkzm72acrgj0nmvqcchln7jxrc-nixos-test-driver-dhparams/bin/nixos-test-driver
builder for '/nix/store/gqaa94hihgl54szsjgpv9iaghkpcsyx8-vm-test-run-dhparams.drv' failed with exit code 134
| 00:18:43 |
 hexa | heh, the python bump is in staging, not master 😀 | 00:35:01 |
| hexa | 3.9.6 🆗 | 00:35:33 |
| hexa | 3.9.7 ❌ | 00:35:45 |
| hexa | https://hydra.nixos.org/log/1xwq5gg8fi31g6klkyc092dwpji04qx6-Python-3.9.7.tar.xz.drv | 01:00:46 |
| hexa | great. | 01:00:49 |
| hexa | error: unable to download 'https://www.python.org/ftp/python/3.9.7/Python-3.9.7.tar.xz': Couldn't resolve host name (6)
builder for '/nix/store/1xwq5gg8fi31g6klkyc092dwpji04qx6-Python-3.9.7.tar.xz.drv' failed with exit code 1
| 01:01:13 |
 Vladimír Čunát | In reply to @hexa:lossy.network
error: unable to download 'https://www.python.org/ftp/python/3.9.7/Python-3.9.7.tar.xz': Couldn't resolve host name (6)
builder for '/nix/store/1xwq5gg8fi31g6klkyc092dwpji04qx6-Python-3.9.7.tar.xz.drv' failed with exit code 1
I don't know which Hydra build triggered this, but restarting it now should work. My current workaround: https://hydra.nixos.org/eval/1712001
(Though I really still hope for Nix release "soon" and getting it to Hydra.) | 07:22:28 |
| Vladimír Čunát | In reply to @vcunat:matrix.org
I don't know which Hydra build triggered this, but restarting it now should work. My current workaround: https://hydra.nixos.org/eval/1712001
(Though I really still hope for Nix release "soon" and getting it to Hydra.) Anyway, let's do a new staging-small eval: https://hydra.nixos.org/eval/1712002 | 08:11:57 |
| hexa | Vladimír Čunát: on python-unstable (https://hydra.nixos.org/eval/1711922?full=1#tabs-now-fail) | 10:21:30 |
| hexa | not sure how to navigate to the python3.9 build itself to restart it, since it is only an indirect dependency of the package set | 10:22:01 |
| hexa | restarted all failed builds, let's see if that helps | 10:27:07 |
| hexa | Vladimír Čunát: https://hydra.nixos.org/build/155611207 no idea how to give python itself a poke here. | 11:00:31 |
 das_j | In reply to @hexa:lossy.network
Vladimír Čunát: https://hydra.nixos.org/build/155611207 no idea how to give python itself a poke here. You can probably clear the failed builds cache if you have the permissions | 11:21:43 |
| das_j | I don't think there is a selective way unless you log into the hydra and do nix-store -r and restart the build | 11:22:00 |
| hexa | 🤷 | 11:22:02 |
| hexa | pretty sure I only have restart bits | 11:22:10 |
| das_j | that's more than me :D | 11:22:39 |
| hexa | just had to ask 😆 | 11:38:09 |
| das_j | 🤔 | 11:48:13 |
| Vladimír Čunát | When you restart a build, it restarts the dependency that failed it. | 12:20:04 |
| Vladimír Čunát | Anyway, it's blocked on a different failure now :-) | 12:21:29 |
| hexa | great! | 12:25:57 |
| das_j | In reply to @vcunat:matrix.org
When you restart a build, it restarts the dependency that failed it. Even when the dependency is cached failed? :0 | 13:19:13 |
| Vladimír Čunát | Redacted or Malformed Event | 15:10:05 |
| Vladimír Čunát | In reply to @janne.hess:helsinki-systems.de
Even when the dependency is cached failed? :0 I think so, but in any case you can click on the build from which it was cached and restart that one. | 15:10:18 |
| das_j | In reply to @vcunat:matrix.org
I think so, but in any case you can click on the build from which it was cached and restart that one. But wouldn't that possibly rebuild non-current builds? | 15:32:00 |
| das_j | * But wouldn't that possibly build non-current builds? | 15:32:12 |
| Vladimír Čunát | In reply to @janne.hess:helsinki-systems.de
But wouldn't that possibly build non-current builds? It could, but typically we do have a separate job for non-trivial builds, except e.g. stdenv bootstrapping. | 15:32:48 |
