| 26 Dec 2025 |
 gabyx | Hi all,
Short question: ofBorg -> is there endeavor to scale this beast a bit more somehow, cause its pretty valuable IMO to test on PRs etc especially for architectures which are not directly x86_64 | 14:35:27 |
 K900 | Not in the immediate future | 14:38:41 |
| gabyx | Does ofBorg if it didnt ran yet, take up the latest commit on the branch? or only when the job has been submitted, so one needs to retrigger it? How to delete the latest @ofborg build bla before then? | 14:46:21 |
| gabyx | * Does ofBorg if it didnt ran yet, take up the latest commit on the branch? or only when the job has been submitted, so one needs to retrigger it? How to delete the latest @ofborg build bla issued before in that scenario? | 14:46:51 |
| K900 | It should use the latest | 14:50:21 |
 Janne | Why not? It's literally free | 15:05:59 |
| gabyx | free? it runs on Github Jobs? or what? | 15:06:34 |
| gabyx | * free? it runs on Github Jobs? It has its own VMs right and is a Github Bot written in Rust? | 15:07:09 |
| Janne | Either my company or my coworker is paying for it :D | 15:07:17 |
| Janne | There are actually plans to re-engineer the entire thing, but the new hydra queue runner came first | 15:07:40 |
| Janne | The current design means there is not really a way to do smart scheduling | 15:08:11 |
| gabyx | What would be really cool is for now, could we launch ofborg our self? | 15:08:35 |
| gabyx | * What would be really cool is for now, could we launch ofborg our self?
Basically manually on a PR? on my own VM or system? | 15:08:57 |
