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

Re: [PATCH 0/2] ci: fix the FreeBSD build

From
Carlo Marcelo Arenas Belón <carenas@gmail.com>
Date
Jul 29, 2022, 17:51 UTC
Message-ID
<20220729175108.zk63qonchmrvprsl@Carlos-MacBook-Pro-2.local>
In-Reply-To
<985e4bb8-0cb1-3980-aaf7-bd3c793f7627@github.com>
On Fri, Jul 29, 2022 at 08:58:46AM -0400, Derrick Stolee wrote:
Show 8 quoted lines
> On 7/29/2022 8:28 AM, Johannes Schindelin via GitGitGadget wrote:
> > Since 3a251bac0d1a (trace2: only include "fsync" events if we git_fsync(),
> > 2022-07-18), the FreeBSD builds are failing in t5351.6. See
> > https://cirrus-ci.com/task/4577761405698048 for an example. The run at
> > https://cirrus-ci.com/task/6004115347079168 shows that this patch fixes the
> > bug.
> 
> Thanks for noticing and fixing this bug. The FreeBSD build is slow

It usually takes a little more than 7 minutes for a full run, which is IMHO less (at least wall time) than the whole CI does; could you elaborate on why being "slow" would warrant ignoring its failures?

> and flaky enough that I sometimes ignore its output before submitting
> a series. Good that it will be green again.

I'd noticed that because it runs outside GitHub actions it sometimes has synchronization(ex [1]) issues, but that might be some bug on the integration with Cirrus which is easily avoided by looking instead directly to their status page:

  https://cirrus-ci.com/github/git/git
Carlo
Previous: Derrick StoleeNext: Junio C Hamano
Message 7 of 8 in “ci: fix the FreeBSD build”
  1. 0/2 ci: fix the FreeBSD buildJohannes Schindelin via GitGitGadget, Jul 29, 2022
  2. 1/2 t5351: avoid relying on `core.fsyncMethod = batch` to be supportedJohannes Schindelin via GitGitGadget, Jul 29, 2022
  3. Junio C HamanoJul 29, 2022
  4. brian m. carlsonJul 29, 2022
  5. 2/2 t5351: avoid using `test_cmp` for binary dataJohannes Schindelin via GitGitGadget, Jul 29, 2022
  6. Derrick StoleeJul 29, 2022
  7. Carlo Marcelo Arenas BelónJul 29, 2022
  8. Junio C HamanoJul 29, 2022

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.