On Fri, Sep 27, 2024 at 6:51 PM Ryan Slominski via sssd-users < [email protected]> wrote:
> 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_watch_no_file] (0x4000): Watching file > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_inotify > [sssd] [watch_file] (0x1000): Falling back to polling > Difference starts here ^^ . In a "regular" environment test output looks like: ``` [sssd] [test_file_watch_no_file] (0x4000): Watching file /dev/shm/file-watch-test-dir/../file-watch-test-dir/watched_file_inotify [sssd] [snotify_watch] (0x2000): Opened inotify fd 5 [sssd] [snotify_watch] (0x2000): Opened file watch -1 [sssd] [snotify_watch] (0x2000): Opened directory watch 1 [sssd] [_snotify_create] (0x0400): Added a watch for /dev/shm/file-watch-test-dir/watched_file_inotify with inotify flags 0x8D88 internal flags 0x1 using function watched_file_inotify_cb after delay 1.0 ``` Perhaps `inotify` infrastructure doesn't work in container env. If this is indeed the case then sssd.conf::try_inotify option can be used to disable attempting this feature usage. > [sssd] [fw_watch_file_poll] (0x3f7c0): File > [/dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_inotify] > is missing. Will try again later. > [sssd] [set_file_watching] (0x1000): > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_inotify > missing. Waiting for it to appear. > [sssd] [modify_file] (0x0400): Modifying file > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/unwatched_file > [sssd] [setup_file_watch] (0x4000): > ========================================== > [sssd] [modify_file] (0x0400): Modifying file > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_inotify.exists > [sssd] [setup_file_watch] (0x4000): > ========================================== > [sssd] [test_file_watch_no_file] (0x4000): Watching file > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_poll > [sssd] [fw_watch_file_poll] (0x3f7c0): File > [/dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_poll] > is missing. Will try again later. > [sssd] [set_file_watching] (0x1000): > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_poll > missing. Waiting for it to appear. > [sssd] [modify_file] (0x0400): Modifying file > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/unwatched_file > [sssd] [setup_file_watch] (0x4000): > ========================================== > [sssd] [modify_file] (0x0400): Modifying file > /dev/shm/ci-test-dir.XcCkS8dF/file-watch-test-dir/../file-watch-test-dir/watched_file_poll.exists > 0%: Checks: 4, Failures: 4, Errors: 0 > /workspaces/sssd/src/tests/file_watch-tests.c:118:F:file_watch:test_inotify_no_file:0: > Failed to open the file. > /workspaces/sssd/src/tests/file_watch-tests.c:118:F:file_watch:test_inotify_with_file:0: > Failed to open the file. > /workspaces/sssd/src/tests/file_watch-tests.c:118:F:file_watch:test_poll_no_file:0: > Failed to open the file. > /workspaces/sssd/src/tests/file_watch-tests.c:118:F:file_watch:test_poll_with_file:0: > Failed to open the file. > > > Maybe a side-effect of running tini instead of systemd? Side effect of > running on Windows WSL2 container host? > > > More info: > > [root@b0853212bcdb sssd]# cd /dev > [root@b0853212bcdb dev]# ls -ltra > total 4 > drwxrwxrwt 2 root root 40 Sep 27 16:40 mqueue > drwxr-xr-x 1 root root 4096 Sep 27 16:40 .. > crw-rw-rw- 1 root root 1, 5 Sep 27 16:40 zero > crw-rw-rw- 1 root root 1, 9 Sep 27 16:40 urandom > crw-rw-rw- 1 root root 5, 0 Sep 27 16:40 tty > lrwxrwxrwx 1 root root 15 Sep 27 16:40 stdout -> /proc/self/fd/1 > lrwxrwxrwx 1 root root 15 Sep 27 16:40 stdin -> /proc/self/fd/0 > lrwxrwxrwx 1 root root 15 Sep 27 16:40 stderr -> /proc/self/fd/2 > crw-rw-rw- 1 root root 1, 8 Sep 27 16:40 random > drwxr-xr-x 2 root root 0 Sep 27 16:40 pts > lrwxrwxrwx 1 root root 8 Sep 27 16:40 ptmx -> pts/ptmx > crw-rw-rw- 1 root root 1, 3 Sep 27 16:40 null > crw-rw-rw- 1 root root 1, 7 Sep 27 16:40 full > lrwxrwxrwx 1 root root 13 Sep 27 16:40 fd -> /proc/self/fd > lrwxrwxrwx 1 root root 11 Sep 27 16:40 core -> /proc/kcore > drwxr-xr-x 5 root root 360 Sep 27 16:40 . > drwxrwxrwt 2 root root 40 Sep 27 16:46 shm > crw--w---- 1 root tty 136, 0 Sep 27 16:48 console > [root@b0853212bcdb dev]# cd shm > [root@b0853212bcdb shm]# ls -ltr > total 0 > -- > _______________________________________________ > sssd-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
-- _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
