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, so simply ./contrib/ci/run) fail with 1 issue:
[root@1e8d8cdc9537 sssd]# cat ci-build-debug/test-suite.log ========================================= sssd 2.10.0-beta2: ./test-suite.log =========================================
# TOTAL: 99 # PASS: 98 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0
.. contents:: :depth: 2
FAIL: file_watch-tests ======================
Running suite(s): file_watch 75%: Checks: 4, Failures: 1, Errors: 0 /workspaces/sssd/src/tests/file_watch-tests.c:162:F:file_watch:test_poll_no_file:0: Callback not invoked on creation. FAIL file_watch-tests (exit status: 1)
Any tips?