Sometimes, I stop a simulation in the middle, and the simulation.log file end up broken.
I just initiate a small crapy python script to close all opened groups and end all started users.
Thus the gatling report can be generated.
Here it is, attached to this post.
healGatlingReport.py (1.59 KB)
Cool, thanks for sharing.
FYI, that’s something the standard report engine does in memory after parsing.
When I run gatling.sh -ro simulationDir, simulation log files aren’t fixed. Do you mean it should ?
No. I said that balancing happens in memory.
The only reason for someone to want to “fix” the simulation.log file is to write his own parser, which is of course something you can do, but that we don’t support.