You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In CI, we run a cron job every day to check that master runs. In that cron job, we run the same integration test shards with and without pantsd.
Since we started introducing integration tests under chroot, those shards have been broken.
The main problem seems to be that Watchman behaves baldly under chroot (relevant thread).
As far as we know, these are the concrete problems:
When using with chroot, the watchman socket path ends up being too long.
When using with chroot, the folder we chroot to seems to dissapear before we properly close out pantsd, crashing watchman.
Repro
Run integration tests with the flag --test-pytest-chroot and the environment variable USE_PANTSD_FOR_INTEGRATION_TESTS="true"
The text was updated successfully, but these errors were encountered:
### Problem
Using the notify crate for file invalidation is now feature complete, and so we are using two file watching implementations simultaneously under `pantsd`.
### Solution
Disable watchman by default, and deprecate it. Additionally, remove the implementation of the `experimental` flag from notify. Fixes#8710, fixes#8198, fixes#7375, fixes#5487, fixes#4999, fixes#3479.
Problem
In CI, we run a cron job every day to check that master runs. In that cron job, we run the same integration test shards with and without pantsd.
Since we started introducing integration tests under chroot, those shards have been broken.
The main problem seems to be that
Watchman
behaves baldly under chroot (relevant thread).As far as we know, these are the concrete problems:
Repro
Run integration tests with the flag
--test-pytest-chroot
and the environment variableUSE_PANTSD_FOR_INTEGRATION_TESTS="true"
The text was updated successfully, but these errors were encountered: