Summary: | sys-devel/gdb-8.3: many test errors on sparc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rolf Eike Beer <eike> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | matoro_gentoo, sparc |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | Sparc64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Rolf Eike Beer
2019-06-30 07:44:46 UTC
From what I can see, tests on sys-devel/gdb are disabled on all arches with RESTRICT=test. Should this stay open, and only be closed when force-enabling tests passes? Or is it obsolete? (In reply to matoro from comment #1) > From what I can see, tests on sys-devel/gdb are disabled on all arches with > RESTRICT=test. Should this stay open, and only be closed when > force-enabling tests passes? Or is it obsolete? Given how scary the gdb test suite is even on amd64, I'd say we can call it obsolete. The issues are still there on sparc AFAIK but I have no idea if they're sparc specific or sandbox or what. So let's leave it for now unless someone tells us gdb is actually malfunctioning, or unless someone wants to do the work of whitelisting a baseline set of tests for all arches (which would be nice!) |