| Summary: | disable test USE flag where emerge failure known | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Glenn Enright <elinar> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | enhancement | CC: | bugs+gentoo |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 108438 | ||
Not portage. You need to file bugs about the broken ebuilds, so that RESTRICT="test" can be put there if there's no better solution. |
Have some across several ebuilds that devs know fail during emerges, when tests are enabled. One example at least is glibc-2.3.5 http://bugs.gentoo.org/show_bug.cgi?id=108438 Can we engineer a method to disable these tests to avoid spurious bugs? This would be especially useful where devs had no plans to fix in certain versions, especially system ebuilds stable stream applied to individual tests? is this even possible/trivial to do?