I don't have the greatest description of the probl...
# general
h
I don't have the greatest description of the problem, but has anyone ever seen anything like the log spam in the thread?
Copy code
Running Pants tests...
11:17:51.29 [INFO] Filesystem changed during run: retrying `ChangedAddresses` in 500ms...
11:17:57.10 [INFO] Filesystem changed during run: retrying `ChangedAddresses` in 500ms...
11:18:01.38 [INFO] Filesystem changed during run: retrying `ChangedAddresses` in 500ms...
11:18:02.85 [INFO] Filesystem changed during run: retrying `ChangedAddresses` in 500ms...
11:18:07.91 [INFO] Filesystem changed during run: retrying `ChangedAddresses` in 500ms...
f
There have been some reports of similar errors with Pants goals that modify source files. https://github.com/pantsbuild/pants/issues/14466
Are your tests writing files into the source tree?
h
This is just
./pants test
, though
I'd have to do a check, but I don't think so. Anything in
testdata
folders should just be read-only and anything that gets generated as part of a test is usually using
tempfile
f
also I suggest running with debug logging (
-ldebug
) and see what paths the filesystem watch code logs
w
rather than
-ldebug
, you’ll want to check the pantsd log at
.pants.d/pants.log
: invalidation is logged at INFO, but only to the log file.
h
Anything specific to look for? Will it report what is trying to change files?
w
it will report which files are changing
👍 1
something like this:
Copy code
20:30:03.93 [INFO] notify invalidation: cleared 0 and dirtied 0 nodes for: {"pants.toml"}
h
Okay, we're having trouble reproducing, but hopefully it's a bad test on our end or something. If I do find anything that doesn't seem like our doing, I'll post it to the ticket linked above.
❤️ 1