René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Step tree seems not correct in multithreaded testing","articleBody":"[//]: # (\n. Note: for support questions, please use Stackoverflow or Gitter**. \n. This repository's issues are reserved for feature requests and bug reports.\n.\n. In case of any problems with Allure Jenkins plugin** please use the following repository \n. to create an issue: https://github.com/jenkinsci/allure-plugin/issues\n.\n. Make sure you have a clear name for your issue. The name should start with a capital \n. letter and no dot is required in the end of the sentence. An example of good issue names:\n.\n. - The report is broken in IE11\n. - Add an ability to disable default plugins\n. - Support emoji in test descriptions\n)\n\n#### I'm submitting a ... \n  - [x] bug report\n  - [ ] feature request\n  - [ ] support request =\u003e Please do not submit support request here, see note at the top of this template.\n\n#### What is the current behavior?\n\nWhen Thead#entrance spawned Thread#node, Thread#node spawned Thread#session, step tree of allure seems incorrect?\n\n\u003cimg width=\"620\" height=\"889\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8ed74de4-451c-44c7-9a9d-88476e483f38\" /\u003e\n\n#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem\n\n```python\nfrom concurrent.futures import ThreadPoolExecutor\nimport allure\n\n\ndef session_on_node(node_id, session):\n    with allure.step(f\"Session#{session} on node {node_id}\"):\n        pass\n\n\ndef parallel_task_for_specific_node(node_id):\n    with allure.step(f\"Parallel task for node {node_id}\"):\n        with ThreadPoolExecutor() as executor:\n            for session in range(5):\n                executor.submit(session_on_node, node_id, session)\n\n            executor.shutdown(wait=True)\n\n\ndef test_multithreaded():\n    with allure.step(\"Entrance\"):\n        with ThreadPoolExecutor() as executor:\n            for node_id in range(3):\n                executor.submit(parallel_task_for_specific_node, node_id)\n\n            executor.shutdown(wait=True)\n\n```\n\n#### What is the expected behavior?\n\nstep tree should be like this?\n\n```\nThread#entrance\n        - Thread#node\n                - Thread#session\n                - Thread#session\n                - Thread#session\n        - Thread#node\n                - Thread#session\n                - Thread#session\n                - Thread#session\n```\n\n#### What is the motivation / use case for changing the behavior?\n\nThere is a service combined of multiple nodes. Every node could handle several sessions from client. \nSometimes, parallel testing is needed: Multi sessions for multi nodes, which means main thread is to spawn threads of different node, thread of a single node is to spawn different threads of multiple session, and finally we collect every step and organize them in a friendly tree.\n\n#### Please tell us about your environment:\n\n- Allure version:        2.32.0\n- Test framework:        pytest@7.4.4\n- Allure adaptor:        allure-pytest@2.13.5\n\n#### Other information \n\n[//]: # (\n. e.g. detailed explanation, stacktraces, related issues, suggestions \n. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc\n)","author":{"url":"https://github.com/SalHe","@type":"Person","name":"SalHe"},"datePublished":"2025-08-05T12:49:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/872/allure-python/issues/872"}