Skip to content
Community PR Labels

update sqlserver windows test env #16217

Sign in to view logs

update sqlserver windows test env

update sqlserver windows test env #16217

GitHub Actions / Test Results failed Mar 6, 2024 in 0s

110 errors, 27 fail, 12 skipped, 129 pass in 48m 47s

   13 files     13 suites   48m 47s ⏱️
  278 tests   129 ✅  12 💤 27 ❌ 110 🔥
1 976 runs  1 677 ✅ 162 💤 27 ❌ 110 🔥

Results for commit 6ee0550.

Annotations

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_collect_load_activity[datadog_test-/*test=foo*/ SELECT * FROM \u03d1ings-SELECT \\* FROM \u03d1ings-False-expected_comments0-True] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 19m 48s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_collect_load_activity[datadog_test-/*test=foo*/ SELECT * FROM \u03d1ings-SELECT \\* FROM \u03d1ings-False-expected_comments0-False] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_collect_load_activity[datadog_test-EXEC bobProc-SELECT \\* FROM \u03d1ings-True-expected_comments1-True] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_collect_load_activity[datadog_test-EXEC bobProc-SELECT \\* FROM \u03d1ings-True-expected_comments1-False] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_metadata[metadata0-expected_metadata_payload0] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_metadata[metadata1-expected_metadata_payload1] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_reported_hostname[None-stubbed.hostname] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_reported_hostname[override.hostname-override.hostname] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_stored_procedure_characters_limit[500] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_stored_procedure_characters_limit[1000] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_activity_stored_procedure_characters_limit[2000] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check warning on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_activity_collection_rate_limit (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 15s]
Raw output 
Exception: 
Traceback (most recent call last):
  File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run
    initialization()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname
    self.load_static_information()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information
    with self.connection.open_managed_default_connection():
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection
    with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections
    self.open_db_connections(db_key, db_name, key_prefix=key_prefix)
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections
    raise_from(SQLConnectionError(check_err_message), None)
  File "<string>", line 3, in raise_from
datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login
code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None
#x1B[1m#x1B[31mtests\test_activity.py#x1B[0m:728: in test_activity_collection_rate_limit
    dd_run_check(check)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\plugin\pytest.py#x1B[0m:259: in run_check
    raise Exception('\n'.join(exc_lines))
#x1B[1m#x1B[31mE   Exception: #x1B[0m
#x1B[1m#x1B[31mE   Traceback (most recent call last):#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run#x1B[0m
#x1B[1m#x1B[31mE       initialization()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname#x1B[0m
#x1B[1m#x1B[31mE       self.load_static_information()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information#x1B[0m
#x1B[1m#x1B[31mE       with self.connection.open_managed_default_connection():#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection#x1B[0m
#x1B[1m#x1B[31mE       with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections#x1B[0m
#x1B[1m#x1B[31mE       self.open_db_connections(db_key, db_name, key_prefix=key_prefix)#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections#x1B[0m
#x1B[1m#x1B[31mE       raise_from(SQLConnectionError(check_err_message), None)#x1B[0m
#x1B[1m#x1B[31mE     File "<string>", line 3, in raise_from#x1B[0m
#x1B[1m#x1B[31mE   datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login#x1B[0m
#x1B[1m#x1B[31mE   code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None#x1B[0m

Check warning on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_async_job_enabled[True] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 14s]
Raw output 
Exception: 
Traceback (most recent call last):
  File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run
    initialization()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname
    self.load_static_information()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information
    with self.connection.open_managed_default_connection():
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection
    with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections
    self.open_db_connections(db_key, db_name, key_prefix=key_prefix)
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections
    raise_from(SQLConnectionError(check_err_message), None)
  File "<string>", line 3, in raise_from
datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login
code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None
#x1B[1m#x1B[31mtests\test_activity.py#x1B[0m:760: in test_async_job_enabled
    dd_run_check(check)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\plugin\pytest.py#x1B[0m:259: in run_check
    raise Exception('\n'.join(exc_lines))
#x1B[1m#x1B[31mE   Exception: #x1B[0m
#x1B[1m#x1B[31mE   Traceback (most recent call last):#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run#x1B[0m
#x1B[1m#x1B[31mE       initialization()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname#x1B[0m
#x1B[1m#x1B[31mE       self.load_static_information()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information#x1B[0m
#x1B[1m#x1B[31mE       with self.connection.open_managed_default_connection():#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection#x1B[0m
#x1B[1m#x1B[31mE       with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections#x1B[0m
#x1B[1m#x1B[31mE       self.open_db_connections(db_key, db_name, key_prefix=key_prefix)#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections#x1B[0m
#x1B[1m#x1B[31mE       raise_from(SQLConnectionError(check_err_message), None)#x1B[0m
#x1B[1m#x1B[31mE     File "<string>", line 3, in raise_from#x1B[0m
#x1B[1m#x1B[31mE   datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login#x1B[0m
#x1B[1m#x1B[31mE   code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None#x1B[0m

Check warning on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_async_job_enabled[False] (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 14s]
Raw output 
Exception: 
Traceback (most recent call last):
  File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run
    initialization()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname
    self.load_static_information()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information
    with self.connection.open_managed_default_connection():
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection
    with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections
    self.open_db_connections(db_key, db_name, key_prefix=key_prefix)
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections
    raise_from(SQLConnectionError(check_err_message), None)
  File "<string>", line 3, in raise_from
datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login
code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None
#x1B[1m#x1B[31mtests\test_activity.py#x1B[0m:760: in test_async_job_enabled
    dd_run_check(check)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\plugin\pytest.py#x1B[0m:259: in run_check
    raise Exception('\n'.join(exc_lines))
#x1B[1m#x1B[31mE   Exception: #x1B[0m
#x1B[1m#x1B[31mE   Traceback (most recent call last):#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run#x1B[0m
#x1B[1m#x1B[31mE       initialization()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname#x1B[0m
#x1B[1m#x1B[31mE       self.load_static_information()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information#x1B[0m
#x1B[1m#x1B[31mE       with self.connection.open_managed_default_connection():#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection#x1B[0m
#x1B[1m#x1B[31mE       with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections#x1B[0m
#x1B[1m#x1B[31mE       self.open_db_connections(db_key, db_name, key_prefix=key_prefix)#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections#x1B[0m
#x1B[1m#x1B[31mE       raise_from(SQLConnectionError(check_err_message), None)#x1B[0m
#x1B[1m#x1B[31mE     File "<string>", line 3, in raise_from#x1B[0m
#x1B[1m#x1B[31mE   datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login#x1B[0m
#x1B[1m#x1B[31mE   code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_async_job_inactive_stop (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_activity

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_async_job_cancel_cancel (sqlserver.tests.test_activity) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_connection

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_connection_cleanup (sqlserver.tests.test_connection) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check warning on line 0 in sqlserver.tests.test_connection

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_connection_failure (sqlserver.tests.test_connection) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 14s]
Raw output 
Exception: 
Traceback (most recent call last):
  File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run
    initialization()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname
    self.load_static_information()
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information
    with self.connection.open_managed_default_connection():
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection
    with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections
    self.open_db_connections(db_key, db_name, key_prefix=key_prefix)
  File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections
    raise_from(SQLConnectionError(check_err_message), None)
  File "<string>", line 3, in raise_from
datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login
code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None
#x1B[1m#x1B[31mtests\test_connection.py#x1B[0m:359: in test_connection_failure
    dd_run_check(check)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\plugin\pytest.py#x1B[0m:259: in run_check
    raise Exception('\n'.join(exc_lines))
#x1B[1m#x1B[31mE   Exception: #x1B[0m
#x1B[1m#x1B[31mE   Traceback (most recent call last):#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\datadog_checks_base\datadog_checks\base\checks\base.py", line 1210, in run#x1B[0m
#x1B[1m#x1B[31mE       initialization()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 232, in set_resolved_hostname#x1B[0m
#x1B[1m#x1B[31mE       self.load_static_information()#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\sqlserver.py", line 271, in load_static_information#x1B[0m
#x1B[1m#x1B[31mE       with self.connection.open_managed_default_connection():#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 251, in open_managed_default_connection#x1B[0m
#x1B[1m#x1B[31mE       with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):#x1B[0m
#x1B[1m#x1B[31mE     File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py", line 137, in __enter__#x1B[0m
#x1B[1m#x1B[31mE       return next(self.gen)#x1B[0m
#x1B[1m#x1B[31mE              ^^^^^^^^^^^^^^#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 256, in _open_managed_db_connections#x1B[0m
#x1B[1m#x1B[31mE       self.open_db_connections(db_key, db_name, key_prefix=key_prefix)#x1B[0m
#x1B[1m#x1B[31mE     File "D:\a\integrations-core\integrations-core\sqlserver\datadog_checks\sqlserver\connection.py", line 339, in open_db_connections#x1B[0m
#x1B[1m#x1B[31mE       raise_from(SQLConnectionError(check_err_message), None)#x1B[0m
#x1B[1m#x1B[31mE     File "<string>", line 3, in raise_from#x1B[0m
#x1B[1m#x1B[31mE   datadog_checks.sqlserver.connection_errors.SQLConnectionError: Unable to connect to SQL Server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. TCP-connection(ERROR: No connection could be made because the target machine actively refused it), Exception: unable to connect: could not open database requested by login#x1B[0m
#x1B[1m#x1B[31mE   code=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={ODBC Driver 18 for SQL Server} host=None#x1B[0m

Check warning on line 0 in sqlserver.tests.test_connection

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_connection_error_reporting[unknown_adoprovider-instance_overrides0-expected_error_patterns0-ConnectionErrorCode.driver_not_found] (sqlserver.tests.test_connection) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 2s]
Raw output 
assert None
 +  where None = <function search at 0x000001FB6A858AE0>('TCP-connection\\(OK\\).*Provider cannot be found. It may not be properly installed.', 'unable to connect to sql server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#common-driver-issues for more details on how to debug this issue. tcp-connection(error: no connection could be made because the target machine actively refused it), exception: operationalerror(com_error(-2147352567, \'exception occurred.\', (0, \'adodb.connection\', \'provider cannot be found. it may not be properly installed.\', \'c:\\\\windows\\\\help\\\\ado270.chm\', 1240655, -2146824582), none), \'error opening connection to "connectretrycount=2;provider=fake;data source=localhost,1433;initial catalog=master;user id=datadog;password=******;"\')\ncode=common-driver-issues connection_host=localhost,1433 connector=adodbapi database=master driver={odbc driver 18 for sql server} host=none', re.IGNORECASE)
 +    where <function search at 0x000001FB6A858AE0> = re.search
 +    and   re.IGNORECASE = re.IGNORECASE
#x1B[1m#x1B[31mtests\test_connection.py#x1B[0m:500: in test_connection_error_reporting
    assert re.search(expected_error_pattern, message, re.IGNORECASE)
#x1B[1m#x1B[31mE   assert None#x1B[0m
#x1B[1m#x1B[31mE    +  where None = <function search at 0x000001FB6A858AE0>('TCP-connection\\(OK\\).*Provider cannot be found. It may not be properly installed.', 'unable to connect to sql server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#common-driver-issues for more details on how to debug this issue. tcp-connection(error: no connection could be made because the target machine actively refused it), exception: operationalerror(com_error(-2147352567, \'exception occurred.\', (0, \'adodb.connection\', \'provider cannot be found. it may not be properly installed.\', \'c:\\\\windows\\\\help\\\\ado270.chm\', 1240655, -2146824582), none), \'error opening connection to "connectretrycount=2;provider=fake;data source=localhost,1433;initial catalog=master;user id=datadog;password=******;"\')\ncode=common-driver-issues connection_host=localhost,1433 connector=adodbapi database=master driver={odbc driver 18 for sql server} host=none', re.IGNORECASE)#x1B[0m
#x1B[1m#x1B[31mE    +    where <function search at 0x000001FB6A858AE0> = re.search#x1B[0m
#x1B[1m#x1B[31mE    +    and   re.IGNORECASE = re.IGNORECASE#x1B[0m

Check warning on line 0 in sqlserver.tests.test_connection

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_connection_error_reporting[unknown_database-instance_overrides5-expected_error_patterns5-ConnectionErrorCode.tcp_connection_failed] (sqlserver.tests.test_connection) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 14s]
Raw output 
AssertionError: assert None
 +  where None = <function search at 0x000001FB6A858AE0>('TCP-connection\\(OK\\).*could not open database requested by login', 'unable to connect to sql server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. tcp-connection(error: no connection could be made because the target machine actively refused it), exception: unable to connect: could not open database requested by login\ncode=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=wrong driver={odbc driver 18 for sql server} host=none', re.IGNORECASE)
 +    where <function search at 0x000001FB6A858AE0> = re.search
 +    and   re.IGNORECASE = re.IGNORECASE
#x1B[1m#x1B[31mtests\test_connection.py#x1B[0m:500: in test_connection_error_reporting
    assert re.search(expected_error_pattern, message, re.IGNORECASE)
#x1B[1m#x1B[31mE   AssertionError: assert None#x1B[0m
#x1B[1m#x1B[31mE    +  where None = <function search at 0x000001FB6A858AE0>('TCP-connection\\(OK\\).*could not open database requested by login', 'unable to connect to sql server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. tcp-connection(error: no connection could be made because the target machine actively refused it), exception: unable to connect: could not open database requested by login\ncode=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=wrong driver={odbc driver 18 for sql server} host=none', re.IGNORECASE)#x1B[0m
#x1B[1m#x1B[31mE    +    where <function search at 0x000001FB6A858AE0> = re.search#x1B[0m
#x1B[1m#x1B[31mE    +    and   re.IGNORECASE = re.IGNORECASE#x1B[0m

Check warning on line 0 in sqlserver.tests.test_connection

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs failed: test_connection_error_reporting[invalid_credentials-instance_overrides6-expected_error_patterns6-ConnectionErrorCode.login_failed_for_user] (sqlserver.tests.test_connection) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 14s]
Raw output 
AssertionError: assert None
 +  where None = <function search at 0x000001FB6A858AE0>('TCP-connection\\(OK\\).*login failed for user', 'unable to connect to sql server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. tcp-connection(error: no connection could be made because the target machine actively refused it), exception: unable to connect: could not open database requested by login\ncode=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={odbc driver 18 for sql server} host=none', re.IGNORECASE)
 +    where <function search at 0x000001FB6A858AE0> = re.search
 +    and   re.IGNORECASE = re.IGNORECASE
#x1B[1m#x1B[31mtests\test_connection.py#x1B[0m:500: in test_connection_error_reporting
    assert re.search(expected_error_pattern, message, re.IGNORECASE)
#x1B[1m#x1B[31mE   AssertionError: assert None#x1B[0m
#x1B[1m#x1B[31mE    +  where None = <function search at 0x000001FB6A858AE0>('TCP-connection\\(OK\\).*login failed for user', 'unable to connect to sql server, see https://docs.datadoghq.com/database_monitoring/setup_sql_server/troubleshooting#tcp-connection-error for more details on how to debug this issue. tcp-connection(error: no connection could be made because the target machine actively refused it), exception: unable to connect: could not open database requested by login\ncode=tcp-connection-error connection_host=localhost,1433 connector=adodbapi database=master driver={odbc driver 18 for sql server} host=none', re.IGNORECASE)#x1B[0m
#x1B[1m#x1B[31mE    +    where <function search at 0x000001FB6A858AE0> = re.search#x1B[0m
#x1B[1m#x1B[31mE    +    and   re.IGNORECASE = re.IGNORECASE#x1B[0m

Check failure on line 0 in sqlserver.tests.test_integration

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_check_invalid_password (sqlserver.tests.test_integration) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_integration

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_check_dbm_enabled_config[True] (sqlserver.tests.test_integration) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_integration

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_check_dbm_enabled_config[False] (sqlserver.tests.test_integration) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m

Check failure on line 0 in sqlserver.tests.test_integration

See this annotation in the file changed.

@github-actions github-actions / Test Results

1 out of 7 runs with error: test_check_dbm_enabled_config[true] (sqlserver.tests.test_integration) 

artifacts/test-results/SQL Server on Windows/test-unit-py3.11-windows-SQLOLEDB-2019-single.xml [took 0s]
Raw output 
failed on setup with "tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]"
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:382: in __call__
    result = fn(*args, **kwargs)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:98: in set_up_with_retry
    return set_up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:79: in set_up
    set_up_result = up()
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:247: in __call__
    return run_command(self.command, check=True)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\subprocess.py#x1B[0m:77: in run_command
    raise SubprocessError(
#x1B[1m#x1B[31mE   datadog_checks.dev.errors.SubprocessError: Command: ['docker', 'compose', '-f', 'D:\\a\\integrations-core\\integrations-core\\sqlserver\\tests\\compose-windows\\docker-compose.yaml', 'up', '-d', '--force-recreate', '--build']#x1B[0m
#x1B[1m#x1B[31mE   Exit code: 1#x1B[0m
#x1B[1m#x1B[31mE   Captured Output:#x1B[0m

#x1B[33mThe above exception was the direct cause of the following exception:#x1B[0m
#x1B[1m#x1B[31mtests\conftest.py#x1B[0m:330: in dd_environment
    with docker_run(compose_file=compose_file, conditions=conditions, mount_logs=True, build=True, attempts=3):
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\docker.py#x1B[0m:218: in docker_run
    with environment_run(
#x1B[1m#x1B[31mC:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\contextlib.py#x1B[0m:137: in __enter__
    return next(self.gen)
#x1B[1m#x1B[31m..\datadog_checks_dev\datadog_checks\dev\env.py#x1B[0m:110: in environment_run
    result = set_up_func()
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:289: in wrapped_f
    return self(f, *args, **kw)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:379: in __call__
    do = self.iter(retry_state=retry_state)
#x1B[1m#x1B[31mC:\Users\runneradmin\AppData\Local\hatch\env\virtual\datadog-sqlserver\zl4h8FuS\py3.11-windows-SQLOLEDB-2019-single\Lib\site-packages\tenacity\__init__.py#x1B[0m:326: in iter
    raise retry_exc from fut.exception()
#x1B[1m#x1B[31mE   tenacity.RetryError: RetryError[<Future at 0x1fb709224d0 state=finished raised SubprocessError>]#x1B[0m
View more details on GitHub Actions