git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: t9400-git-cvsserver-server failures

From
Brian Gernhardt <benji@silverinsanity.com>
Date
Jun 27, 2007, 13:08 UTC
Message-ID
<DA4A2395-33EA-4209-A1DE-E6CAB55C94AD@silverinsanity.com>
In-Reply-To
<3E98C380-541B-479F-9E8F-6BBE82EE2930@silverinsanity.com>
On Jun 26, 2007, at 11:07 PM, Brian Gernhardt wrote:
Show 17 quoted lines
> I'm getting several failures in the git-cvsserver tests.  I don't  
> even know where to start with that code, so here's as detailed an  
> error report as I can give.
>
> The first category appears to be that several of the tests use  
> test_expect_failure, which expects the error codes to be less than  
> 127 and the error it gets is 255 (-1).
>
> * FAIL 9: req_Root failure (strict-paths)
>         cat request-anonymous | git-cvsserver --strict-paths  
> pserver $WORKDIR >log 2>&1
> * FAIL 11: req_Root failure (w/o strict-paths)
>         cat request-anonymous | git-cvsserver pserver $WORKDIR/ 
> gitcvs >log 2>&1
> * FAIL 13: req_Root failure (base-path)
>         cat request-anonymous | git-cvsserver --strict-paths --base- 
> path $WORKDIR pserver $SERVERDIR >log 2>&1

Running the tests again this morning after a fresh pull results in only the above failures occurring. I looked through git- cvsserver.perl and couldn't find any exit(-1) or similar. Anyone have any idea where to start to fix these?

~~ Brian
Previous: Brian GernhardtNext: Frank Lichtenheld
Message 2 of 3 in “t9400-git-cvsserver-server failures”
  1. Brian GernhardtJun 27, 2007
  2. Brian GernhardtJun 27, 2007
  3. Frank LichtenheldJun 27, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.