Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test dirsrvtests/tests/suites/basic/basic_test.py::test_conn_limits fails in main branch #6296

Open
vashirov opened this issue Aug 13, 2024 · 0 comments
Assignees
Labels
needs triage The issue will be triaged during scrum

Comments

@vashirov
Copy link
Member

Issue Description
Test dirsrvtests/tests/suites/basic/basic_test.py::test_conn_limits fails in main branch:

____________________ ERROR at setup of test_conn_limits[4] _____________________

request = <SubRequest 'dscreate_with_numlistener' for <Function test_conn_limits[4]>>
dscreate_custom_instance = <dirsrvtests.tests.suites.basic.basic_test.CustomSetup object at 0x7f98b8411eb0>

    @pytest.fixture(scope="module", params=set(range(1,5)))
    def dscreate_with_numlistener(request, dscreate_custom_instance):
        numlisteners = request.param
        dscreate_custom_instance.create_wrapper(maxfds=MAX_FDS)
        inst = dscreate_custom_instance.inst
        inst.stop()
        dse_ldif = DSEldif(inst)
        dse_ldif.replace('cn=config', 'nsslapd-numlisteners', str(numlisteners))
>       inst.start()

dirsrvtests/tests/suites/basic/basic_test.py:2395: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.12/site-packages/lib389/__init__.py:177: in inner
    return f(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <dirsrvtests.tests.suites.basic.basic_test.CustomSetup.CustomDirSrv object at 0x7f98b83c11c0>
timeout = 120, args = ()
tmp_env = environ({'PATH': '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 'HOSTNAME': 'server.example.com', 'DI.../root', 'LC_CTYPE': 'C.UTF-8', 'PYTEST_CURRENT_TEST': 'tests/suites/basic/basic_test.py::test_conn_limits[4] (setup)'})
count = 119

    def start(self, timeout=120, *args):
        if self.status():
            return
        tmp_env = os.environ
        # Unset PYTHONPATH to avoid mixing old CLI tools and new lib389
        if "PYTHONPATH" in tmp_env:
            del tmp_env["PYTHONPATH"]
        try:
            subprocess.check_call([
                '/usr/bin/sh',
                self.wrapper
            ], env=tmp_env, stderr=subprocess.STDOUT)
        except subprocess.CalledProcessError as e:
            log.fatal("%s failed!  Error (%s) %s" % (self.wrapper, e.returncode, e.output))
            raise e from None
        for count in range(timeout):
            if self.status():
                return
            time.sleep(1)
>       raise TimeoutException('Failed to start ns-slpad')
E       NameError: name 'TimeoutException' is not defined

dirsrvtests/tests/suites/basic/basic_test.py:131: NameError
@vashirov vashirov added the needs triage The issue will be triaged during scrum label Aug 13, 2024
@jchapma jchapma self-assigned this Aug 15, 2024
jchapma added a commit to jchapma/389-ds-base that referenced this issue Aug 15, 2024
Description:
A CI test to validate connection management functionality by
configuring an instance with a very small connection table fails,
with the instance failing to start.

Fix description:
In a multi list connection table configuration, the connection table
code has been updated to expand the connection table size to include
a head for each list. This expanded size needs to be accounted for
when we determine if we can accept new connections and on final check
at server starup time.

Relates: 389ds#6296

Reviewed by:
jchapma added a commit that referenced this issue Aug 21, 2024
)

Description:
A CI test to validate connection management functionality by
configuring an instance with a very small connection table fails,
with the instance failing to start.

Fix description:
In a multi list connection table configuration, the connection table
code has been updated to expand the connection table size to include
a head for each list. This expanded size needs to be accounted for
when we determine if we can accept new connections and on final check
at server starup time.

Relates: #6296

Reviewed by: @droideck  (Thank you)
jchapma added a commit that referenced this issue Aug 29, 2024
)

Description:
A CI test to validate connection management functionality by
configuring an instance with a very small connection table fails,
with the instance failing to start.

Fix description:
In a multi list connection table configuration, the connection table
code has been updated to expand the connection table size to include
a head for each list. This expanded size needs to be accounted for
when we determine if we can accept new connections and on final check
at server starup time.

Relates: #6296

Reviewed by: @droideck  (Thank you)
jchapma added a commit that referenced this issue Aug 29, 2024
)

Description:
A CI test to validate connection management functionality by
configuring an instance with a very small connection table fails,
with the instance failing to start.

Fix description:
In a multi list connection table configuration, the connection table
code has been updated to expand the connection table size to include
a head for each list. This expanded size needs to be accounted for
when we determine if we can accept new connections and on final check
at server starup time.

Relates: #6296

Reviewed by: @droideck  (Thank you)
jchapma added a commit that referenced this issue Aug 29, 2024
)

Description:
A CI test to validate connection management functionality by
configuring an instance with a very small connection table fails,
with the instance failing to start.

Fix description:
In a multi list connection table configuration, the connection table
code has been updated to expand the connection table size to include
a head for each list. This expanded size needs to be accounted for
when we determine if we can accept new connections and on final check
at server starup time.

Relates: #6296

Reviewed by: @droideck  (Thank you)
jchapma added a commit that referenced this issue Aug 29, 2024
)

Description:
A CI test to validate connection management functionality by
configuring an instance with a very small connection table fails,
with the instance failing to start.

Fix description:
In a multi list connection table configuration, the connection table
code has been updated to expand the connection table size to include
a head for each list. This expanded size needs to be accounted for
when we determine if we can accept new connections and on final check
at server starup time.

Relates: #6296

Reviewed by: @droideck  (Thank you)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Development

No branches or pull requests

2 participants