You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
JsonMappingException: Could not read test result file allure-results #863
Getting a JsonMappingException using Allure single file generation when the parameter value exceeds the maximum allowed. The report is generated, but empty. I'm running on GitLab CI/CD.
Steps to Reproduce
Try to get json file with params value more than maximum allowed (20000000)
open cmd
run allure generate --single-file allure-results --clean
Expected Behaviour
The report is generated without errors.
Screenshots or Additional Context
Could not read test result file allure-results/03142bda-850b-4896-a93b-ca53751bdbc9-result.json
com.fasterxml.jackson.databind.JsonMappingException: String value length (20054016) exceeds the maximum allowed (20000000, from StreamReadConstraints.getMaxStringLength()) (through reference chain: io.qameta.allure.model.TestResult["steps"]->java.util.ArrayList[7]->io.qameta.allure.model.StepResult["parameters"]->java.util.ArrayList[3]->io.qameta.allure.model.Parameter["value"])
Try to get json file with params value more than maximum allowed (20000000)
Could you please provide an example where such a large parameter value is needed?
I agree that this is a valid issue that needs to be addressed. However, I think it would be better to store such large amounts of data as an attachment than to pass them on as test parameters. The described issue should not occur in this case.
But in this case, the JSON file is automatically generated when I run my test scenario in the GitLab pipeline.
When I run the same tests locally, they fail, but the file size doesn't exceed 3 or 4 MB.
Activity
sharovd commentedon Jun 16, 2025
@leandrowcs, hi!
Thanks for the issue!
Could you please provide an example where such a large parameter value is needed?
I agree that this is a valid issue that needs to be addressed. However, I think it would be better to store such large amounts of data as an attachment than to pass them on as test parameters. The described issue should not occur in this case.
leandrowcs commentedon Jul 11, 2025
But in this case, the JSON file is automatically generated when I run my test scenario in the GitLab pipeline.
When I run the same tests locally, they fail, but the file size doesn't exceed 3 or 4 MB.