https://pantsbuild.org/ logo
Join Slack
Powered by
Seeing a weird thing with “Filesystem changed duri...
# development
h
Seeing a weird thing with “Filesystem changed during run”:
I made a tiny change here, to request a VenvPex instead of a Pex: https://github.com/pantsbuild/pants/blob/main/src/python/pants/backend/python/goals/export.py#L97
And now running 
./pants -ldebug export ::
gives me:
Copy code
12:50:41.83 [INFO] Filesystem changed during run: retrying `Export` in 500ms...
12:50:41.85 [DEBUG] Canceled: pants.backend.python.util_rules.pex.build_pex
12:50:42.36 [DEBUG] Canceled: pants.backend.python.util_rules.pex_from_targets.create_pex_from_targets
12:50:42.37 [DEBUG] Completed: `export` goal
12:50:42.37 [DEBUG] Canceled: Resolve transitive targets
12:50:42.38 [INFO] Filesystem changed during run: retrying `Export` in 500ms...
12:50:42.38 [DEBUG] Canceled: pants.backend.python.util_rules.pex.build_pex
12:50:42.38 [DEBUG] Canceled: Scheduling: Building 1 requirement for requirements.pex from the src/python/pants/backend/helm/subsystems/k8s_parser.lock resolve: hikaru==0.11.0b
12:50:42.91 [DEBUG] Canceled: pants.backend.python.util_rules.pex_from_targets.create_pex_from_targets
12:50:42.91 [DEBUG] Canceled: Resolve transitive targets
12:50:42.92 [DEBUG] Completed: `export` goal
12:50:42.94 [INFO] Filesystem changed during run: retrying `Export` in 500ms...
12:50:42.94 [DEBUG] Canceled: pants.backend.python.util_rules.pex.build_pex
12:50:42.94 [DEBUG] Canceled: Scheduling: Building 1 requirement for requirements.pex from the src/python/pants/backend/helm/subsystems/k8s_parser.lock resolve: hikaru==0.11.0b
12:50:43.46 [DEBUG] Canceled: pants.backend.python.util_rules.pex_from_targets.create_pex_from_targets
12:50:43.46 [DEBUG] Canceled: Resolve transitive targets
12:50:43.47 [DEBUG] Completed: `export` goal
12:50:43.48 [DEBUG] Canceled: pants.backend.python.util_rules.pex.build_pex
12:50:43.48 [INFO] Filesystem changed during run: retrying `Export` in 500ms...
12:50:44.00 [DEBUG] Canceled: pants.backend.python.util_rules.pex_from_targets.create_pex_from_targets
12:50:44.00 [DEBUG] Completed: `export` goal
ad infinitum
But the log shows nothing out of the ordinary, and certainly not any files that have changed:
Copy code
12:50:34.02 [INFO] handling request: `-ldebug export ::`
12:50:44.32 [INFO] request completed: `-ldebug export ::`
The issue is when running the resulting pex, I think, not when creating it.
I’ll drill in, just curious if this rings any bells
e
No clue, but that's a good eye on the change. Creating a PEX means zipping and Pants does not use --no-compress and that's slow and then the PEX will need to unzip itself after - all wasted work.
w
@happy-kitchen-89482: after a goal has had a side-effect, it should not be restartable… this sounds potentially related to https://github.com/pantsbuild/pants/pull/17079 though, which landed this morning
…but with no files having changed, that’s definitely strange.
if you repro without your change as well, let me know and i can take a look.
@happy-kitchen-89482: do you have remote caching enabled locally?
h
No
👍 1
And I turned it off explicitly just to be sure
Working a hunch right now
FWIW, backing out https://github.com/pantsbuild/pants/pull/17079 did not fix this
w
sorry, but … pheew, heh
h
although it did change the exact log sequencing
but that could just be a timing thing
w
did you find out what this was? i just found https://github.com/pantsbuild/pants/issues/15360 while searching for something else
h
No, I worked around it, but can dig in a little more
w
Feel free to assign me an issue with a repro
h
Open in Slack
PreviousNext
Powered by