On Tuesday, September 9, 2025 6:02:14 AM Mountain Standard Time Santiago Vila wrote: > Hello Otto. > > I've finally disabled the pipelines, not exactly in the same way you > proposed in the MR, but in another way which I believe preserves the > spirit. > > I still would like to know how much memory can we expect from Salsa CI > runners, and how likely or unlikely it is that we will be able to > enable Salsa CI for graph-tool some day. In case it is helpful to others, I have setup a small number of custom runners for packages I maintain where the standard CI runners are not sufficient. In my case, these are situations where the standard CI runners cannot finish at least one of the stages within 3 hours. Using a custom runner allows me to set any timeout I prefer. In some cases, because the hardware on my custom runner is more powerful than the standard CI runners, I no longer need to adjust the timeout, but in other cases an adjustment is still needed. For example: https://salsa.debian.org/python-team/packages/pyinstaller/-/blob/debian/ master/debian/salsa-ci.yml?ref_type=heads For anyone wanting to setup a custom runner, I have updated the wiki with the instructions that worked for me: https://wiki.debian.org/Salsa/Doc/CustomRunners To round out this conversation, I am currently in the process of developing a custom salsa-ci.yml for qt6-webengine. The unique problem with that package is that it produces over 4.5 GB of artifacts, which exceeds the maximum allowed by Salsa (in addition to needing to run for longer and needing more system resources than the standard runners). I have not finished, but currently I have a modified salsa-ci.yml that performs some of the tests I am interested in tracking: https://salsa.debian.org/soren/qt6-webengine/-/blob/salsa-ci/debian/salsa-ci.yml?ref_type=heads -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.