Summary: | dev-vcs/git-1.7.3.4-r1: CVS automagically built, fails CVS testsuite with FEATURES=-userpriv USE=-cvs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeremy Murphy <jeremy.william.murphy> |
Component: | [OLD] Development | Assignee: | Robin Johnson <robbat2> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | peter, ricmm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Fails testsuite on x86
t9200 test failure t9200 test failure --verbose --no-color Updated patch against current git.git master HEAD |
Description
Jeremy Murphy
2011-01-02 04:46:34 UTC
Created attachment 258603 [details]
Fails testsuite on x86
Please re-run just test t9200 with --verbose --no-color, in non-parallel and attach the output here. (In reply to comment #2) > Please re-run just test t9200 with --verbose --no-color, in non-parallel and > attach the output here. > Sure, but... how? If I run t9200-git-cvsexportcommit.sh, I get an error about not having built things yet. Run ebuild ... package with your identical FEATURES etc. When it bails out due to test failure, go into the test dir and run it manually. Hmmm, but shouldn't it already be in that state now, after the emerge failed? It should work quite fine at that point. Can you give me the actual output from trying to run it manually after the previous emerge command? (In reply to comment #6) > It should work quite fine at that point. > Can you give me the actual output from trying to run it manually after the > previous emerge command? > If I go into work/git-1.7.3.4 there is this: # ./git-cvsexportcommit.perl Need at least one commit identifier! at ./git-cvsexportcommit.perl line 19. and if I then go into work/git-1.7.3.4/t there is this: # ./t9200-git-cvsexportcommit.sh error: You haven't built things yet, have you? That's really weird. Can you please retest with 1.7.3.5-r1 (both the automatic stuff and the manual test procedure I gave you) Created attachment 259105 [details]
t9200 test failure
OK, I re-emerged and it worked this time for some reason. Here is the output of the t9200 test from the t directory.
You missed the --verbose --no-color options for running t9200 :-(. It doesn't tell me where in the first t9200 subtest it failed. Created attachment 259114 [details]
t9200 test failure --verbose --no-color
Ah, sorry, by the time I got it working I forgot what I was doing.
Ok, reproduced now. Specifically, with FEATURES=-userpriv USE=-cvs, the CVS code is still building, and the CVS tests are running. Only, CVS can NEVER be run as root, and that's why the tests are failing. I'm working on a patch. It's a false positive for your system, but one that should be fixed for future use anyway. Fixed in 1.7.3.5-r1, no revbump. Not closing this bug because I need to port it to 1.7.4 and submit to upstream. Ported to 1.7.4_rc1, and send a version of the patch to the upstream mailing list. Thanks for devising a patch so quickly. Any chance you could also apply it to 1.7.3.4-r1, since that is the latest stable version? Done Created attachment 312295 [details, diff]
Updated patch against current git.git master HEAD
dev-vcs/git-9999 currently fails to build because of the old patch. I rebased the patch on top of current master.
(In reply to comment #17) > Created attachment 312295 [details, diff] [details, diff] > Updated patch against current git.git master HEAD > > dev-vcs/git-9999 currently fails to build because of the old patch. I > rebased the patch on top of current master. This is in the tree now. In future, please open a new bug. |