13 Oct 2024 |
raitobezarius | and every failure the -1 back | 19:48:46 |
KFears (tragedy arc) | Yeah, it's always +- 1 | 19:48:57 |
KFears (tragedy arc) | I've got a lot of patchsets, too | 19:49:11 |
raitobezarius | i just realized that we could also fix probably the checks.js script | 19:49:16 |
KFears (tragedy arc) | So I'll hope we'll have a much easier time merging those once the CI is less prone to flapping | 19:49:36 |
raitobezarius | aha, i guess i need to find a way to propagate it correctly | 19:49:53 |
KFears (tragedy arc) | FWIW, I've seen some legitimate failures on Buildbot CI, but they also seems like some Hydra internals are leaking out | 19:50:13 |
KFears (tragedy arc) | I mean, I can't find other explanations for why parts of Vagrant VMs just refuse to evaluate all of a sudden, and the CI fails, other than some eval/Hydra mysteries | 19:51:04 |
just1602 | raitobezarius: nice job, having the report directly in guerrit is really cool ! 🎉 | 20:16:05 |
raitobezarius | heh, it was there a long time ago, I just broke it unfortunately :) | 20:16:25 |
14 Oct 2024 |
| IndustrialRobot joined the room. | 05:20:53 |
jade_ | raitobezarius: do you know anything about upgrading garage from 0.9.x to 1.0? | 05:30:21 |
jade_ | it appears that we would need to do that to fix garage's inability to shut down properly | 05:31:00 |
jade_ | ah, i see, we would have to take a backup of metadata and then do the upgrade. hm. doable. | 05:42:00 |
jade_ | well it doesn't seem to be borked, and i simply upgraded it | 05:50:18 |
jade_ | i would so love to have profiles for our buildbot instance, it's very weird that the API is so slow | 06:31:41 |
jade_ | the particular api request that keeps doing this is https://buildbot.lix.systems/api/v2/builds?builderid=1&property=owners&property=workername&property=branch&property=revision&property=branch&limit=200&order=-number | 06:33:55 |
| polygon system (it/she, no "you") changed their profile picture. | 10:02:53 |
raitobezarius | In reply to @jade_:matrix.org the particular api request that keeps doing this is https://buildbot.lix.systems/api/v2/builds?builderid=1&property=owners&property=workername&property=branch&property=revision&property=branch&limit=200&order=-number i can plug in the prometheus reporter for buildbot but i think it won't be sufficient at all | 12:25:22 |
raitobezarius | we could just throw OTEL there and plug it in our Tempo | 12:25:30 |
raitobezarius | uhm Pyroscope * | 12:25:38 |
raitobezarius | if you log an issue in the public infra repo, I can take care of it at some point | 12:26:02 |
KFears (tragedy arc) | Having it in Tempo would also be nice, I think. You can correlate metrics and profiles in LGTM stack | 12:27:53 |
raitobezarius | there's no otel code in buildbot, so I'm not sure it would be useful | 12:28:06 |
KFears (tragedy arc) | Doesn't Python have OTEL auto-instrumentation? | 12:28:27 |
raitobezarius | with severe caveats | 12:28:41 |
KFears (tragedy arc) | rip | 12:29:24 |
KFears (tragedy arc) | Well I guess it's also not great that OTEL doesn't have profiling even in the most bleeding edge distributions, but can't be helped | 12:29:58 |
KFears (tragedy arc) | https://opentelemetry.io/docs/zero-code/python/ | 12:34:29 |
KFears (tragedy arc) | Looks like it's not too bad? Tracing only inbound and outbound requests isn't the best, but it's still quite useful | 12:35:01 |