Not sure why, but conflict_resolve_test.py fails only with DEBUGGING=True:
dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_add_modrdn PASSED [ 16%] dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_complex_add_modify_modrdn_delete ERROR [ 33%] dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_memberof_groups ERROR [ 50%] dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_managed_entries xfail [ 66%] dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_nested_entries_with_children ERROR [ 83%] dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestThreeMasters::test_nested_entries xfail [100%]
Opening this for the further investigation.
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.1
Metadata Update from @vashirov: - Issue set to the milestone: CI test 1.0 (was: 1.4.1)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3441
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.