Hi Sumit,
Using either of your approaches worked, thanks. Using the ci/run script
seems like the easiest/best choice as presumably dependencies are tracked in
lock step with sssd version, unlike the dnf builddep approach.
Using that same devcontainer, I noticed the ci tests (run without -d
Here is the output:
[root@b0853212bcdb ci-build-debug]# ./file_watch-tests -d 9
Could not chdir to [/dev/shm/ci-test-dir.XcCkS8dF].
Attempting to continue with current dir
Running suite(s): file_watch
[sssd] [setup_file_watch] (0x4000): ==
[sssd] [test_file_
Hi Alexander,
I agree that inotify has known issues with WSL2, but I expect it would only
be an issue with bind mounts and I'm not using any. I ran the devcontainer on
a different host with Windows 11 Pro host and WSL2 and it worked fine, so there
is something odd with my Windows 11 Home edi
