Re: Windows: core.useBuiltinFSMonitor without core.untrackedcache - performance hazard?

From: Tao Klerks <tao@klerks.biz>
Date: Jun 24, 2021, 05:25 UTC
Message-ID: <CAPMMpojKMZmorKPgMASkHsvKcQTaaGyWURsgDS+KTGVeuBh1ww@mail.gmail.com>
In-Reply-To: <81153d02-8e7a-be59-e709-e90cd5906f3a@jeffhostetler.com>

Hi Jeff,

On Mon, Jun 21, 2021 at 8:41 PM Jeff Hostetler <git@jeffhostetler.com> wrote:

Show 10 quoted lines

> We're currently looking at a problem that we believe is in the
> untracked-cache code.  This is causing some of our Scalar tests
> to fail on Windows when the untracked-cache is turned on.  This
> is independent of whether FSMonitor or FSCache is turned on.
> We're still tracking this down.
>
> And yes, the best possible solution is to turn on FSMonitor *and*
> the untracked-cache, so that the "untracked" status code doesn't
> have to do anything.  So I want to look at tracking down the above
> problem before doing anything else.

I got a bit excited about a possible clean path forward to getting -uall to work well with untracked cache, and submitted a patch along those lines, but rereading the above I should probably have been a little more patient.

Is there anything "we" can do to see/understand the scalar-test-suite-error you describe above, or is this microsoft-internal?

Thanks Tao