Hermes Jesus Rodriguez Azuaje <[email protected]> writes: > Hi, > > I have been packaging the ncruces / pgwd chain under go-team/packages. > Over the weekend several test_the_archive jobs stayed stuck / failed with > no matching runners for tag go-ci (no job trace). That matches a single > point of failure on the current go-ci pool.
What value do you find in the test_the_archive CI job? I'm not objecting to fixing it, but I never found it useful for any of my workflows. When does it help you notice a problem in the packaging? For me it normally just always succeeds regardless of package mistakes, and sometimes it consistently fail (e.g., for packages with repacked upstream sources) even though there is no problem with the package. /Simon
signature.asc
Description: PGP signature
