search

allure-framework / allure-python

Allure integrations for Python test frameworks
https://allurereport.org/
Apache License 2.0
726 stars 237 forks source link

Robot Framework Allure listener generates a huge amount of files #814

Open chache35 opened 4 years ago

chache35 commented 4 years ago

Describe the bug When I use the Allure listener with Robot-Framework, a huge amount of files are generated. For example : around 3000 json & html files (13MB !) are generated for a couple of basics Robot-Framework tests. The final Allure report generated from the same tests also contains around 1500 files (6MB).

This situation has a limited impact for some basics tests, but, in case of my real tests campaign, more than 800.000 files are generated, for more than 1GB size ! This lead to memory issues or disk spaces failures.

To Reproduce Steps to reproduce the behavior:

  1. Start a basic Robot-Framework test campaign with the Allure listener ( --listener "allure_robotframework;allure-export"
  2. Check the number of files in the "allure-export" folder and its size.
  3. Generate the Allure report from the previous export files.
  4. Check the number of files in the report folder, and its size .

Expected behavior The listener output and Allure report should be optimized to reduce number of files generated and their size.

Environment (please complete the following information):

Allure version: 2.12.1 Test framework: robotframework@3.0.2 Allure adaptor: allure-robotframework@2.8.6

apallier commented 4 years ago

+1

yvespelle commented 3 years ago

+1

inurmi commented 3 years ago

My workaround for this is following:

  1. delete old allure results folder (in you example above its "allure-export" folder)
  2. run robot tests with listener normally
  3. to show trends in allure report, copy history folder under results folder (in you example it should go under "allure-export" folder)
  4. generate allure report with --clean option
bucherarnold commented 6 months ago

any update about this bug?

Permillisecond commented 1 week ago

Just +1, every logged entry = one html file for now, it's hard to keep retries/history, in our environment it takes more than 2 minutes to just delete results folder with more than 50k files related to one test run.

SerhiiMaksymivQAMadness commented 1 week ago

hey, any update about this 'bug'? we recently updated framework and have moved to a newer allure version. now, because of generated artifact files jvm is crashing on one of our allure-report steps. tried increasing heap size on machine, still, same issue