Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

azdev test failing with LROPoller Error

Open
#286 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, python
Domain
cli, testing-qa

Research direction

Reproduce the failure with azdev test and start with src/k8s-extension/azext_k8s_extension/tests/latest/test_k8s_extension_scenario.py::K8sExtensionScenarioTest::test_k8s_extension. Read the teardown assertion in azure_devtools/scenario_tests/base.py and determine which LROPoller remains active; done means this scenario test completes without the assertion failure.

Written by the indexing model from the issue text.

Description

Running azdev test is failing on our private preview extension with the following error, please help resolve this

self = <azext_k8s_extension.tests.latest.test_k8s_extension_scenario.K8sExtensionScenarioTest testMethod=test_k8s_extension>

    def tearDown(self):
        os.environ = self.original_env
        # Autorest.Python 2.x
        assert not [t for t in threading.enumerate() if t.name.startswith("AzureOperationPoller")], \
            "You need to call 'result' or 'wait' on all AzureOperationPoller you have created"
        # Autorest.Python 3.x
>       assert not [t for t in threading.enumerate() if t.name.startswith("LROPoller")], \
            "You need to call 'result' or 'wait' on all LROPoller you have created"
E       AssertionError: You need to call 'result' or 'wait' on all LROPoller you have created

env\lib\site-packages\azure_devtools\scenario_tests\base.py:154: AssertionError
------------------------------------------------------------------------------------------------------------------ Captured stderr call ------------------------------------------------------------------------------------------------------------------- 
WARNING: Command group 'k8s-extension' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Ignoring name, release-namespace and scope parameters since microsoft.azuremonitor.containers only supports cluster scope and single instance of this extension
--------------------------------------------------------------------- generated xml file: C:\Users\joinnis\.azdev\env_config\Users\joinnis\github\narayan-cli-pr\env\test_results.xml --------------------------------------------------------------------- 
================================================================================================================= short test summary info ================================================================================================================= 
FAILED src\k8s-extension\azext_k8s_extension\tests\latest\test_k8s_extension_scenario.py::K8sExtensionScenarioTest::test_k8s_extension - AssertionError: You need to call 'result' or 'wait' on all LROPoller you have created
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! xdist.dsession.Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
=================================================================================================================== 1 failed in 11.24s ====================================================================================================================
Dominant language
Python
Stars
91
Forks
134
Avg merge
2h 51m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-cli-dev-tools

All issues in Azure/azure-cli-dev-tools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.