framework: optimize test key fetching to fix build job going out of memory #355
+65
−37
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.
🗒️ Description
Following #320 that we had to limit the number of build workers. I think it was because the key manager is loading all keys even though most of them are not used. With parallel workers, this saturates the memory really fast.
This PR update the test key manager to lazy load individual keys only when they are needed.
Because
-n autowas failing for all builds previously, so #320 set it to 2. If this PR sets it back to-n autoand the build passes then this solution fixes the original issue.🔗 Related Issues or PRs
✅ Checklist
toxchecks to avoid unnecessary CI fails:uvx tox