[tests] Check apk tests sizes to avoid regressions #3594
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.
Implements: #3593
Added new
ProcessApkSizestask based onProcessPlotInput, whichtakes additional argument with apk sizes reference file. The file is
used to check the current apk sizes and fails when the size difference
is over a given threshold, we use 100KiB now. There's one additional
threshold to warn about smalled differences, with current threshold
50KiB.
The reference files can be updated with
which copies the current apk sizes files to
tests/apk-sizes-referencedirectory, these are then used byProcessApkSizestask.The apk sizes files were split by configuration and contain
$(Configuration)in the name. The reason for that is an easierupdate of the references after failed PR build. (after the size
difference is checked to be valid and desired) This way it is possible
to just download the results artifacts file and copy the sizes
recorded by CI build into the reference directory.