Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 104:21:22 |
Calls: | 290 |
Files: | 905 |
Messages: | 76,612 |
Hi,
On 01-01-2025 21:22, Julian Gilbey wrote:
I could mark the autopkgtests as only
running on those four archs. Is that the best thing to do, or is
there some way to indicate to ci.debian.net that the package is not installable on some archs and so it should not try to test the package
on them?
ci.d.n just runs what's requested by users of the API or self-service and doesn't know anything about packages. It's our migration software that knows for sources that only build arch specific binaries that there's nothing to run, but arch:all binaries are available anywhere, so it errs on the greedy side.
That being said, how we normally deal with these things if we're made aware of them is to hint-ignore the problem on those architectures for the migration to testing, as the problem is automatically ignored from that moment on. Because it is a PITA to maintain those kind of lists in sync with the archive. Imagine spyder being build on an architecture where it's not available yet, you'd need to update all those lists.
I'll add the hints shortly.
Paul