Re: Don't run Salsa CI in vain - a disabled CI is better than a persistently failing one
Eric Dorland <[email protected]>
| Newsgroups | gmane.linux.debian.devel.general |
|---|---|
| Message-ID | <akIK29T30cgLMOnT@colossus> |
* Otto Kekäläinen ([email protected]) wrote: [snip] > Of course, there are also cases where Salsa CI fails because something > is genuinely broken (e.g. today I looked at rtpengine, which has > autopkgtest failing in Salsa CI and continues to upload, causing > Debian CI to fail as well). However, people won't pay attention to > real failures if too many packages have unmaintained and permanently > failing Salsa CI results. [snip] This is perhaps a slight tangent, but how does one get help with salsa CI problems? For example, jujutsu's build appears to stall with no output until it times out: https://salsa.debian.org/rust-team/jujutsu/-/jobs/9852029. It builds fine locally and on buildds and I'm at a bit of a loss how to debug this problem. -- Eric Dorland <[email protected]> 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEQ88SKPcm/VtHTOliwlb71QAiHpMFAmpCCtcACgkQwlb71QAi HpNHjhAAl1I5hlrTBvyaTPQI6d2Gg3YP8pKBAitb7G6OCtkdVmR9LBXDwNWnZUxh D/0vr53jTwAMCTEK7RPZcqUVkisT4hgc56hpJv6FFc1VABBJOJQxYD7PMJWq9otS mzdwEsEI9RbVcLq/ocAqQA0n2z6sXdXfwn0cvPBhAR+nXs5ePkuB/rl895XGdyag LYFjI3hmHGmvSzWmjRRL7M9Rcz+9Ink0nChlzwfSwSaLqenG4Afv+n3SrEjFxL7s h+ErRSgUDKO8BhCHhmaC9ssLMuLB058BpMrTCyMtHRue+r+M5ntPVrZuUXyOKgH8 x6TFv5E4MUcgAoVak9/NpY6KAXfd6pX6jC9E3r2bS/hkfEWZt3JdcSEfyoWtQ9hD IfX87aEtKWv+1LHdmqpAZrI+IFyoR9pE0RYMUCiKDKh6vaE5vb+gnku0Kj4ZfLyh tE9MWpUXD3aDYS0fmaqu36nmaWaI9ySC8/7bZ06te3KM4zx9oATbJ2/uqOlOkqeP TpXaZ2yIoK2ipoctL72t2Juc8nza8nrSTVzP9EuxvbyFOiY4YguIiSvqDoRmh/f9 9QCi3v1JZ2SGCe9bzZ4G3tBUMH9xEww72JzT+9d/3YYY46PeN9q/FUMe3K6/afV2 dBh6QjK1WZLsYYuYxPV7yOTY7eiDuq+Cakw3ExrduuiPsiiAEFk= =zxrP -----END PGP SIGNATURE-----