#47847 lib389 - unit test failures
Closed: wontfix Opened by mkubik.

The tests were ran on rev. 8e136ed after applying patch from #47691.

The paths in the test scripts has been updated to reflect the applied patch.

Summary:

- some tests have problems with passed unexpected arguments
- some tests try to access non-existent attributes
- some tests do not reflect current API of lib389
- several tests try to import _constants module that has been moved or removed
- module proxy tests aren't used anywhere -- just functions, nose tries to execute them
- some key errors on dictionaries (key access instead of get method)
- various problems in replication agreement tests
- problems with hostname resolution

Complete error log attached.

Tests were run on a system with DS installed via RPM.
Python environment:

python 2.7.5
nose==1.3.3
pytest==2.5.2
python-ldap==2.4.15

Metadata Update from @mkubik:
- Issue set to the milestone: lib389 1.0.2

I think that this is a bit too old to consider an issue now. If you would like, please re-run the tests now as we have done a lot of work to improve this situation.

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

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/1178

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: invalid)

Metadata