| 18 Oct 2024 |
 jade_ | to a degree there are also lix bugs involved in a few of these ones, but we are working on those | 22:34:06 |
| jade_ | * to a degree there are also lix bugs involved in a few of the ci issues, but we are working on those | 22:34:13 |
 Yureka (she/her) | as in conceptually broken, the order in which the buildbot creates gcroots and builds stuff did not make any sense | 22:34:39 |
| jade_ | mhmm | 22:34:48 |
| jade_ | yeah i noticed that too | 22:34:55 |
| jade_ | and the gcroots notably have to be on the remote store | 22:35:01 |
| jade_ | rather than the local one | 22:35:06 |
| jade_ | but this is all actually silliness because ideally it would be bound to a protocol session :/ | 22:35:32 |
| jade_ | also, raitobezarius can you get the state of what is actually running in prod buildbot-nix wise clarified?
I want to go fix the eval errors not causing buildbot failures rectified.
| 22:47:14 |
| jade_ | * also, raitobezarius can you get the state of what is actually running in prod buildbot-nix wise clarified?
I want to go fix the eval errors not causing buildbot failures
| 22:47:22 |
| jade_ | if it's a dev branch, that's okay, we can merge it or whatever, i just want to be able to deploy to the box without exploding everything | 22:54:03 |
 raitobezarius | The main branch on the infra repo is the state of truth | 23:14:39 |
| raitobezarius | I can remerge the PR in the ForkOS branch and remerge this in the main branch and tag a checkpoint so that it's clarified, yep | 23:15:09 |
| jade_ | ah, okay. cool. if that's so, i can get the state into order! | 23:18:25 |
| raitobezarius | (I try to keep all the deployments proper wrt to git state but I do sometimes push hotfixes without pushing to git, please yell at me if I do that too often) | 23:19:49 |
| jade_ | yeah, i was scared that there was a loadbearing one of those | 23:20:01 |
| jade_ | so i had assumed you had a lock on the machine | 23:20:05 |
| jade_ | if whatever is in main is clean, i can go from there | 23:20:16 |
| raitobezarius | I lied ; give me a se | 23:21:11 |
| raitobezarius | +c | 23:21:13 |
| raitobezarius | it's not a lie anymore: https://git.lix.systems/the-distro/infra/pulls/143 | 23:23:00 |
| raitobezarius | .oO(really need to fix that "lock machine" concept once and for all) | 23:23:28 |
| raitobezarius | apologies | 23:23:45 |
 Dusk | is https://buildbot.lix.systems/#/buildrequests/197977 a transient failure? | 23:29:07 |
| jade_ | In reply to @bb010g:matrix.org
is https://buildbot.lix.systems/#/buildrequests/197977 a transient failure? that's what usually happens if you push your CL | 23:29:37 |
| jade_ | did it happen in another condition? | 23:29:44 |
| Dusk | In reply to @jade_:matrix.org
did it happen in another condition? i'm not totally sure what you mean by "condition", but i don't believe so. tests reliably pass for me and nothing related changed AFAICT. | 23:30:19 |
| jade_ | In reply to @bb010g:matrix.org
i'm not totally sure what you mean by "condition", but i don't believe so. tests reliably pass for me and nothing related changed AFAICT. like, this happens if you push a new revision of your CL and the old one gets cancelled | 23:30:40 |
| Dusk | ah, i see | 23:30:46 |
| jade_ | there should be a new CL run for the new revision | 23:30:55 |
