I need to debug a thing that runs in CI. Part of the run is a tool that takes five minutes to run and this makes iterations slow. I could rewrite that to run in less than ten seconds, but doing that would take a week or two of full time work. What do I do?
EDIT: posted a response describing what I actually did
- Suffer slow iterations (23%, 8 votes)
- Take the Knuthian detour and rewrite the tool (64%, 22 votes)
- Use a fake tool that's fast (32%, 11 votes)
- You're supposed to be experienced, why ask? (8%, 3 votes)
Questa voce è stata modificata (2 settimane fa)
Elena ``of Valhalla''
in reply to Lars Wirzenius • •Lars Wirzenius
in reply to Elena ``of Valhalla'' • • •Elena ``of Valhalla''
in reply to Lars Wirzenius • •Tony Finch likes this.
Didier Raboud
in reply to Lars Wirzenius • • •itgrrl
in reply to Lars Wirzenius • • •obligatory #XKCD 1205 💁♀️
see shy jo
in reply to Lars Wirzenius • • •Joe ❌👑
in reply to Lars Wirzenius • • •Lars Wirzenius
in reply to Lars Wirzenius • • •This got more interest than I expected. My least serious polls do that. But it's fine.
I went with the "fake it" option, because the thing I was debugging was not inherently about the tool I was using, but about the things happening in CI when publishing the output. By removing the real tool from the process, I shortened the iteration cycle to about half a minute. This allowed me to find the root cause of the problem, which turned out be something entirely different than I though it'd be.
Lars Wirzenius
in reply to Lars Wirzenius • • •Wouter Verhelst
in reply to Lars Wirzenius • • •<evil grin> use an LLM to interpret the CI definition and ask it to generate an overengineered stub that simulates your CI environment and then call that every time?
(yes I've seen people do that 🤷)