The issue turned out to be that the pandas repository's settings were
pointed to a CI settings file outside the repository, so it wasn't even
looking at my debian/salsa-ci.yml.
As suggested by Eriberto's link, this setting is found at (starting from
the repository's page in Salsa, logged in)
Am Thu, Jan 27, 2022 at 10:29:26PM + schrieb Rebecca N. Palmer:
> I've tried these attempts at "do nothing" in debian/salsa-ci.yml. Neither of
> them does that: the default CI still runs.
>
> https://salsa.debian.org/science-team/pandas/-/commits/debian
See
Hi Rebecca,
Em qui., 27 de jan. de 2022 às 20:00, Rebecca N. Palmer
escreveu:
>
> The default (I'm not sure if this is a global or per-team default) Salsa
> CI pipeline tries to build and test packages on every commit.
>
> For pandas, this always hits the 1 hour timeout, and hence "fails"
>
The default (I'm not sure if this is a global or per-team default) Salsa
CI pipeline tries to build and test packages on every commit.
For pandas, this always hits the 1 hour timeout, and hence "fails"
uselessly (wasting both the server's resources, and my attention when a
failure alert
4 matches
Mail list logo