Since runtime numbers are mainly justified for large ZIM files, the solution is to report small runtimes as " Performance testing, it keeps serving as a simple defence against unintended significant slowdown in zimcheck). the performance info is preserved in the output and is not excluded from comparison (so that, in the absence of dedicated no discrimination between fast and (moderately) slow build environmentsī. The challenge was to come up with a solution meeting the following requirements:Ī. The incurred slowdown results in the runtime exceeding the 0.5 second limit whereupon the performance report changes and the unit-tests fail (openzim/zim-tools#287). However, Debian builds and tests zimcheck - among other configurations - on virtualized hardware too. Which corresponds to the duration of the flow being under half a second. Since those flows are very small the corresponding line from the zimcheck output used to be Total time taken by zimcheck: 0 seconds. The unit-tests of zimcheck include a report on the total runtime of each flow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |