[Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?
Ahmed Siam
aahs.coder at gmail.com
Sat Aug 24 00:06:39 BST 2024
On Sat, Aug 24, 2024 at 2:00 AM Ahmed Siam <aahs.coder at gmail.com> wrote:
>
> On Sat, Aug 24, 2024 at 1:45 AM Ahmed Siam <aahs.coder at gmail.com> wrote:
> >
> > On Sat, Aug 24, 2024 at 1:25 AM Jérémy Lal <kapouer at melix.org> wrote:
> > > A bunch of packages I know (nodejs, receptor to name a few) have salsa CI failures, but no sbuild failures.
> > > It would be perfect if the build process was exactly the same.
> >
> > There is a work-in-progress MRs about using sbuild for building packages.
> >
> > When I tried to run salsaci on the perl package, It failed at the first job.
> > Maybe the bug that causes failure of the pipeline on nodejs is similar.
> > I will try to figure out the cause and fix it.
>
> Actually, it isn't the same error.
> It seems that nodejs fails to build because of runner timeout.
> I think this error won't be solved even after switching to sbuild.
> Nodejs package needs more powerful runners and/or larger timeout value.
>
> Nodejs pipeline run: https://salsa.debian.org/js-team/nodejs/-/pipelines/681481
This pipeline run from Nodejs shows a similar error to the one I got
in Perl package:
https://salsa.debian.org/js-team/nodejs/-/pipelines/683419
-- Ahmed Siam
More information about the Debian-salsa-ci
mailing list