Also write Crystalball coverage strategy mapping data
What does this MR do and why?
Also write Crystalball coverage strategy mapping data
This should not affect any actual behaviour because it should still read and write with the described strategy. We just additionally also write another mapping file for coverage strategy so that we can compare them.
Validation
-
update-tests-metadata: https://gitlab.com/gitlab-org/gitlab/-/jobs/7355960874 -
crystalball/packed-mapping.gz: https://gitlab.com/gitlab-org/gitlab/-/jobs/7355960874/artifacts/file/crystalball/packed-mapping.json.gz -
crystalball/packed-mapping-alt.gz: https://gitlab.com/gitlab-org/gitlab/-/jobs/7355960874/artifacts/file/crystalball/packed-mapping-alt.json.gz
Test commit is removed so we no longer run update-tests-metadata in the merge requests.
Related to #472071 (closed)
Edited by Lin Jen-Shin