Build sub reports per platform & suite #124
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
La0
force-pushed
the
suites
branch
7 times, most recently
from
aa923b6 to
0f4075a
Compare
added 12 commits
September 3, 2019 13:23
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on top of #114 (to merge first).
Fixes #104
The uploaded reports are using these new paths:
mozilla-central/revXXXX/all:all.json.zstdfor the full report currently usedmozilla-central/revXXXX/platform:suite.json.zstdfor the a sub report for a specific platform & suite combination.platformdefaults toallI've also looked into GCP object metadata to store more efficiently these informations, but their API does not allow to search objects by metadata: so that would not be an effective lookup strategy for the backend.