| 14 Sep 2023 |
chayleaf | hydra-eval-jobs returned signal -1:
warning: unknown setting 'allowed-users'
warning: unknown setting 'trusted-users'
trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
trace: warning: fail2ban can not be used without a firewall
trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
timeout
would meta.timeout help with this? | 19:25:18 |
chayleaf | * hydra-eval-jobs returned signal -1:
warning: unknown setting 'allowed-users'
warning: unknown setting 'trusted-users'
...
timeout
would meta.timeout help with this? | 19:25:52 |
chayleaf | * hydra-eval-jobs returned signal -1:
warning: unknown setting 'allowed-users'
warning: unknown setting 'trusted-users'
trace: <omitted by me for brevity>
timeout
would meta.timeout help with this? | 19:26:05 |
chayleaf | or maybe meta.maxSilent? | 19:26:16 |
@rick:matrix.ciphernetics.nl | Either could help, but what's up with the build? | 20:44:15 |
chayleaf | my server is just slow | 20:56:15 |
chayleaf | and it isn't being built, this is just the evaluation | 20:56:38 |
| 0xMRTT [envs.net] changed their display name from 0xMRTT to 0xMRTT (Old). | 20:59:37 |
@rick:matrix.ciphernetics.nl | I am not sure if eval is affected by these timeouts, actually | 21:26:50 |
chayleaf | for context, my last successful eval took a total of 5 hours | 21:27:09 |
@rick:matrix.ciphernetics.nl | They seem mainly for builds to me | 21:27:07 |
@rick:matrix.ciphernetics.nl | Did you check the output of hydra in journalctl? | 21:27:36 |
@rick:matrix.ciphernetics.nl | That's pretty long | 21:27:46 |
@rick:matrix.ciphernetics.nl | So yeah, not sure | 21:28:00 |
@rick:matrix.ciphernetics.nl | Sounds like it's _some_ timeout indeed | 21:28:11 |
chayleaf | yeah, it just doesn't specify which one... | 21:28:28 |
| 17 Sep 2023 |
| 0xMRTT [envs.net] changed their display name from 0xMRTT (Old) to 0xMRTT [envs.net]. | 17:00:16 |
| 18 Sep 2023 |
| @ulrikstrid:matrix.org left the room. | 08:36:00 |
| 19 Sep 2023 |
hacker1024 | Redacted or Malformed Event | 01:41:56 |
hacker1024 | * We've recently started using a gitlabpulls input to generate jobsets for merge requests in our declarative project. Since doing this, however, we have noticed that jobsets seem to randomly be missing inputs. These inputs are present in the generated jobset.json, but are absent from the "configuration" tab in the Web UI. I cannot find anything relevant in the evaluation or queue-runner logs. Does anyone know what might be going on here? The missing inputs change whenever the .jobsets output changes. | 01:42:27 |
| 21 Sep 2023 |
| dedmunwalk joined the room. | 23:03:52 |
| 22 Sep 2023 |
| K900 changed their profile picture. | 09:40:58 |
| @clerie:bau-ha.us changed their display name from clerie to (moved to @clerie:entr0py.de). | 21:13:48 |