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

Re: [PATCH] doc: update information about windows build

From
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
Date
Sep 19, 2017, 09:27 UTC
Message-ID
<ca0d3d6c-68a1-f689-6051-9ba1fc2b3a42@gmail.com>
In-Reply-To
<b1add5b2-7ebe-38b9-de85-742e64cd1ee3@talktalk.net>
On Monday 18 September 2017 12:32 AM, Phillip Wood wrote:
Show 8 quoted lines
>> May be the Windows build exit with failure on other repos rather than
>> saying it passes?
>
> I'm not quite sure what you're asking. If the tests aren't run it 
> needs to look like a pass or everyone's branches would be marked as 
> failing on github and more importantly it wouldn't be clear when there 
> was a real failure on linux/macos. If the tests are run then it will 
> pass/fail depending on the test result.

I thought failing wasn't a big issue because the macOS build failed most of the time due to time-outs, at least for me. Most of the failed builds in my build history were just the macOS builds timing out. That was some time ago. They seem to be passing quite often recently.

--- Kaartic

Previous: Phillip Wood
Message 5 of 5 in “doc: update information about windows build”
  1. doc: update information about windows buildKaartic Sivaraam, Sep 17, 2017
  2. Phillip WoodSep 17, 2017
  3. Kaartic SivaraamSep 17, 2017
  4. Phillip WoodSep 17, 2017
  5. Kaartic SivaraamSep 19, 2017

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.