show gzipped structures in analysis report #758
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You are about to submit a new Pull Request. Before continuing make sure you read the contributing guidelines and that you comply with the following criteria:
tox
tests pass. Runtox
command inside the repository folder-test.cfg
examples execute without errors. Insideexamples/
runpython run_tests.py -b
Closes #713 by adding a check on the
clean
configuration parameter. If clean is True, then the structures will be gzipped in the last stage of the workflow, thus making them unaccessible in the html report. To solve this, at the postprocessing stage we check the clean parameter. If True, the file names are modified by adding the .gz suffix.Important : this PR cannot take care of the case in which clean is False at the global level and True at the module level (and vice versa), as this would require a complicated traceback at the postprocessing stage, which is out of the scope of the analysis. This is a very unlikely scenario.