!zghijEASpYQWYFzriI:nixos.org

Hydra

388 Members
111 Servers

Load older messages


SenderMessageTime
7 Feb 2022
@janne.hess:helsinki-systems.dedas_j(also I think you broke our Hydra only 1 or 2 times in ways that were pretty trivial to fix)18:31:28
@grahamc:nixos.org@grahamc:nixos.orgBug breaks or intentional breaks? (Thinking about missed column changes or function signature mistakes)18:32:11
@janne.hess:helsinki-systems.dedas_j
In reply to @grahamc:nixos.org
Bug breaks or intentional breaks? (Thinking about missed column changes or function signature mistakes)
Intentional breaks. Yeah there was also the function signature mistake but that was easily reverted locally for the time being
18:32:40
@grahamc:nixos.org@grahamc:nixos.orgGotcha18:32:50
@janne.hess:helsinki-systems.dedas_jI do however think it would be useful to document intentional breakages somewhere (unless it introduces too much work for the developer)18:33:26
@janne.hess:helsinki-systems.dedas_j something like a changelog but without releases. Just 2021-02-07 fefefe emitted eval_* events are now tab-separated instead of \t separated 18:34:08
@janne.hess:helsinki-systems.dedas_j * something like a changelog but without releases. Just 2021-02-07 fefefe Emitted eval_* events are now tab-separated instead of \t separated 18:34:32
@grahamc:nixos.org@grahamc:nixos.org That does sound good. Especially, for example, the Postgres version change 18:35:17
@grahamc:nixos.org@grahamc:nixos.org Let’s do that and add it to the pr template 18:35:37
@janne.hess:helsinki-systems.dedas_jYeah, I could then use either the date or the commit hash when updating my Hydra after a long time and see what I can expect to be broken18:35:43
@grahamc:nixos.org@grahamc:nixos.org Yeah, seems great. 18:37:02
@grahamc:nixos.org@grahamc:nixos.orgWhen I broke your hydra on purpose did you adapt or partially revert, or?18:37:25
@janne.hess:helsinki-systems.dedas_jwell adapt. there's no point in carrying patches for years and having to rebase them over time18:43:24
@janne.hess:helsinki-systems.dedas_jalso your changes did usually improve things so staying with the old working state was not ideal either18:43:42
@grahamc:nixos.org@grahamc:nixos.orgI just wanted to make sure it wasn’t a nuisance you were actively choosing to avoid. That wouldn’t be very nice!18:44:22
@janne.hess:helsinki-systems.dedas_jnono, the only time we reverted your changes was when the signature stuff broke our hydra18:44:59
@janne.hess:helsinki-systems.dedas_jI swear I never disliked your changes :D18:45:09
@grahamc:nixos.org@grahamc:nixos.orgwhew, thanks :)18:48:08
@janne.hess:helsinki-systems.dedas_jBtw, is both dynamic runcommand and runcommand logs on master now?18:48:31
@janne.hess:helsinki-systems.dedas_jWe could upgrade then and drop the patches (and my insecure implementation 👀18:48:47
@janne.hess:helsinki-systems.dedas_j * We could upgrade then and drop the patches (and my insecure implementation 👀)18:48:48
@cole-h:matrix.orgcole-hDynamic RunCommand, not yet. But the logs are on (Hydra) master.18:53:03
@cole-h:matrix.orgcole-h(Dynamic RunCommand PR: https://github.com/NixOS/hydra/pull/1103)18:53:16
@grahamc:nixos.org@grahamc:nixos.orgI'm a bit shy on merging the dynamic runcommand PR given, well, its behavior :P18:53:34
@grahamc:nixos.org@grahamc:nixos.orgwe use it internally but I'd like at least another set of people want it for real before merging18:54:00
@janne.hess:helsinki-systems.dedas_j aren't you using it, ajs124? 18:54:16
@andreas.schraegle:helsinki-systems.deajs124 yes 18:54:43
@janne.hess:helsinki-systems.dedas_j

url = "https://nc.helsinki.tools

big oof

18:55:04
@grahamc:nixos.org@grahamc:nixos.orgneat18:55:19
@grahamc:nixos.org@grahamc:nixos.orgis it a good interface?18:55:59

Show newer messages


Back to Room ListRoom Version: 6