René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"allure_robotframework sets incorrect statusDetails message for steps","articleBody":"#### check.robot\n```robot\n*** Test Cases ***\nTest Case To Demonstrate Allure Result File Issue\n    [Tags]    allure\n\n    Wait Until Keyword Succeeds   10x  200ms\n    ...                           Should Be True    ${{random.choice([1, 2, 11])}} \u003e 10\n    Log To Console    Next step in test case\n```\nCommand to execute the test above\n`robot --listener allure_robotframework .\\check.robot`\n\nGenerated Allure output files:\n[ff520b2f-c542-4179-b256-3ab5d6aa1ffc-result.json](https://github.com/user-attachments/files/18441802/ff520b2f-c542-4179-b256-3ab5d6aa1ffc-result.json)\nRobotFramework log file\n[log.html.txt](https://github.com/user-attachments/files/18441890/log.html.txt)\n\nPlease see screenshot below that demonstrates an issue - statusDetails message for the _Log To Console_ keyword has a message related for the first failed `Should Be True` call  in _Wait Until Keyword Succeeds_ for some reasons.\n![Image](https://github.com/user-attachments/assets/9c73b175-5abb-456a-9b1e-d4805b8b9130)\n\nPS: In fact this bug has an effect to the result.json file size, so in some cases test results can't be uploaded to the Allure TestOps due to 2,000,000 bytes limitation.\n\n**Used versions:**\nallure-python-commons 2.13.2\nallure-robotframework 2.13.2\nrobotframework           7.1","author":{"url":"https://github.com/MrBIN89","@type":"Person","name":"MrBIN89"},"datePublished":"2025-01-16T15:35:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/835/allure-python/issues/835"}