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

Re: [BUG] t7063-status-untracked-cache flaky?

From
David Turner <dturner@twopensource.com>
Date
Oct 16, 2015, 20:11 UTC
Message-ID
<1445026298.20887.28.camel@twopensource.com>
In-Reply-To
<56211619.3090907@web.de>
On Fri, 2015-10-16 at 17:22 +0200, Torsten Bögershausen wrote:
Show 10 quoted lines
> On 15.10.15 09:52, Lars Schneider wrote:
> > Hi,
> > 
> > I noticed that "t7063-status-untracked-cache.sh" occasionally fails with "not ok 24 - test sparse status with untracked cache".
>
> I can't reproduce it here.
> Do you want to give us some info about your setup ?
> OS ?
> Harddisk, SSD, Fusion ?
> Does "debug=t verbose=t ./t7063-status-untracked-cache.sh >xx.txt
2>&1" 
> give any more information ?
(rearranged to bottom-post)
The problem is:

trash directory.t7063-status-untracked-cache$ diff trace trace.expect 3,4c3,4 < directory invalidation: 1 < opendir: 1 ---

> directory invalidation: 2
> opendir: 2
I can repro on a SSD.

I had to try many times to reproduce (I think even more the second time). I just ran the test in a while loop until it failed.

I suspect that the kernel might be a bit slow to update the mtime on the directory, but I have not yet been able to repro, and I don't understand why it only happens in this one test, since sparseness should be completely unrelated.

Previous: Torsten BögershausenNext: Junio C Hamano
Message 4 of 6 in “[BUG] t7063-status-untracked-cache flaky?”
  1. Lars SchneiderOct 15, 2015
  2. David TurnerOct 15, 2015
  3. Torsten BögershausenOct 16, 2015
  4. David TurnerOct 16, 2015
  5. Junio C HamanoOct 16, 2015
  6. David TurnerOct 16, 2015

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.