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

Re: Can't get git to stop outputting to StdErr

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 28, 2016, 21:06 UTC
Message-ID
<xmqq7f8syyhg.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<c09d32d8ab97418d98ddf356e20a6ff5@ES4.impromed.com>
"Scott R. Chamberlain" <srchamberlain@impromed.com> writes:
> The line I do is:
>
>     git push -q binaryRepo HEAD:"$Env:BUILD_SOURCEBRANCH"
This would 
 (1) squelch the output from the sending side (i.e. local), and
 (2) ask "quiet" to the receiving side (i.e. remote), if they know
     how to be quiet.
Show 6 quoted lines
> But I get the following in my log after the build
>
>     2016-10-28T20:05:32.3179442Z ##[error]remote: 
>     remote: Analyzing objects... (3/3) (657 ms)        
>     remote: Storing packfile... done (40 ms)        
>     remote: Storing index... done (42 ms)        

These three lines prefixed with "remote:" are coming from the software that runs on the remote machine that accepts your push, but the way it says these three things do not look familiar to me. Is it possible that the remote machine is running a Git server that is not ours, which lacks the support for "quiet" capability? If that is the case, the symptom is understandable.

A quick archive search tells me that you are seeing the same issue as this one:

https://public-inbox.org/git/20160516133731.GA6903@sigill.intra.peff.net/
where the concluding remark, to which I agree, is:
    The server side here is clearly not stock git, from the content
    of those progress messages (some googling shows it looks like
    whatever visualstudio.com is running, but I don't know what that
    is). So either the server implementation doesn't support the
    "quiet" protocol extension, or it is ignoring it. It might be
    worth filing a bug with them.
Previous: Scott R. ChamberlainNext: Scott R. Chamberlain
Message 2 of 4 in “Can't get git to stop outputting to StdErr”
  1. Scott R. ChamberlainOct 28, 2016
  2. Junio C HamanoOct 28, 2016
  3. Scott R. ChamberlainOct 28, 2016
  4. Scott R. ChamberlainDec 19, 2016

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.