Summary: | cvs-1.11.17 tests fail | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hartwig Brandl <hartwigbrandl> |
Component: | [OLD] Development | Assignee: | Rainer Größlinger (RETIRED) <scandium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Hartwig Brandl
2004-12-03 03:03:42 UTC
Is your issue only that there is an error or do you absolutely want to run the test case? I think for cvs' case the best for now is to use use an empty src_test() since the tests take ages anyway and a failing test doesn't mean that the install is broken. If there are no objections, I'll just add an empty src_test() for now to work around this "problem" (but then again, even most people with maketest in their FEATURES probably don't want to run the cvs tests anyway). Adding an emtpy src_test() probably is a good solution. committed. Changing status to RESOLVED / FIXED because the ebuild doesn't fail because of maketest (just puts a little einfo if maketest is used) and virtually no one would want to run the cvs tests, even those using "maketest". |