El 31/05/26 a las 23:52, Leopold Palomo-Avellaneda escribió: > Hi, > > > I'm trying to help in packaging of fastdds [1]. It is a small monster > package. > > After update all the patches to the new version, I pushed it to salsa. > However, I have not been able to built it because timeout. > > I have modified the timeout in the project to 4h, however, still the limit > of 3h still is applied. > > I have configured a runner in my university to build the package. They > connect to my runner, use the same image as salsa, but it fails because: > > /usr/bin/bash: line 273: cd: /builds/robotics-team/fastdds/debian/output: No > such file or directory > WARNING: after_script failed, but job will continue unaffected: exit code 1 > > So, > > 1) Can we use a private runner to a salsa project to build a packages, at > least in testing?
I think "E: unable to pick chroot mode automatically (use --mode for manual selection)" gives a better clue. You runner needs to run privileged containers for being able to run (sbuild+)unshare. Yeah, that is not idea for a 'docker' gitalb-runner executor in a locally shared runner. > 2) How can I increase or how can we manage to build packages that needs a > lot of time to be built? The Salsa CI team needs to reintroduce the ccache support, that would probably be useful here. In the meantime, please reach out to the salsa admins to see if they could help. Cheers, -- S
